One of my customers had an issue on their Exchange 2010 server regarding Exchange ActiveSync. The mobile device would Autodiscover the settings however it would fail to synchronise email. After investigating the issue I quickly isolated the issue to the users Active Directory user account. This was determined after I recreated the users mailbox by exporting to PST, disabling the mailbox, creating a new mailbox then reimporting the mailbox content.
I used the following command in PowerShell to test the users ActiveSync configuration status.
Test-ActiveSyncConnectivity -MailboxCredential (Get-Credential domain\username) -UseAutodiscoverForClientAccessServer
The command failed.
![]()
I then piped the output to a format list function to provide more details about the error received.
![]()
The error received was as follows:
"[System.Net.WebException]: The remote server returned an error: (500) Internal Server Error."
As I knew the problem was not to do with the mailbox contents as I had recently recreated the users mailbox, and this user was the only user effected by the issue, it had to be a problem with the Active Directory user account itself.
After investigating the user account I noticed the account was no longer inheriting permissions in Active Directory. After re-enabling inheritable permissions, this resolved the problem.
![]()
I used the following command in PowerShell to test the users ActiveSync configuration status.
Test-ActiveSyncConnectivity -MailboxCredential (Get-Credential domain\username) -UseAutodiscoverForClientAccessServer
The command failed.
I then piped the output to a format list function to provide more details about the error received.
The error received was as follows:
"[System.Net.WebException]: The remote server returned an error: (500) Internal Server Error."
As I knew the problem was not to do with the mailbox contents as I had recently recreated the users mailbox, and this user was the only user effected by the issue, it had to be a problem with the Active Directory user account itself.
After investigating the user account I noticed the account was no longer inheriting permissions in Active Directory. After re-enabling inheritable permissions, this resolved the problem.
