MSExchangeGuru.com

Learn Exchange the Guru way !!!

 

Exchange 2010/2013 – Issues and solutions

Sharing my troubleshooting notes

Single User Outlook 2013 new setup fails on “Logging on to the mail server”

Issue:

Issue with one user not able to login to outlook 2013. User attempts to connect & it fails with the following error:

“The Connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action”. The user is unable to access outlook but can access OWA to check mails.

Resolution:

=> Recycle AppPools for both Autodiscover and RPCProxy.

=> Run Get-CasMailbox <user> | fl . Check if MAPIBlockOutlookRpcHttp is set to true.

=> If it is set to true , run Set-CASMailbox <user> -MAPIBlockOutlookRPCHttp $false.

 

========================================================

 

Event ID 4027 MSExchange ADAccess Exchange 2013

Issue: Getting event ID 4027 on Exchange 2013 server.

 Log Name:      Application

 Source:        MSExchange ADAccess

 Event ID:      4027

 Task Category: General

 Level:         Error

 Keywords:      Classic

 User:          N/A

 Description:

  Error Details

  System.ServiceModel.EndpointNotFoundException: Could not connect to 

net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of

00:00:02.0280035. TCP error code 10061: No connection could be made because the target machine actively refused it

127.0.0.1:890.  —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively

refused it 127.0.0.1:890

    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)

    at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)

    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)

 

Resolution:

=> Enable IPv6.

 

========================================================

 

Exchange 2013 CU2 “old mail.Queue” growing & occupying more space.

Issue:

On Mailbox servers in Queue folder there are multiple folders generated with name “messaging old” with date and inside there is old “mail.queue file” on the mailbox server causing disk space issue. (checked pipeline tracing and transport dumpster setting and its in default setting) You will see Messaging.old-201503231091 folder taking up lot of space in C drive.

Resolution:

=> Rename the folder & check if there is any impact.

=> It’s safe to delete the Messaging.old folder. It won’t cause any issues.

 

========================================================

 

451 4.4.0 Primary target IP address responded with: “421 4.4.5 Service not available, connection deferred

Issue:

Issue with sending mails to one specific domain in Exchange 2013 server. Mail flow for a specific domain fails with the following error:

Remote Server at mail.server.com

 (xxx.xxx.xxx.xxx) returned ‘451 4.4.0 Primary target IP address responded with:

 “421 4.4.5 Service not available, connection deferred.” Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was xxx.xxx.xxx.xxx:25′

Resolution:

=> Try sending email from a public email a/c like gmail.com to the problematic domain & see if the mail goes thru.

=> Try running Set-SendConnector -Identity “<SendConnectorName>” -IgnoreSTARTTLS $true & check.

=> Check the Firewall & network device to make sure if they are blocking it.

 

========================================================

 

Unable to move mailbox to new database in Exchange 2010 server.

Issue:

