Just did a Domain Name Rename, (I'm crazy I know), and now trying to settle the lagging issues. Network is a Server 2003 Forest with Exchange 2003 SP2. Most annoying is that ActiveSync does not seem to be working, while OWA seems to be up and functional. Running the activesync test we get the following failure (See below). Everything else passes. Eventvwr is giving errors of "Following client routing node failed to connect to its resvc D:\Program Files\Exchsrvr\bin\emsmta.exe and "Following client routing node failed to connect to its resvc C:\WINDOWS\system32\wbem\wmiprvse.exe" This KB http://support.microsoft.com/kb/886346/ seems to be close, but didn't fix the problem. Same with http://support.microsoft.com/default.aspx?scid=kb;en-us;841576, the metabase is intact and not corrupted. Everything else in the domain seems to be functioning properly, except for activesync. Any help would be appreciated. The error the phones are getting is Result: The server could not be reached. This can be caused by temporary network conditions. Support Code: 0x80072EE2. Attempting FolderSync command on ActiveSync session FolderSync command test failed Tell me more about this issue and how to resolve it Additional Details Exchange Activesync returned an HTTP 500 response.

I would ask you to run EXBPA and see if it can find out anything Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

Hi, Please download ExBPA to have a health check for the Exchange Server. Could you please describe your environment for us? Do you have a front-end server? Please try the suggestion in KB817379 and let us know the result. Regarding error 0x80072ee2, its a temporary network issue. Lets focus on the HTTP 500 error which we got at Exchange Remote Connectivity Analyzer website. Thanks, Elvis

This was resolved by uninstalling IIS and reinstalling, then repair installing Exchange. Using Testexchangeconnectivity still fails now on a different command, GetItemEstimate, however users phones are now syncing without issue. @Elvis, I did try that KB and it did not change the error I was getting. Thank you both for your help! The environment was just one exchange server that was also a DC as well as another 2003 box running as a DC.

Be glad that you have resolved the issue. Thank you for your sharing!