General discussion
-
Topic
-
Outlook 2000 Not Responding
LockedWe are running Outlook 2000 under Windows 2000 connecting to an Exchange server 2000. Some of our users are experiencing problems with Outlook locking up. We go to the Task Manager and see that it is not responding, so we end task. However, this leaves MAPISP32.EXE in memory, and restarting Outlook will get you nowhere unless the process for MAPISP32.EXE is ended. Upon restart, then, everything is fine. We think the problem may revolve around the MAPSP32.EXE, since I have ended the task on Outlook in a test, and MAPISP32.EXE will exit most of the time.
We have narrowed the problem down to just a few users, located near each other, and connected to the same hub. Moving them to a port on the hub whose user does not experience the problem results in no change, so it is not a communications problem, that we can see (it happens mostly when sending or receiving messages).
We have checked the event viewer to find nothing that may indicate a problem with those machines and Outlook, so we do not have an Event ID we could look up.
In several tests, we have found that MAPISP32.EXE will exit if we terminate Outlook using the Task Manager, if there is no apparent problem with Outlook, so we have kind of narrowed the problem down to a problem with MAPISP32.
Office has had SP1 applied, along with all the subsequent patches that do not hinder attachments, as we block on most attachments, and the few we allow to come in seem to be covered by MS’s draconian stance of handling attachments–pretty much blocking them in effect.
We have SP2 applied to Win2K, and do have IE 6.0 installed with all the patches except this last batch that just came out. We are holding out on further patching until we can resolve this problem for those users.