Link to home
Start Free TrialLog in
Avatar of jchri66
jchri66

asked on

Entourage 2008 / Exchange 2003 issues

We are having a problem where Entourage 2008 is pegging are Exchange 2003 server.  The Entourage installation is 2004 with a 2008 upgrade.  We have uninstalled and reinstalled the application and still have the problem.  We have also installed a nonupgrade version of Entourage 2008 and still have the problem.  

I read there a band-aid registry setting for the Exchange server but I don't like that solution.  There got be a better way.
Avatar of strung
strung
Flag of Canada image

Have you had a looki to see if there are any solutions here: http://www.entourage.mvps.org/  ?
Avatar of jchri66
jchri66

ASKER

Didn't see anything after searching that site.  Reverting to 2004 seems to have solved the problem for now.  I'll leave this open in case anyone thinks of something setting-wise.
Avatar of jchri66

ASKER

Update:

Entourage 2004 is doing it also.
Could you please elaborate the issue when you use Office 2008?
Avatar of jchri66

ASKER

Basically once the user opens Entourage my Exchange server gets a huge spike on Disk Reads.  Shortly after that RPC latency goes off the charts and then all my Outlook users start getting timeouts while trying to connect to the Exchaneg server.  
You might have a look here: http://macwindows.com/

and here:  http://macwindows.com/entourage.html
Avatar of jchri66

ASKER

Thanks for the input, I have come across that post before and the solutions aren't realistic.  This particular user has a medium sized mailbox and the issue seemed to just happen.  

One thing we are looking at is the process of how Exchange handles WebDAV clients differently then MAPI.  We have read that the .STM database is where the information for the WebDAV clients are stored.  But we have found a thread where if you open a new mailbox with a webDAV client everything will be great.  Once the mailbox is opened by a MAPI client the mailbox will then be stored in the EDB never to return to the STM.  This will now cause the Exchange server to always convert the Email which leads to the problem we are having.

I am in the process of verifying this.    
ASKER CERTIFIED SOLUTION
Avatar of jchri66
jchri66

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial