What I found from the log files is that no matter if your account is previously set or not EWS is doing the Autodiscover during the startup. If the TimeZoneDefinitionId is being sent as "null" Exchange server returns 18500 error and it goes into the loop.
As I mentioned in my other mail, after figuring out that detail, I checked the timezone information on computer and Entourage. Only problem seems to be that computer is set to "GTM+4 Dubai" and Dubai is not defined as a timezone in Entourage. I changed the computer timezone to GMT+4 Muscat and now the log file shows the TimeZoneDefinitionId="Arabian Standard Time" and connection is ok. It just cost me at least 10 uninstall/reinstall and numerous trials to restore configuration files from my previous backups :-(( > From: ext William Smith <[email protected]> > Reply-To: YouTalk mailing list for discussion of Microsoft Entourage > <[email protected]> > Date: Sun, 15 Nov 2009 22:20:18 +0100 > To: Entourage Help Page mailing list <[email protected]> > Subject: Re: exchange server connection problem after 13.0.3 update > >> Successful connection: <t:TimeZoneContext><t:TimeZoneDefinition Id="Georgian >> Standard Time"/></t:TimeZoneContext></ >> failed connection: <t:TimeZoneContext><t:TimeZoneDefinition >> Id="(null)"/></t:TimeZoneContext></ > > I have no idea why time zone would affect setup or connection. I could > understand that a problem might occur if your computer's clock weren't > properly synchronized. Be sure to check that as well. -- YouTalk mailing list List address: [email protected] List information: http://entourage.mvps.org/support_options/list.html List moderator: [email protected], [email protected] To unsubscribe: mailto:[email protected]?subject=unsubscribe
