Article ID: 2850143 - View products that this article applies to.
Consider the following scenario:
Additionally, the following event is logged in the Application log:
Log Name: ApplicationSource: MSExchange ActiveSyncDate: Date and TimeEvent ID: 1044Task Category: RequestsLevel: WarningKeywords: ClassicUser: N/AComputer: COMPUTERDescription:The Client Access server doesn't have the InternalURL value set for the Microsoft-Server-ActiveSync virtual directory. This prevents Exchange ServiceDiscovery from finding the MobileSyncService information for user MBX server. At least one Client Access server in the user's mailbox Active Directory site must have the InternalURL value set. The format for the InternalURL value is https://hostname/Microsoft-Server-ActiveSync
This issue occurs on Android and Windows Phone 8 devices because the list of device types and models that is validated by the DeviceCapability.RedirectDeviceTypes structure does not contain the type and model of your device.
This issue occurs on Apple iOS devices because requests from iOS devices do not contain EAS version information or the device string. Therefore, the DeviceCapability function does not redirect the request.
To resolve this issue, install the following update rollup:
(http://support.microsoft.com/kb/2866475/ )Description of Update Rollup 2 for Exchange Server 2010 SP3
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about this issue, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2746164/ )Description of Update Rollup 6 for Exchange Server 2010 Service Pack 2
2751417For more information about Log Parser Studio, go to the following Microsoft website:
(http://support.microsoft.com/kb/2751417/ )Synchronization fails if you sync an external device to a mailbox through EAS in an Exchange Server 2010 environment
General information about Log Parser Studio 2.0
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Article ID: 2850143 - Last Review: October 10, 2013 - Revision: 2.0