I have an issue that is driving me crazy. Here is the situation: We recently upgraded a user to Windows 7. We are using Outlook 2007 and Exchange 2007. Occasionally, when the user tries to open Outlook, it gives the error stating that the connection to Exchange is unavailble. This usually happens after they have been away from their desk for more than about 10 minutes. It does not matter how many times we hit "Retry" it does not work. Now here is the strange part. If I close Office Communicator, and then try to open Outlook, it works fine. Now if I open OC, close Outlook, and reopen Outlook it opens fine. We have done repair installs and complete reinstalls of both programs. We have also deleted and recreated his mail profile. No luck. Everything is completely up to date as far as I can tell. I have had this issue one other time that I fixed, but I am unable to remember for the life of me what fixed it. The other user received a new computer with Windows 7 (not a rebuild like the current situation). The only real connection that I can find between the two users is that they both use static IP's. However another user is on the same basic setup and has not experienced any issues. Any help would be greatly appreciated

On Tue, 27 Apr 2010 19:15:26 +0000, SeanPenrice wrote: > > >I have an issue that is driving me crazy. Here is the situation: > >We recently upgraded a user to Windows 7. We are using Outlook 2007 and Exchange 2007. Occasionally, when the user tries to open Outlook, it gives the error stating that the connection to Exchange is unavailble. This usually happens after they have been away from their desk for more than about 10 minutes. It does not matter how many times we hit "Retry" it does not work. Now here is the strange part. If I close Office Communicator, and then try to open Outlook, it works fine. Now if I open OC, close Outlook, and reopen Outlook it opens fine. We have done repair installs and complete reinstalls of both programs. We have also deleted and recreated his mail profile. No luck. Everything is completely up to date as far as I can tell. > >I have had this issue one other time that I fixed, but I am unable to remember for the life of me what fixed it. The other user received a new computer with Windows 7 (not a rebuild like the current situation). The only real connection that I can find between the two users is that they both use static IP's. However another user is on the same basic setup and has not experienced any issues. > >Any help would be greatly appreciated MOC shares the connection and MAPI profile with Outlook (as do other mail-enabled applications like MS Word). What service pack of MS Office is being used? And what MS Office rollup patches have been installed? If you would, get the information from the 1st like of the "Help | About..." in Outlook nd post it here. If you're not running MSO SP2, install it. If you're not running the MS Office rollup from at least August 2009 get it and install it (or just get the most recent one and install it). MS Outlook is three years old and there have been lots of improvements since RTM -- incuding the ability for Outlook to shut down even if the connection is shared with MOC. I'll be that if you get into this situation again and you exit Outlook that you'll still see Outlook in Task Manager's list of processes. Kill Outlook and restart it and see if it works better. Then install the updates. :-) --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

OC and Office are both completely updated. Also, Outlook does not show up in the task manager. The only reason I found that closing Office Communicator allowed it to open is by looking at the task manager in the original case and seeing that it was taking about 20% of the CPU time. I have found a fix that will work for me now, but it is not the original fix and not the most ideal solution. If I go to Tools>Options in MOC and change Personal Information Manager to None, the issue goes away. I applied this solution approximately 2 weeks ago and have not had it happen again since then.

Any update on this Sean? We are having the same issue but really don't wanna disable the pim. Thanks in advance.