I have started migrating a batch of single user(35GB) of size, after the migration reached 8 GB, i was stuck in Syncing state for almost 4 hours now.

Provide a solution.

Hi All,

I have configured Exchange 2013 hybrid with Office 365. I want reconfigure hybrid configuration, I success logon to the ECP but cannot run the hybrid configuration wizard from inside the link in the console. Prompts for sign in to O365 then page just continues to load and receive the error below.

Please help me T_T

Thank you,

-IH-

Error details:

The web page isn't loading correctly. Please reload the page by refreshing your browser.
Technical Information: Uncaught SecurityError: Blocked a frame with origin "https://webmail.domain.com" from accessing a cross-origin frame.
The entire error report is listed below: Hide report

Client Information
------------------
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
CPU Class: undefined
Platform: Win32
System Language: undefined
User Language: en-US
CookieEnabled: true
-----------------
Exception Details
-----------------
Date: Fri Jul 14 2017 17:51:15 GMT+0700 (SE Asia Standard Time)
Message: Uncaught SecurityError: Blocked a frame with origin "https://webmail.domain.com" from accessing a cross-origin frame.
Url: https://webmail.domain.com/ecp/15.0.1210.3/scripts/common.js
Line: 1

Call Stack
----------
Error
    at Function.ErrorHandling.$EM (https://webmail.domain.com/ecp/15.0.1210.3/scripts/common.js:1:172926)
    at ErrorHandling.showUnhandledException (https://webmail.domain.com/ecp/15.0.1210.3/scripts/common.js:1:172011)




Dump Event
----------
isTrusted = true
message = Uncaught SecurityError: Blocked a frame with origin "https://webmail.domain.com" from accessing a cross-origin frame.
filename = https://webmail.domain.com/ecp/15.0.1210.3/scripts/common.js
lineno = 1
colno = 373014
error = SecurityError: Blocked a frame with origin "https://webmail.domain.com" from accessing a cross-origin frame.
NONE = 0
CAPTURING_PHASE = 1
AT_TARGET = 2
BUBBLING_PHASE = 3
type = error
target = [object Window]
currentTarget = [object Window]
eventPhase = 2
bubbles = false
cancelable = true
defaultPrevented = false
composed = false
timeStamp = 132.69
srcElement = [object Window]
returnValue = true
cancelBubble = false
path = [object Window]
composedPath = function composedPath() { [native code] }
stopPropagation = function stopPropagation() { [native code] }
stopImmediatePropagation = function stopImmediatePropagation() { [native code] }
preventDefault = function preventDefault() { [native code] }
initEvent = function initEvent() { [native code] }

Screenshot:

Hi experts

When trying to install another Exchange 2013 server in my test environment I got the following error:

 The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)
          {
            $setSharedCDCErrors = @();
            try
            {
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)
              {
                break;
              }
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            }
            catch
            {
              Write-ExchangeSetupLog -Info ("An exception ocurred while settingshared config DC. Exception: " + $_.Exception.Message);
            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attemptingagain.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          }

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }
        " was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

Did I miss anything? Any solution to this ?

Hi,

I have started a phased migration to Hybrid Exchange/Office 365 and noticed a few problems. The main one is that when I move a mailbox from on-premises to Office 365, it completes OK and the user can access the mailbox from Outlook. However, they can only see the other users on Office 365, they cannot see the local Global Address List. Mail sent to local mailboxes fails saying the mailbox couldn't be found. It seems to only look at the Office 365 address list, not the on-premises one.

I'm using Centralized Mail Transport with Exchange Classic Hybrid Topology. For Azure AD I'm using Password Hash Sync and I've ticked the box for Exchange Hybrid Deployment Azure AD Connect.

Any ideas on what I might have missed?

Thanks,

Pat Rooney

Hi all,

I  faced an error while installing exchange 2013 cu9 on windows server 2012 R2:

in the step 11 of 15:

Error:
The following error was generated when "$error.Clear(); 
          $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
          $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
          $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
          if( $dismbx -ne $null)
          {
          $srvname = $dismbx.ServerName;
          if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
          {
          Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -eq $null )
          {
          Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
          mount-database $dismbx.Database;
          }

          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -ne $null )
          {
          $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
          $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
          if( $dmRoleGroup -ne $null )
          {
            trap [Exception]
            {
              Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              continue;
            }

            Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
          }
          }
          }
          }
        " was run: "Microsoft.Exchange.Data.Common.LocalizedException: Couldn't resolve the user or group "***.**.**/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust. ---> System.SystemException: The trust relationship between the primary domain and the trusted domain failed.

   at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed)
   at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
   at System.Security.Principal.NTAccount.Translate(Type targetType)
   at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
   at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetSecurityPrincipal(IRecipientSession session, SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
   at Microsoft.Exchange.Management.RecipientTasks.SetMailboxPermissionTaskBase.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.AddMailboxPermission.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Any help will be highly appreciated :)

Hello and thank you for help.

I started an exchange migration, right now both server are up and running. Owa is working fine, ECP is working fine, I can connect to outlook via phone and send emails. 

I also created a signed certificate, which is working.

Now my problem. 

Exchange 2013 had different host names for internal and external.

Internal mail.contoso.local

External exchange.contoso.eu

Using IIS I created a signed certificate over a CA server for mail.contoso.local. Both at the same time, not working.

So I made a split DNS entry for exchange.contoso.local and added the internal Ip of Ex 2013, alongside autodiscover. I also changed autodiscover _tcp entry in the old DNS forest, the standard one.

Changed all internal virtual folders to match the external one, also for outlook anywhere and for autodiscover.

If I try to add a mailbox to outlook I receive a certificate error which shows the old address, mail.contoso.local...why??

Also, much weirder, I also get a certificate error for autodiscover.contoso.eu, so not exchange.autodiscover.contoso.eu, from an unknown wildcard certificate...where does THAT come from?

Right now I am a bit scared in moving all mailboxes and uninstalling the old exchange. Sorry for the long post, I had many issues with this (as it is my first time doing a migration..or exchange in general) in the last couple of nights. Who needs sleep?

I'm in the process of migrating from E2013 to E2016. I've tried to start my mailbox moves, but any user I migrate just stays in a "syncing" state. I've left batches running for days and it never changes. The users are only test accounts, so there really is almost no data. I am also only doing 1 user at a time until it is successful.

On the E2016 event log, it shows the migration cmdlet was started successfully. No other events after that. On the E2013, no messages there either.

Running the Get-MoveRequest -BatchName "Pilot" | Get-MoveRequestStatistics cmdlet yields nothing. It just returns to a prompt with no output.

I've had to kill the batches forcefully as deleting them also just hangs in a state of deleting.

I've tried restarting a Mailbox Replication as others have suggested and that doesn't do anything either.

Any ideas?

Hi to all and sorry for my English,

*****************************************************************

$createTenantRoot = ($RoleIsDatacenter -or $RoleIsPartnerHosted);
          $createMsoSyncRoot = $RoleIsDatacenter;

          #$RoleDatacenterIsManagementForest is set only in Datacenter deployment; interpret its absense as $false
          [bool]$isManagementForest = ($RoleDatacenterIsManagementForest -eq $true);

          if ($RolePrepareAllDomains)
          {
              initialize-DomainPermissions -AllDomains:$true -CreateTenantRoot:$createTenantRoot -CreateMsoSyncRoot:$cre
ateMsoSyncRoot -IsManagementForest:$isManagementForest;
          }
          elseif ($RoleDomain -ne $null)
          {
              initialize-DomainPermissions -Domain $RoleDomain -CreateTenantRoot:$createTenantRoot -CreateMsoSyncRoot:$c
reateMsoSyncRoot -IsManagementForest:$isManagementForest;
          }
          else
          {
              initialize-DomainPermissions -CreateTenantRoot:$createTenantRoot -CreateMsoSyncRoot:$createMsoSyncRoot -Is
ManagementForest:$isManagementForest;
          }
        ": "Microsoft.Exchange.Management.Tasks.EnumerateRightsFailedException: Rilevato l'errore 0x6BE durante l'enumer
azione dei criteri di gruppo per l'account S-1-5-21-3562906010-3634392973-2603855403-2111.
   in Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object ta
rget, String helpUrl)
   in Microsoft.Exchange.Management.Tasks.InitializeDomainPermissions.AddSaclRight(ADDomain dom, SecurityIdentifier exsS
id)
   in Microsoft.Exchange.Management.Tasks.InitializeDomainPermissions.InternalProcessRecord()
   in Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   in Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePip
