MSExchangeGuru.com

Learn Exchange the Guru way !!!

 

Exchange Server 2013 Troubleshooting notes

These are my troubleshooting notes. Thought it could benefit the community.

Error when installing Exchange Server 2013 CU 7:

Issue:

When installing Exchange 2013CU7, it fails to update with the following error: We will not be able to uninstall or continue further with the installation:

Exception : Microsoft.Exchange.Management.Deployment.ScriptExecutionException: The following error was generated when “$error.Clear();
          Enable-RpcOverTcpPortScaling; 
          Enable-ExtendedTcpPortRange
        ” was run: “System.Management.Automation.ActionPreferenceStopException: The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: The registry key at the specified path does not exist.
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)”. —> System.Management.Automation.ActionPreferenceStopException: The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: The registry key at the specified path does not exist.
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
— End of inner exception stack trace —
at Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.InternalExecuteScript(String script, Boolean handleError, Int32 subSteps, LocalizedString statusDescription)
at Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.ExecuteScript(String script, Boolean handleError, Int32 subSteps, LocalizedString statusDescription)
at Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.GenerateAndExecuteTaskScript(InstallationCircumstances installationCircumstance)
[01/30/2015 19:47:58.0635] [1] [ERROR] The following error was generated when “$error.Clear();
. “$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1″;
Enable-RpcOverTcpPortScaling;
Enable-ExtendedTcpPortRange
” was run: “System.Management.Automation.ActionPreferenceStopException: The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: The registry key at the specified path does not exist.
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)”.
[01/30/2015 19:47:58.0635] [1] [ERROR] The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: The registry key at the specified path does not exist.
[01/30/2015 19:47:58.0635] [1] [WARNING] An unexpected error has occurred and a Watson dump is being generated: The following error was generated when “$error.Clear();
. “$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1″;
Enable-RpcOverTcpPortScaling;
Enable-ExtendedTcpPortRange
” was run: “System.Management.Automation.ActionPreferenceStopException: The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: The registry key at the specified path does not exist.
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)”.

Resolution:

  • Check if the registry key is present “HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Rpc” and a value EnableTcpPortScaling. If this registry key is missing, please try to create it. Go to HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Rpc  -> Click Edit -> New -> DWORD -> enter EnableTcpPortScaling -> double click it and change the value data to 1.
  • Disable any third party security software ( Symantec Endpoint, Sopohs etc.) & try installing it again

Unable to initialize the Microsoft Exchange Information Store service. – Error 0x96f. Exchange fails to start with the following error:”Unable to initialize the Microsoft Exchange Information Store service.   – Error 0x96f. “    

Resolution:

  • Re-enabling IPv6.

https://social.technet.microsoft.com/Forums/office/en-US/b89d34a7-c8c8-4433-89ab-90114d1b7012/unable-to-initialize-the-microsoft-exchange-information-store-service-error-0x96f?forum=exchangesvrdevelopment

Getting error “Multiple potential Migration mailboxes were found for this organization. Please specify a particular Partition mailbox to use” when trying to set up mailbox migrating through EAC.

When trying to migrate mailbox from Exchange 2010 to Exchange 2013 using Exchange EAC we get the following error in the migration wizard:

“Multiple potential Migration mailboxes were found for this organization. Please specify a particular Partition mailbox to use.”

Resolution:

  • It is recommended to remove all migrated data first.
  • To remove run the following command:

    Remove-MoveRequest 

    Identity: Mailbox@ domain.com

    Select [A]

  • Then using the following command try to migrate the mailbox:

    ‘mail@domain.com’ | New-MoveRequest -TargetDatabase “Database_Name” -BadItemLimit 200 (if you have corrupted mails)

 

Exchange management shell on Exchange 2013  server locally it would fail to connect locally with error:


Failed to connect to an Exchange server in the current site.x.x.x. New-PSSession : [mail.abc.com] Connecting to remote server server.domain.com failed with the following error message :WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer server.domain.com

Issue:

When opening Exchange Management Shell in Exchange 2013 using the Administrator account it fails with the following error. However we can create a new account in the Organization Management Permission it will connect successfully.

Failed to connect to an Exchange server in the current site.

Enter the server FQDN where you want to connect.: SERVER.DOMAIN.COM

VERBOSE: Connecting to mail.*.*.

New-PSSession : [server.domain.com] Connecting to remote server SERVER.DOMAIN.COM failed with the following error message :

WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer Server.domain.com. Verify that the computer exists on the network and that the name provided is spelled correctly. For more information, see the about_Remote_Troubleshooting Help topic.

At line:1 char:1

+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException

    + FullyQualifiedErrorId : NetworkPathNotFound,PSSessionOpenFailed

[PS] C:\Windows\system32>

