How do I get outlook to shutdown without using task manager?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Workstations are XP SP2, attached to NT server running exchange 5.5. Email
accounts used are POP and Exchange. SAV Corporate AV 9.05 clients also
running. Outlook launches and closes fine with just the POP3 account. I add
the exchange account, and it runs, but I can't close Outlook and then restart
it without going to the task manager to end the task. I'd like to buy
another 40 copies of Office Professional 2003, but not without figuring this
out first.

Any help would be appreciated.
 
Did you install SAV 9.x with the email scanner(s) enabled? If yes, try
uninstalling/reinstalling SAV 9.x w/out it.

Should also let you know there are tons of reasons why Outlook will stay
resident in memory after selecting exit. Some reasons are poorly written
3rd party addins (e.g. COM Addins), Fax software (e.g. WinFax), PDA software
(ActiveSync), using Word 2003 as the email editor and Word is still running
when Outlook closes. Best advice is just look for items that use, store,
and/or protect Outlook data.
 
Close but no cigar.

What I was able to determine is that uninstallation of SAV 9, together with
having mail delivered to a PST file (versus the exchange server mailbox)
allowed Outlook to shut down without ending it in task manager.

Once SAV 9 is installed again, without any email scanning, and excluding the
PST file, the problem comes back and task manager is required to end Outlook.

Enabling/disabling Word as the email editor has no impact. No com add ins
are installed.

It's also interesting that Windows 2000 operating systems work properly
(meaning Outlook 2003 with Exchange 5.5 and POP3 accounts and SAV 9.0 with
mail scanning for exchange and internet mail) work flaulessly
 
Hmm... Exchange 5.5 is at what service pack level? Might as well supply the
same information for the NT4 operating system that is supporting the
Exchange 5.5 server.

Are you running in cached or traditional mode against the Exchange 5.5
server?

Outside of that, I run Windows XP(SP2)/Office 2003(SP2)/SAVCE 9.0.5 against
an Exchange 5.5 (SP4)/Windows 2000 (SP4) server and I have never seen this
behavior. (The only account type we allow is Exchange with the Exchange
mailbox set as the default delivery location.)
 
Exchange SP4, NT SP6. I've tried running cached and traditional and either
way seems to have no impact.

It's hard for me to believe that I'm the only person seeing this kind of
thing. I guess it's to be expected when you try things like puting a PT
Cruiser engine, transmittion and body on an Edsel frame.

I've been trying (literally for years) to get approval to move away from NT
and towards 2003 server (a couple of years it was to move toward 2000 server)
but I'm up against "if it isn't broke, don't fix it"

I want to thank you for the time you are taking with this. I really do
appreciate it.
 
Back
Top