elineIfFailed)".

*****************************************************************

where S-1-5-21-3562906010-3634392973-2603855403-2111correspond to "<domain>\Exchange Servers".

Error can be reproduced running 

setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

then "Preparing Organization" fail.

Using domain administrator account and everything work fine even the installation fail.

Where is my mistake?

Thanks in advance for any help

Best regards.

Massimo

Hi,

Having an issue upgrading to Exchange 2013 CU15 on one server thats part of a 4 member DAG 3 of the 4 have already updated successfully. Running Server 2012 R2, its a multirole server and has hybrid config tool running on it.

Execution policy has been set to unrestricted

Setup run from an elevated command prompt

Antivirus disabled

This is the error when updating the mailbox role (other steps completed successfuly)

Error:

The following error was generated when "$error.Clear();

        remove-PerfCounters -DefinitionFileName MailboxTransportSubmissionServicePerfCounters.xml

        new-PerfCounters -DefinitionFileName MailboxTransportSubmissionServicePerfCounters.xml

          " was run: "System.ComponentModel.Win32Exception (0x80004005): The configuration registry key is invalid

   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)

   at Microsoft.Exchange.Management.Tasks.ManagePerfCounters.DeletePerfCounterCategory()

   at Microsoft.Exchange.Management.Tasks.RemovePerfCounters.InternalProcessRecord()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Hey all,

Im stuck in exchange server 2013 CU 23 installation step 10 of 14

I have server 2008 r2

