Outlook 2003 process never ends

[Sandy Modesitt]

Hi,
I saw another posting in the group (6/16 I think) that never received an
answer. I am hoping that, if I post again, someone will see it and have a
solution. I have combed the Microsoft knowledge base and the newsgroups and
didn't find a solution. I have also done Google searches with no success.

Outlook 2003 will not exit completely when I shut it down. The OUTLOOK.EXE
process keeps running (as seen on the status bar and in the Task List). If
I try to restart Outlook, it looks like it is going to start (via the change
in mouse cursor) and then nothing happens. If I logout of Windows (I am on
Win 2K), it indicates that the process is hanging and I must end task to log
off. When I re-login and open Outlook, it asks if I want to start in safe
mode.

I have found a couple of articles, etc. regarding this problem on Outlook
2000. There is a fix for Outlook 2000 that I found on the internet (ftp
site - could also go through Microsoft) but nothing for Outlook 2003. There
also is a MS article (196366) that gives some things to check but none apply
to me.

Anyone find a solution for this yet?

Thanks much.
Sandy

 

[Patricia Cardoza [Outlook MVP]]

Well, the fix depends on what's making Outlook hang in memory. A few
questions:

1. Do you have a PDA that syncs with Outlook?
2. Does your antivirus software monitor your Outlook email.
3. Do you have any COM add-ins loaded in Outlook?
4. Do you have fax software loaded?

--
Patricia Cardoza
Outlook MVP
Author - Special Edition Using Microsoft Office Outlook 2003
Lead Author - Access 2003 VBA Programmer's Reference
Author - Absolute Beginner's Guide to Microsoft OneNote 2003

http://blogs.officezealot.com/cardoza

 

[Sandy Modesitt]

1. Do you have a PDA that syncs with Outlook? No
2. Does your antivirus software monitor your Outlook email. No - we do it from the server.
3. Do you have any COM add-ins loaded in Outlook? No
4. Do you have fax software loaded? Not really; I have Procomm Plus.

One thing that I didn't mention is that I didn't have this problem until
recently. Am wondering if a MS critical update caused this problem. That's
the only thing that I can think of that I might have installed/applied
recently.