When migrating mailboxes to new database in Exchange 2010 SP3 RU6, some of them fails with the following error:

 {MapiExceptionNoAccess: Unable to query table rows. (hr=0x80070005, ec=-2147024891)

 ——–

 Operation: IDestinationMailbox.CreateFolder

 OperationSide: Target

 Primary (e8d46f09-1e95-4714-b9be-054c9793e96c)

 Folder: ‘Drafts’, entryId [len=46, data=000000004CAE01205CB53F48985FAD69EC75CAD90100E29AB6F8D3BA694C8DD7E55

 D2CE8175100000004A55B0000], parentId [len=46, data=000000004CAE01205CB53F48985FAD69EC75CAD90100E29AB6F8D3BA69

 4C8DD7E55D2CE817510000000562D80000]

 FailIfExists: False

 ——–

 Folder: ‘/Top of Information Store/Drafts’, entryId [len=46, data=000000004CAE01205CB53F48985FAD69EC75CAD90

 100E29AB6F8D3BA694C8DD7E55D2CE8175100000004A55B0000], parentId [len=46, data=000000004CAE01205CB53F48985FAD69

 EC75CAD90100E29AB6F8D3BA694C8DD7E55D2CE817510000000562D80000]

 

Resolution:

=> Exported mailbox to PST.

=> Delete mailbox, create a new mailbox & import the PST.

=> Add X500 address – to get rid of NDR messages cause of new mailbox legacyExchangeDN.

========================================================

 

Find oldest email date on a particular mailbox through exchange management shell command ?

Issue:

How to find oldest email date on a particular mailbox through exchange management shell command ?

Resolution:

Get-MailboxFolderStatistics -IncludeOldestAndNewestItems -Identity <mailbox> |

    Where OldestItemReceivedDate -ne $null |

    Sort OldestItemReceivedDate |

    Select -First 1 OldestItemReceivedDate

 

========================================================

 

WebServices connectivity (Internal) transaction failure – The credentials can’t be used to test Web Services

 

Issue: Unable to test web services or outlook connectivity, keep getting an error stating “credentials cannot be used”.

When running test outlook connectivity we get the following error in CAS server :

 

Verbose: Target User = ‘extest_1eb30811639a4@domain.com

 Verbose: Resolved server.  Server Name = ‘CASSERVER’, Server FQDN= ‘CASSERVER.domain.com

 Verbose: Selected RPC Proxy authentication method = ‘NTLM’

 Verbose: Based on RpcTestType, the cmdlet needs to dynamically look up the endpoint that uses this server as reference point.

 Verbose: Target Client Access server = ‘CASSERVER.domain.com

 Verbose: Based on RpcProxyTestType, the cmdlet needs to dynamically look up the endpoint that uses this server as

reference point.

 Verbose: Target Client Access server = ‘CASSERVER.domain.com

 Verbose: Using connection parameters : ‘domain.comextest_1eb30811639a4: RpcProxy/RPC-over-HTTP,

[CASSERVER.domain.com/NTLM]’

 Verbose: Pinging RpcProxy at the following URL:  https://CASSERVER.domain.com/rpc/RpcProxy.dll.

 Verbose: An unexpected exception occurred while pinging RpcProxy. The most common reason for this occurring is that the

IIS DefaultAppPool isn’t running. Exception: The remote server returned an error: (401) Unauthorized.

 Verbose: Mailbox = ‘domain.comextest_1eb30811639a4′, Owner = ‘/o=company/ou=Exchange Administrative Group

(FYDIBOHF23SPDLT)/cn=Recipients/cn=extest_1eb30811639a4′

 

 Diagnostic command: “Test-OutlookConnectivity -RpcProxyTestType:Internal -RpcTestType:Server -TrustAnySSLCert:$true –

MonitoringContext:$true”

 TimeWindowStart: 2015-03-18T07:10:07.0437501+02:00

 TimeWindowEnd: 2015-03-18T07:23:27.0437500+02:00

 TimeFirst: 2015-03-18T07:10:07.0437501+02:00

 TimeLast: 2015-03-18T07:15:08.0145501+02:00

 Count: 2

 EventSourceName: MSExchange Monitoring OutlookConnectivity Internal

 

Resolution:

 

=> Deleted the ac extest_1eb30811639a4 & recreated it.

 

========================================================

 

Exchange 2013: Public Folder Mailbox cannot be deleted:”Cannot open Mailbox”.

 

Issue:

Unable to delete the public folder Mailbox we get the following error. Also the same happens when trying to delete using the Shell & web interface.

“Cannot open mailbox /o=Test Lab/ou=Exchange Administrative Group … /cn=Servers/cn=EXServer/cn=Microsoft System Attendant”

Resolution:

=> Run Remove-Mailbox with -force parameter.

 

========================================================

 

Remove-MailboxDatabase fails

Issue:

Migrating from Exchange 2013 to a new Exchange 2013. When trying to run Remove-MailboxDatabase it fails with the following error:

VERBOSE: [16:02:40.757 GMT] Remove-MailboxDatabase : Mailbox with DistinguishedName <<omitted>> is still present in this database.

 

Resolution:

=> Found users had wrong attribute set.

=> Ran the below command to fix it:

PS AD:DC=mydomain,DC=local> $usersToChange = dir -rec | ? {$_.objectClass -eq “user”} | ? {(get-itemproperty -name

msExchArchiveDatabaseLink -path $_.pspath) -like “*Mailbox Database 1096099116*”}

PS AD:DC=mydomain,DC=local> $usersToChange | foreach {Clear-ItemProperty -Name msExchArchiveDatabaseLink -Path $_.PSPath -verbose}

 

========================================================

 

After migration from exch 2007 to 2013 “show this folder as an e-mail address book not available” client 2007

Issue: After we migrated our exchange from 2007 to 2013 and we are facing some issues with our public folders

we have an address book at our public folders (migrated from 2007)  when i look for “”show this folder as an e-mail address book” tab on outlook 2007 clients its missing , when i look for it on outlook 2013 clients its there, why?

Resolution:

=> It is by design that there is no Outlook Address Book tab with the Show this folder as an e-mail Address Book check box for Public Contact in Outlook 2007. Need to update the Outlook 2007 to Outlook 2010 or higher version as a workaround.

 

========================================================

 

Cannot create a new Offline adressbook

Issue : When creating new OAB & arbitration mailbox using the following command it fails:

Get-Mailbox -Arbitration | where {$_.PersistedCapabilities -like “*oab*”} | ft name,servername

After running the above command & while running Update-OfflineAddressBook -Identity “OAB-FAB” it fails with the following error:

+ CategoryInfo          : InvalidResult: (OAB-FAB:OfflineAddressBookIdParameter) [Update-OfflineAddressBook],

LocalizedException

    + FullyQualifiedErrorId : [Server=EXCH-SRV,RequestId=84bb0fb1-d6dd-4718-a704-4e9a20e178b6,TimeStamp=19.02.2015

12:07:00] [FailureCategory=Cmdle

   t-LocalizedException] 12FE7FE1,Microsoft.Exchange.Management.SystemConfigurationTasks.UpdateOfflineAddressBook

    + PSComputerName        : EXCH=SRV.xxx.local

 

Cannot create a new Offline Address Book “OAB” This may be caused to two reasons: the service “Mailbox Assistant service.” is not started on “EXCH-SRV.xxx.local” server or you do not have permission to perform this operation.

 

Resolution:

 

Run the following command instead:

1. New-OfflineAddressBook -Identity “OAB-FAB” –GeneratingMailbox “CN= BK Arbitration OAB,CN=Users,DC=contoso,DC=com” –AddressLists “Default Global Address List”

2. Update-OfflineAddressBook -Identity “OAB-FAB”

========================================================

 

Move Mailbox error

 

Issue: Tried moving mailboxes from 2010sp3 to 2013sp1. All mailboxes moved except two & we get the following error

One mailbox error message is “Error: MigrationPermanentException: Mailbox ‘AAA’ has a completed move request associated with it. Before you create a new move request for the mailbox, run the Remove-MoveRequest cmdlet to clear the completed move request.

Another mailbox error message is “Error: MigrationPermanentException: The Mailbox database “BBB”is not the same version as the cmdlet.

Resolution:

 

Run the following command:

New-MoveRequest “username” -TargetDatabase “database” -BadItemLimit 50 -Verbose

========================================================

 

Cannot update to CU7 – remote registry error 

 

Issue: When trying to install CU7 from CU6 we get the following error:

“There was a problem accessing the registry on this computer. This may happen if the Remote Registry service is not running. It may also indicate a network problem or that the TCP/IP NetBIOS Helper service is not running”.

Resolution:

 

 =>Start the following services to check this issue.

=>”Remote Registry” Service

=>”TCP/IP NETBIOS Helper” service

=>Computer Browser” service and setting it to “Automatic”

========================================================

 

Exchange 2013 CU7 Installation crash on Mailbox role: Transport Service.

 

Issue:

Started installing CU7 & it fails with the following error:

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

 

            # Apply XML Transforms to FIPS configuration file if schema changed Write-ExchangeSetupLog -Info “Applying XML Transforms to FIPS configuration”;

 $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, “FIP-FSbin”);

