We've been quite happily running Activesync on our mobile phones for a while now, however just before midday on the 15th May our phone synchs stopped.
We rebooted the servers, checked the permissions on the IIS tree, and eventually found that OMA was broken for no apparent reason with the following :
Server Error in '/OMA' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration> |
Doing some research around the net I found an article which suggested rolling back the .NET framework to 1.1.4322 this didn't work, so I've rolled it forward again to 2.0.50727 and it still doesn't work.
Anyone else have a suggestion to what I should be looking at to get it back up and running again?