Suddenly, Outlook doesn't close

[Guest]

I'm using Outlook 2003 SP3 with XP Pro SP2. I've been using it with no real
trouble for a year. Suddenly, this week, I'm finding that the program doesn't
completely close after I exit. When I try to log off or shut down my
computer, I'll get the End Program dialog for tfswctrl.exe, then for
Outlook.exe. In each case I had recently closed Outlook, usually within 5
minutes. There is no icon in the system tray. In Task Manager, nothing shows
up for Outlook under Applications or Processes. It happens even if I haven't
sent or received any mail prior to closing Outlook. I've tested this a few
times, and sometimes it does close. Other times, not.

2 things happened the day I started to see the behavior: I received the
newest Windows Updates, and I deleted an IMAP mail account.

I read several threads on this topic, but the suddenness of the behavior
after using the program so long , made me think it couldn't be an add-in. All
the add-ins have been in place for 2 months to a year, without causing this
issue.

Any ideas on what could be wrong and how to fix it? It's mostly a nuisance,
but if this is, in fact, related to add-ins, the same thing will be happening
for other users on our network, so I need to find out now how to resolve the
situation.

Thanks for your help.

 

[Brian Tillman]

I'm using Outlook 2003 SP3 with XP Pro SP2. I've been using it with
no real trouble for a year. Suddenly, this week, I'm finding that the
program doesn't completely close after I exit. When I try to log off
or shut down my computer, I'll get the End Program dialog for
tfswctrl.exe, then for Outlook.exe.

The former file is likely HP's packet writing software for copying files to
a CD from Windows Explorer and it's meant to always be running. Did you
install an update for it recently?

In each case I had recently
closed Outlook, usually within 5 minutes. There is no icon in the
system tray. In Task Manager, nothing shows up for Outlook under
Applications or Processes.

If you do not see OUTLOOK.EXE as a process, then I'd say it did close.

It happens even if I haven't sent or
received any mail prior to closing Outlook. I've tested this a few
times, and sometimes it does close. Other times, not.

2 things happened the day I started to see the behavior: I received
the newest Windows Updates, and I deleted an IMAP mail account.

You could always try a new mail profile.

 

[Guest]

If you do not see OUTLOOK.EXE as a process, then I'd say it did close.

I was wrong. Outlook is still listed under processes, using no CPU resources
but using the same amount of memory as if I just launched it. I tested again,
and after 45 minutes, it was still holding on to this memory.

You could always try a new mail profile.

That would mean a new user account on the domain, so I'd prefer not to have
to go that route.

Thanks for your help. Are there any other possibilities?

Peggy

 

[Brian Tillman]

That would mean a new user account on the domain, so I'd prefer not
to have to go that route.

No new user required at all. See this:
http://www.howto-outlook.com/faq/newprofile.htm