[Reflection.Assembly]::LoadFile([System.IO.Path]::Combine($FipsBinPath, “FSCConfigurationServerInterfaces.dll”));

            [Reflection.Assembly]::LoadFile([System.IO.Path]::Combine($FipsBinPath, “FSCConfigSupport.dll”));

 

            $configServer = New-Object Microsoft.FSC.Configuration.ConfigManagerClass;

            if(! $configServer)

            {

              Write-ExchangeSetupLog -Error “Configuration Server object could not be created.”;

            }

            else

            {

              try

              {

                $configServer.Upgrade();

                Write-ExchangeSetupLog -Info “Configuration.xml was upgraded successfully”;

              }

              catch

              {

                Write-ExchangeSetupLog -Error “Upgrade of Configuration.xml was unsuccessfull, $_”;

 

 

# Stop the process if it is still running

# We silently continue because if process has already exited, Stop-Process will throw error

# Error is non-terminating and so can be suppressed

Stop-Process -processname FSCConfigurationServer -Force -ErrorAction SilentlyContinue;

 

         }

          ” was run: “System.Exception: Upgrade of Configuration.xml was unsuccessfull, Exception calling “Upgrade” with

“0” argument(s): “Root element is missing.”

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target,

Boolean reThrow, 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)”.

 

Resolution:

