I have a single Power Edge Server 2900 4GB RAM Windows Server 2008 Enterprise (Running as the DC, File Server, etc) Exchange Server 2007 on the same server as a simple deployment, no edge transport A Unix firewall with NAT publishing necessary ports to the single server. Everything has been working fine for a week, got a Godaddy.com Turbo SSL Certificate and OWA and ActiveSync were working like a charm on all the Windows Mobile 5 and 6 phones. I got a call from this client Monday saying that around 5:12pm the phones stopped recieving updates. Upon further investigation I found the OWA also wasn't working. Things I have tried from reading posts so far: 1.) Restarted Server 2.) Uninstalled rollup update for SP1 for Exchange 2007 3.) Uninstall and reinstalled Client Access Role Nothing has changed, this is the error OWA presents me with. Any help is greatly appreciated. I will update this ticket to resolution for future reference... body {font-family:'Verdana';font-weight:normal;font-size:.7em;color:black;} p {font-family:'Verdana';font-weight:normal;color:black;margin-top:-5px;} b {font-family:'Verdana';font-weight:bold;color:black;margin-top:-5px;} H1 {font-family:'Verdana';font-weight:normal;font-size:18pt;color:red;} H2 {font-family:'Verdana';font-weight:normal;font-size:14pt;color:maroon;} pre {font-family:'Lucida Console';font-size:.9em;} .marker {font-weight:bold;color:black;text-decoration:none;} .version {color:gray;} .error {margin-bottom:10px;} .expandable {text-decoration:underline;font-weight:bold;color:navy;cursor:hand;} Server Error in '/owa' 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>Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>