Outlook will not open until I reboot

[chipper]

I'm running Outlook 2003 on a Vista operating system. I continue to have the
same problem.... I have to reboot my computer to get my Outlook to open. I
can run outlook a couple of times without shutting down the system, but then,
it just simply won't open....

Any advise ??

 

[Pat Willener]

Is it possible that Outlook does not close when you close it, so that
you have multiple version of Outlook running? Check with the Task
Manager. If you find indeed multiple copies of Outlook running, then the
next step will be to find out why it does not close. Usually the reason
is some add-on that prevents OL from closing.

 

[chipper]

According to the task manager, there are no versions of outlook running.

 

[Pat Willener]

You *did* check the 'Processes' tab?

 

[chipper]

No, I had been only looking at the "Applications" Tab. Not sure what to do /
or look at in the "Processes" tab. I did a test on, to see what would happen
in the Process tab with outlook running, then with it closed. I found that
OUTLOOK.EXE, indicated CPU at "0" when outlook was open. I then closed it,
and OUTLOOK.EXE still indicates CPU "0". Does that reveal anything to you?

Thanks for your analysis!!!

 

[Pat Willener]

When you close Outlook, process OUTLOOK.EXE should disappear from the
active processes. This may take a few seconds until it's completely gone.

If it remains as an active process, this means that "something" is
preventing Outlook from terminating - usually an add-on or plugin.

After you closed Outlook, then waited about 1 minute or so, open the
Task Manager's Processes tab again, and end all OUTLOOK.EXE processes
(right-click, then End Process).

After this, start Outlook in Safe Mode (Start -> Run -> outlook.exe
/safe). Let it run for a while, then close it normally. Check the
processes again in Task Manager, and see if OUTLOOK.EXE disappears this
time.

I have a long weekend coming up, so I won't be able to respond until
Tuesday. I hope someone else will jump in, e.g. with advice how to find
which add-on may be causing the problem.