Error:
The following error was generated when "$error.Clear();
          if (!$RoleIsDatacenter -and !$RoleIsDatacenterDedicated)
          {
          $mailboxId = [Microsoft.Exchange.Management.Migration.MigrationBatchIdParameter]::MigrationMailboxName;
          $dispName = "Microsoft Exchange Migration";
          $mbxs = @(Get-Mailbox -Arbitration -DomainController $RoleDomainController -Filter {Name -eq $mailboxId});
          $migrationMailbox = $null;

          if ($mbxs.Length -eq 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
          $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
          if ($dbs.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Retrieving users with Name=$mailboxId.");
          $arbUsers = @(Get-User -Filter {Name -eq $mailboxId} -IgnoreDefaultScope -ResultSize 1);
          if ($arbUsers.Length -ne 0)
          {
          Write-ExchangeSetupLog -Info ("Enabling mailbox $mailboxId.");
          $migrationMailbox = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
          }
          }

Please help

Hi All,

We have on on-prem. Exchange server 2013 server, with DAG configured on the same. when we assigning POP and IMAP services on wildcard certificate it showing below error.

"This certificate with thumbprint ********* and subject '*.yourdomain.com' cannot used for POP SSL/TLS connections because the subject is not a Fully Qualified Domain Name (FQDN). Use command Set-POPSettings to set X509CertificateName to the FQDN of the service."

due to this we are facing certificate error popups at client end where we have configured POP and Imap a/c.

Please help us to resolve this issue.

Regards, Prashant

I have done lots of mess with certs on my exchange environment, as i prepared to migrate 365..

basically, i request help because my outlook is not working (keeps poping for passwords) - pointing to my autodiscoverinternally just not working well.

i have one cas and MB and one MB alone - 2013 exchange (please don't ask why) - had nasty issues due to storage..etc..

when i ran: Get-ExchangeCertificate -DomainName mail.domain.com 

i get two certificates - one purchased online (i want this to be default of all services), and one self-signed one - i would want to remove from reference of -domain (mail.domain.com & autodiscovery.domain.com)

i request for command to force my online cert to over-write the selfsigned one in this case (of owa & autodiscovery).

*** is there a command Enable-ExchangeCertificate -Thumbprint - domain -mail.domain.com, autodiscover.com**

FYI: when i open owa -- i get notified that cert (selfsigned one) is INVALID (by right-clicking on cert info)

thanks

I put this post up on another forum but the advice I was given from from 2008 and there was a note if it had to do with Exchanged 2013, to come here. Here goes ...

We are currently using Exchange 2013 CU14 on Windows 2008 and I'd like to get a fresh install of Exchange on 2012 R2 since 2008 is out of support next month. Since CU14 is no longer available, I was looking to upgrade to CU23 so we would at least be on a supported version of 2013 on a supported server OS.

So far, I have a new 2012 R2 VM that is patched and up to date.

I've run repadmin /syncall on by DCs and they are error free

I've run dcdiag on my DCs and they are  in synch

I ran setup /PrepareSchema /IAcceptExchangeServerLicenseTerms successfully.

I reran the two utilities above as well as repadmin /showreps ... everything cleared.

When I try to run setup with the /PrepareAD parameter, it errors out.

-----------------------------

D:\Exchange Install\Exchange2>setup /PrepareAD /IAcceptExchangeServerLicenseTerms

Microsoft Exchange Server 2013 Cumulative Update 23 Unattended Setup

Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.

Performing Microsoft Exchange Server Prerequisite Check

Prerequisite Analysis COMPLETED

Configuring Microsoft Exchange Server

Organization Preparation FAILED
The following error was generated when "$error.Clear();
initialize-ExchangeUniversalGroups -DomainController $RoleDomainControll
er -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions

" was run: "System.NullReferenceException: Object reference not set to an instan
ce of an object.
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.Crea
teOrMoveEWPGroup(ADGroup ewp, ADOrganizationalUnit usgContainer)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.Inte
rnalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fun
cName, Action func, Boolean terminatePipelineIfFailed)
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage tas
kStage, Action initFunc, Action mainFunc, Action completeFunc)
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()".

The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

----------------------

When I go into ADSI Edit and look at Configuration, Services, Microsoft Exchange properties and drill down to the contents of the OtherWellKnownObjects attribute, I can see the full path of where it is currently set. When I look in AD, I can drill down into the OU and see the Managed Availability Servers group. On the members tab, I can see our existing Exchange server.

Since the OtherWellKnownObjects attribute can't be edited, how can I resolve the issue to get AD Prep'd and Exchange installed? Am I going about this the wrong way? My thoughts were to bring up a second exchange server, migrate the mailboxes and other settings and then make the necessary DNS modifications.

From the other forum I posted in, I was pointed to this link but as I said, it is from 2008.

https://social.technet.microsoft.com/Forums/en-US/ff537d3d-9da8-4a69-ab09-4310726246ca/fail-preparead-object-reference-not-set-to-an-instance-of-an-object

Once on the page, I hovered over this part of the link: "Exchange Previous Versions - Setup, Deployment, Updates, and Migration" and it led me here. 

Would this:

The Microsoft Exchange Security Groups object container needs to be deleted from the advanced view of AD Users and Computers or ADSIEDIT.

make our present server unmanageable?

Any thoughts?

Hi,

We have 4 Exchange 2013 servers prepped ready to migrate from Exchange 2010.

2 of these servers seem to have somehow got corrupt with the OWA virtual Directory configuration.

I ran the remove owa-virtualdirectory command and this seemed to work fine with the directory now not showing up on the server in question from the get-owavirtualdirectory command, the ECP and in IIS.

I then tried to run new-owavirtualdirectory for the default web site but is says it comes back with an error.  Looking in the event logs more detail is given that it cannot create a file if it already exists.  This is pointing to /W3SVC/1/ROOT/owa on the server. I found an article that this is held in the applicationHost file under the inetsrv\config directory and there are entries for all the other virtual directories in there but no the owa one.

Anyone got any ideas how I can get this fixed as I can't start my migration until all of the servers are running properly.

Thanks in a advance.

Rob

Hello!

A few months ago we configured an on premise Exchange 2019 server and then migrated our mailboxes to a 2013 instance(2013 also on premise).

Our 2013 server has been physically powered off for three months. I would like to understand the steps i need to officially decommission it, remove any connections, and uninstall it. My goal would be to then raise the functional level of our domain to 2016 version.

Can somebody please help me understand what the steps are to decommission this 2013 instance?

thanks!

current exch version:

Need Help

Is Exchange 2013 CU 23 Support Domain controller running on Windows Server 2019 (Forest and Domain FL 2012 R2 )?

Thank You

Nur

NUR BD

i can't install Exchange role

One of our exchange server has recently developed a fault the Microsoft Exchange RPC Client Access is failing to start and the following errors are being logged.

We are running Exchange 2013 with the latest CU. Any ideas where to start troubleshooting?

Hello,

Is it possible to perform Hybrid migration without accessing the exchange server? If so, then how it can be possible and what port we need to access?