1.Go to “C:Program FilesMicrosoftExchange ServerV15FIP-FSData”

2.Deleted the file “configurationServer.xml” and renamed “configurationServer.xml.back” to configurationServer.xml.

3.Then try to re-install Exchange Mailbox Server.

========================================================

 

After setup of Exchange2013 Exchange Management Shell fails

 

Issue:

Upgrading from Exchange 2007 to Exchange 2013. After upgrading to Exchange 2013 , we get the following error in the Exchange Management Shell:

 

VERBOSE: Connecting to server2013.domain.com.

                                       New-PSSession : [server2013.domain.com] Processing data from remote server

server2013.domain.com failed with the

                                       following error message:

[ClientAccessServer=SERVER2013,BackEndServer=SERVER2013.domain.com,RequestId=2d2dcfef-3753-4c3e-b

                                       207-3845ca5d6833,TimeStamp=2/23/2015 08:02:10 AM]

                                       [AuthZRequestId=45093630-4a0f-4c08-a5ff-4d6bf230c5b5][FailureCategory=AuthZ-

SetupVersionInformationCorruptException]

                                       Unable to determine the installed file version from the registry key

                                       ‘HKEY_LOCAL_MACHINESOFTWAREMicrosoftPowerShell1PowerShellEngine’. 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], PSRemotin

                                          gTransportException

                                           + FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed

                                       WARNING: No Exchange servers are available in the Active Directory site A.

Connecting to an Exchange server in another

                                        Active Directory site.

 

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

                                       Enter the server FQDN where you want to connect.

 

Resolution:

 

Moving these keys from other servers or creating all the 6 strings manually should solve this issue.

1.Created the Key “PowerShellEngine” under HKEY_LOCAL_MACHINESOFTWAREMicrosoftPowerShell1.

2.Created all 6 Strings under “PowerShellEngine”

•ApplicationBase    (C:WindowsSystem32WindowsPowerShellv1.0)

•ConsoleHostAssemblyName    (Microsoft.PowerShell.ConsoleHost, Version=1.0.0.0,

Culture=neutral,PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=msil)

•ConsoleHostModuleName    (C:WindowsSystem32WindowsPowerShellv1.Microsoft.PowerShell.ConsoleHost.dll)

•PowerShellVersion    (2.0)

•PSCompatibleVersion    (1.0, 2.0)

•RuntimeVersion    (v2.0.50727)

 

Ratish Nair

Microsoft MVP | Exchange Server

Team @MSExchangeGuru.com

2 Responses to “Exchange 2010/2013 – Issues and solutions”

  1. Vishal Says:

    Remove alert | Edit | Change type
    Question
    You cannot vote on your own post
    0
    Hi All,

    So after reading various blogs and posts – I finally managed to get Exchange 2013 installed and set up correctly in co-existence environment along with Exchange 2010. Everything is working fine – emails are flowing in both the directions internally and externally. However, I’ve got a minor issue to which I need some advise to look into right direction.

    When I move the mailbox from Exchange 2010 to Exchange 2013, once the move is completed – if mailbox is opened in Outlook 2007, users get notification – “The exchange administrator has made the changes and requires you to quit and restart the outlook”. When you click OK, it’s trying to configure the profile and open the outlook – but gives another message – “Cannot open your default e-mail folder. Microsoft Exchange is not available. Either there are network problems or the Exchange computer is down for maintenance”. When we click OK on message – it quits the outlook. When I load the outlook 2007 again, the same message appears.

    However, I can go and setup the outlook profile manually for the mailbox which is migrated to Exchange 2013 and it works fine. But it will be a painful process to configure the profile manually for thousands of users.

    What could be the root cause of this problem? and how can I fix it?

    Await to hear from you guys.

    Regards,

    Vishal.

  2. Prabhat Nigam Says:

    Vishal,

    Before migrating the user mailbox make sure 2007 user is using outlook anywhere in the fast network connection as well. This should reduce some issues.
    It is also recommended to run the migration in the night to cover any replication delays.

Leave a Reply

ad

Categories

Archives