When I'm done reading and sending mail I close Outlook (It's version 2003,
running under Windows XP) using the 'Close' button. After going through a
day of opening, checking and answering mail and then closing when done,
I've noticed that Task Manager shows multiple copies of OUTLOOK.EXE
running. None of them seem to be taking CPU resources, but they do have
memory assigned. During the day, I don't notice any error messages.
Everything seems to be working fine. There are no clues to indicate that
something hasn't closed until I try to re-boot the PC. Then I get 'not
responding' messages and have to an 'End Now' for each of the running
instances. Any ideas as to why this is occurring?

Sounds like you have a 3rd party addin or program that is holding Outlook
open. Some of the things to look for are PDA or FAX software. Other things
could be Word, Instant Messaging, or poorly written Office/Outlook addins.

"Greg" wrote in message
...
When I'm done reading and sending mail I close Outlook (It's version 2003,
running under Windows XP) using the 'Close' button. After going through a
day of opening, checking and answering mail and then closing when done,
I've noticed that Task Manager shows multiple copies of OUTLOOK.EXE
running. None of them seem to be taking CPU resources, but they do have
memory assigned. During the day, I don't notice any error messages.
Everything seems to be working fine. There are no clues to indicate that
something hasn't closed until I try to re-boot the PC. Then I get 'not
responding' messages and have to an 'End Now' for each of the running
instances. Any ideas as to why this is occurring?

http://www.slipstick.com/problems/close.asp contains a list of some of the
programs that will keep it open - there are many more.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:



"neo [mvp outlook]" wrote in message
...
Sounds like you have a 3rd party addin or program that is holding Outlook
open. Some of the things to look for are PDA or FAX software. Other
things could be Word, Instant Messaging, or poorly written Office/Outlook
addins.

"Greg" wrote in message
...
When I'm done reading and sending mail I close Outlook (It's version
2003,
running under Windows XP) using the 'Close' button. After going through
a
day of opening, checking and answering mail and then closing when done,
I've noticed that Task Manager shows multiple copies of OUTLOOK.EXE
running. None of them seem to be taking CPU resources, but they do have
memory assigned. During the day, I don't notice any error messages.
Everything seems to be working fine. There are no clues to indicate that
something hasn't closed until I try to re-boot the PC. Then I get 'not
responding' messages and have to an 'End Now' for each of the running
instances. Any ideas as to why this is occurring?

Thanks. Are there any utilities that can look at the session and tell
who/what has it open?

"neo [mvp outlook]" wrote in
:

Sounds like you have a 3rd party addin or program that is holding
Outlook open. Some of the things to look for are PDA or FAX software.
Other things could be Word, Instant Messaging, or poorly written
Office/Outlook addins.

"Greg" wrote in message
...
When I'm done reading and sending mail I close Outlook (It's version
2003, running under Windows XP) using the 'Close' button. After
going through a day of opening, checking and answering mail and then
closing when done, I've noticed that Task Manager shows multiple
copies of OUTLOOK.EXE running. None of them seem to be taking CPU
resources, but they do have memory assigned. During the day, I don't
notice any error messages. Everything seems to be working fine.
There are no clues to indicate that something hasn't closed until I
try to re-boot the PC. Then I get 'not responding' messages and have
to an 'End Now' for each of the running instances. Any ideas as to
why this is occurring?