Home > Exchange, Exchange 2010, Exchange 2010 AKA E14, Exchange and UC > #Exchange #Exchange2010 Activesync not working “unable to find server” and then this shows up in the http logs “LdapC1_LdapL16_Error:TiSyncStateLocked_Mbx:2003server”.

#Exchange #Exchange2010 Activesync not working “unable to find server” and then this shows up in the http logs “LdapC1_LdapL16_Error:TiSyncStateLocked_Mbx:2003server”.

well, this looks like something is not correct either with auth. config on the vdir or the mailbox home attribute, James lou posted a nice troubleshooting guide, I am posting it here for reference (those steps can be used with general activesync troubleshooting:

  • confirm that the ActiveSync works when you use the exchange 2003 URL directly
  • check if there’s any related event error in the application log on the CAS server after reproduced the issue
  • verify if the issue only happens to IPhone. You can use the windows mobile emulator for testing

Windows Mobile 6.1.4 Emulator Images

Users with mailboxes on an Exchange 2003 server who try to use Exchange ActiveSync through an Exchange 2010 Client Access server will receive an error and be unable to synchronize unless Integrated Windows authentication is enabled on the Microsoft-Server-ActiveSync virtual directory on the Exchange 2003 server

———-Refer to <Transitioning Client Access to Exchange Server 2010>

install the required hotfix and change the related attribute

reproduce the issue on the Remote Connectivity Analyzer for further troubleshooting information

Possible cause: ExchangeVDir settings exist on exchange 2003 BE server as KB 817379 has been applied before


1.      Please refer to method 2 to revert the setting in the KB 817379 to remove the registry setting about ExchangeVDir

2.      Disable Forms-based authentication on the BE server

3.      Remove “Require SSL” from /exchange virtual directory

4.      Remove the exchange-oma virtual directory

Possible cause: The server name in the “msexchhomeservername” attribute doesn’t match with the server name in the “Homemdb” attribute of the problematic user


1.      Launch ADSI Editor, and then find the problematic user in domain partition

2.      Right-click user object, and then click on properties

3.      Check the attribute “msexchhomeservername” and “homemdb” and verify that the server name match

E.g. the server name is CLT-E2k7 in the example mentioned below:

Msexchhomeservername: /o=Fourthcoffee/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CLT-E2K7

Homembd: CN=Mailbox Database,CN=First Storage Group,CN=InformationStore,CN=CLT-E2K7,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Fourthcoffee,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=fourthcoffee,DC=com

4.      If the server name in “msexchhomeservername” attribute is different than the server name in the “Homemdb” attribute, change the server name of the msexchhomeservername attribute to match the server name in the “Homemdb” attribute


  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: