P
Philip Sloss
I've seen this question asked in Usenet archives, but I haven't found a KB
article or any definitive explanation on this.
Here's the problem I have with a couple of users running Outlook 2000 on
Windows 2000 Professional. Both are up-to-date on patches.
They both launch Outlook from an icon in the Quick Launch folder; while
troubleshooting this problem, I changed that icon to be a "regular"
shortcut -- in other words, OL is launched with no command line parameters.
Sometimes, they will click on the icon and "nothing happens." There is no
"task" displayed in the Applications tab of Task Manager and none in the
task tray. I've seen this so many times now that I know what I'll find:
looking in the process list, there are five or more instances of OUTLOOK.EXE
in memory. Using a process monitor program like SysInternals' Process
Explorer, I can see that none of the instances are launched with
"/embedding" or any of the Outlook command line parameters -- the command
lines just consist of the path to the executable and that's it.
As I kill most of those processes and bring the number down to one or two,
one or both of those remaining processes will magically reappear.
Is there any documentation on whether there is a fix, what the problem is,
or what possible workarounds there are -- besides having to clean up the
mess as above?
Thanks,
Philip Sloss
article or any definitive explanation on this.
Here's the problem I have with a couple of users running Outlook 2000 on
Windows 2000 Professional. Both are up-to-date on patches.
They both launch Outlook from an icon in the Quick Launch folder; while
troubleshooting this problem, I changed that icon to be a "regular"
shortcut -- in other words, OL is launched with no command line parameters.
Sometimes, they will click on the icon and "nothing happens." There is no
"task" displayed in the Applications tab of Task Manager and none in the
task tray. I've seen this so many times now that I know what I'll find:
looking in the process list, there are five or more instances of OUTLOOK.EXE
in memory. Using a process monitor program like SysInternals' Process
Explorer, I can see that none of the instances are launched with
"/embedding" or any of the Outlook command line parameters -- the command
lines just consist of the path to the executable and that's it.
As I kill most of those processes and bring the number down to one or two,
one or both of those remaining processes will magically reappear.
Is there any documentation on whether there is a fix, what the problem is,
or what possible workarounds there are -- besides having to clean up the
mess as above?
Thanks,
Philip Sloss