Resolution:

  • Check if there is any permission missing for the Administrator account.
  • Try deleteting the Administrator profile using the following steps:
  1.     Launch=> Control Panel => System and Security => System
  2.        In the dialog click => Advanced system settings
  3.        System Properties dialog will be displayed.
  4.        Make sure you are in the “Advanced” register
  5.        In User Profiles click =>Settings
  6.        The “User Profiles” dialog is displayed
  7.        Select administrator account and Delete it.

Exchange Replication service crashes in Exchange Server 2013 with even ID: 4999 & 4401

Issue:

The Microsoft Exchange Replication service crashes frequently after installing Cumulative Update 6 for Exchange Server 2013. We get the following event ID:

Log Name: Application
Source: MSExchange Common
Event ID: 4999
Task Category: General
Level: Error
Description:
Watson report about to be sent for process id: 14020, with parameters: E12IIS, c-RTL-AMD64, 15.00.0995.029, msexchangerepl, M.Exchange.Common, M.E.C.H.DatabaseFailureItem.Parse, System.ArgumentOutOfRangeException,version.
ErrorReportingEnabled: True

Log Name: Application
Source: MSExchangeRepl
Event ID: 4401
Task Category: Service
Level: Error
Description:
Microsoft Exchange Server Locator Service failed to find active server for database. Error: An Active Manager operation failed. Error: Invalid Active Manager Configuration. Error: Active Manager hasn’t completed configuration initialization.

Resolution:

  • Installing Cumulative Update 7 for Exchange Server 2013
  • Or run the following command in the Exchange server using command prompt:

    Wevtutil.exe cl “Microsoft-Exchange-MailboxDatabaseFailureItems/Operational”

Getting errors accessing Exchange Management Shell, Exchange Admin Console, Exchange Control Panel, or OWA in Exchange Server 2013

Issue:

  • When users try to access EAC it fails with the following error:

    403 Sorry! Access denied L

    You don’t have permission to open this page. If you’re a new user or were recently assigned credentials, please wait 15 minutes and try again.

    We might get the following event ID:

    Log Name:      Application
    Source:        MSExchange Control Panel
    Event ID:      4
    Task Category: General
    Level:         Error
    Description:
    Request for URL ‘https://server.domain.com:444/ecp/default.aspx(https:/CASserver.domain.com/ecp/)’ failed with the following error:
    Microsoft.Exchange.Configuration.Authorization.CmdletAccessDeniedException: The user “domain.com/Computers/CAS1” isn’t assigned to any management roles.

  • When users tries to access OWA it fails with the following error:

    L Something went wrong

    A problem occurred while you were trying to use your mailbox.

  • Also when trying to access the Exchange management Shell it fails with the following error:

    VERBOSE: Connecting to CasServer.domain.com.
    New-PSSession : [CASserver.domain.com] Connecting to remote server CASserver.domain.com failed with the following error
    message : [Server= CASserver ,RequestId=xxxxxx,TimeStamp=xxxxxx] Access is
    denied.

    Resolution:

    • Remove the computer object from the restricted group.
    • You can run the following command to view all the groups denied permission

      Get-ADPermission -Identity <ExchangeServer> | where {($_.ExtendedRights -like “ms-Exch-EPI-Token-Serialization”) -and ($_.Deny -like “True”)} | ft -autosize User,ExtendedRights

Messages are stuck in a remote delivery queue in a Microsoft Exchange Server with event ID:1035 & queue viewer shows: 454 4.7.0 Temporary authentication failure.

Issue:

When few mails are stuck in the remote delivery queue with the following error: In Addition to it , event id: 1035 keeps logging.

451 4.4.0 Primary target IP address responded with: "454 4.7.0 Temporary authentication failure." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.
Event Type: Error
Event Source: MSExchangeTransport
Event Category: SmtpReceive 
Event ID: 1035
Description:
Inbound authentication failed with error IllegalMessage for Receive connector Default <Server>. The authentication mechanism is ExchangeAuth. The source IP address of the client who tried to authenticate to Microsoft Exchange is xxx.
Resolution:
  • Make sure that the clock on both servers and domain controllers display the same time.
  • Check the Service Principal Name (SPN) for SMTPSVC is registered correctly on the target server. You can use SetSPN –L <Exchange server name> . Also its advisible to verify if there are any duplicate SPNs using the command SetSPN –x
  • Check if ports required for Kerberos are enabled. We can add the following registry key:

    Open Regedit , navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters . Click New => DWORD Value=> enter the value as LogLevel => now right click & modify. => Edit DWORD value => Decimal. Add the Value data => 1. & click ok.

The Exchange Server 2013 Client RPC Service keeps on crashing.

Issue:

The Exchange server Client RPC service keeps crashing after a server reboot with Event ID 1006, Event ID 1025, Event ID 3010, Event ID: 1028

Resolution:

  • Run the following command in Exchange Management Shell :

Set-RpcClientAccess -Server Bucksrv70 -EncryptionRequired $false

Set-RpcClientAccess -Server Bucksrv70 -EncryptionRequired $true

(These commands rebuilt the configuration file for the RPC Client Access Connector)

  • Now Start the Service.

 

Unable to Start Exchange server Mailbox service using NT AUTHORITY\Network Service.

Issue:

When installing Exchange 2013, Mailbox service fails to start using NT AUTHORITY\Network Service. When checking Event viewer we will see a message exchange server could not access AD using account NT AUTHORITY\Network Service.

Resolution:

  • Check the permission in the ADSI EDIT & give read permission to this security groups : Authenticated users and Network Service account .

Updating Receive Connector in Exchange server gets overwritten by TMG

Issue:

If Exchange 2010 Server Edge role is installed with TMG 2010 & Forefront Protection for Exchange in the same machine, the Edge servers Default receive connector gets disabled.

Resolution:

  • Enable TMG’s Integration mode to resolve the issue. This issue is caused by the Forefront TMG. During the TMG set up property IntegrationEnabled of the SmtpProtectionConfiguration COM object is wrongly set to TRUE by default.
  • If you don’t prefer to use the intergartion mode, you can workaround by setting the Email Policy Integration mode to Disabled. ( in the TMG Console go to Troubleshooting => on the right pane click Control Email policy Configure Integration => Set the Email policy Integration mode to “Disabled“, save settings.

After running Windows Update in Exchange Server 2013 Event ID: 23 & Event ID: 258 appear.

Issue:

After running Windows Update in Exchange Server 2013, we keep getting Event ID 23 & Event ID 258. In addition to it we will not be able to open the ECP & will not be able to open Exchange Management Shell:

 


Microsoft.Exchange.Diagnostics.SetupVersionInformationCorruptException:
Unable to determine the installed file version from the registry key
‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine’. at
Microsoft.Exchange.Diagnostics.ExchangeSetupContext.get_PSHostPath() at
Microsoft.Exchange.Configuration.Authorization.InitialSessionStateBuilder.InitializeWellKnownSnapinsIfNeeded(ExchangeRunspaceConfigurationSettings
settings, Boolean isPowerShellWebServiceSession) at
Microsoft.Exchange.Configuration.Authorization.InitialSessionStateBuilder.Build(List`1
allCmdlets, List`1 allScripts, ExchangeRunspaceConfiguration runspaceConfig) at
Microsoft.Exchange.Configuration.Authorization.ExchangeRunspaceConfiguration.CreateInitialSessionState()
at
Microsoft.Exchange.Configuration.Authorization.ExchangeAuthorizationPlugin.GetInitialSessionStateCore(PSSenderInfo
senderInfo) at
Microsoft.Exchange.Configuration.Authorization.ExchangeAuthorizationPlugin.<>c__DisplayClass4.<GetApplicationPrivateData>b__3()
at
Microsoft.Exchange.Configuration.Authorization.AuthZLogHelper.HandleExceptionAndRetry[T](String
methodName, Func`1 func, Boolean throwException, T defaultReturnValue)

Resolution:

  • Open Regedit & Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1.
  • Create a Key named “PowerShellEngine” .
  • Create all the following 6 Strings under “PowerShellEngine” and copy the values from Windows Server 2008: ApplicationBase, ConsoleHostAssemblyName, ConsoleHostModuleName, PowerShellVersion, PSCompatibleVersion and RuntimeVersion.
  • Restart the server after creating the Key and Strings.

Unable to access Exchange Management Shell after migrating CAS role to another Server.

Issue:

After moving the CAS server role to HUB/MAILBOX server to have all roles in a single server, getting the following error when trying to access the Exchange Management Shell:

IIS 7.5 Detailed Error – 500.19 – Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell-Proxy\web.config

 

Resolution:

  • Install WinRM-IIS-Ext feature .

Remove- InboxRule not working

Issue:

When trying to remove some Inbox rules, Exchange won’t allow & says there are duplicate inbox rules. When using the following command:

Remove-InboxRule -Mailbox Joe@Contoso.com -Identity “Project-MoveToFolderB”

Resolution:

Running the following command fixes the issue:

$mailboxes = Get-Mailbox -Organization myorganization

$mailboxes | % { Get-InboxRule -Mailbox $_.alias | ?{ $_.Forwardto -match “email@domain.com” } | Remove-inboxRule }

 

Ratish Nair

Microsoft MVP | Exchange Server

Team @MSExchangeGuru

 

 

 


Leave a Reply

migrate exchange to office 365

Categories

Archives