Dear Diane:
Thank you again for your reply.
I agree with you that this is likely not an Outlook file. But Outlook is
the
program being affected by these series of events, and we have numerous
instances
of it occurring within our company alone; therefore I have an incentive to
identify what is causing the issue. I do find it astonishing that after
four
years of this being reported on the Net noone has yet identified the
source of
this error.
I cannot say with certainty what the acronym 'WMS ST' stands for. How can
you
yourself be certain? It might not be from an Outlook file, since that
presumably
is your experience; but it might belong to another Microsoft product, say,
ActiveSync. Several other forum postings have noted this issue involving
sync
software. There are many products which now interact directly with
Outlook, some
from Microsoft, such as Word; and many other third party products. It may
turn
out to be a combination of one or more products interacting with each
other that
results in this error. I do not know yet.
'Windows Messaging System' is an official Microsoft acronym and is part of
their
DLL libraries. Until I have identified what is generating this dialog and
message, it is plausible that WMS stands for this string, since it is a
logical
deduction that a messaging product is generating the problem. But until it
is
identified, my guess is as good as any.
What I am starting to hypothesize is that this message is from a third
party
product which hooks into Outlook and possibly some other program or
programs.
The name of the message dialog suggests that some software code was not
cleaned
up before being put into Production.
As for comparing two systems, easier said than done. A typical system
deployed
within our environment contains thousands of installed program files and
my time
is limited. For my purposes I already have two systems at hand that can
qualify
for this analysis: my desktop system, which is experiencing the problem as
we
speak; and my home laptop, which I bring to work for troubleshooting. Each
has a
slightly different configuration. The laptop does not experience this
shutdown
problem. By process of elimination I can narrow down the list of potential
software suspects and possibly cure my own instance of it, but that does
not
guarantee it will be a reproduceable solution on other machines in our
environment.
I have made inquiries to a specific software vendor to attempt to
determine
whether this error message originates from their software code. If I am
able to
obtain a positive identification, and consequently reliably reproduce a
workable
solution on several machines, I will post my results here, so that others
will
benefit. More to follow.
Abrey Myers
Help Desk/Senior PC Support Specialist
Lowe Enterprises IT Department
11777 San Vicente Blvd. Suite 900
Los Angeles, CA 90049
Telephone: (310) 571-4357
Direct Line: (310) 571-4273
No one really knows for sure what causes the error - some said they had
identical systems, one with logitech software (and the error) and one with
a
different mouse that was error free. Others reported the same with sun
java.
If the problem only occurs on some machines, examine a good machine and
one
'bad' one very closely - see if you can identify what is different between
the two. Look for things like sync software and if users are using
emptying
deleted items on exit.
We've seen errors like this in the past that manifest themselves in
outlook
but in actuality, the problem is with other programs. "WMS ST" is not
short
for Windows Messaging Subsystem and is not an outlook file.
--
Diane Poremsky [MVP - Outlook]
Outlook Tips by email:
mailto:
[email protected]
EMO - a weekly newsletter about Outlook and Exchange:
mailto:
[email protected]
You can access this newsgroup by visiting
http://www.microsoft.com/office/community/en-us/default.mspx or point your
newsreader to msnews.microsoft.com.
Dear Diane:
Thank you for your reply.
We do not use Logitech software products in general. This happens on
machines
that do not have that driver loaded. We also have current Java software
loaded,
but I do not understand how that relates to the error.
None of the posted discussions on this question that I have reviewed
even
identify which DLL, EXE, COM or other support file is generating this
message,
and that is one of the questions I want answered.
Until I am able to identify which piece of software is creating this
message I
have no idea how to approach the problem.
I also have no idea what the letters 'WMS ST' refer to. Is it Windows
Messaging
Subsystem? Does it mean something else? Until I can identify which
software
component is generating the message then I cannot verify anything.
Since you are an Outlook MVP, at least let's start with this. Can
youconfirm
whether this component is part of Outlook or Office, or not, to the best
of your
knowledge?
Regards
Abrey Myers
Help Desk/Senior PC Support Specialist
Lowe Enterprises IT Department
11777 San Vicente Blvd. Suite 900
Los Angeles, CA 90049
Telephone: (310) 571-4357
Direct Line: (310) 571-4273
=======================================
Poremsky
[MVP]" <
[email protected]> says...
I've seen both of the following blamed for it over the years but have no
idea which (if either) is the real cause. It's not specific to outlook,
although it seems to come up often enough in outlook.
Are you using Logitech products and drivers/software? The premise on
this
was the Logitech software sends email and it doesn't interface with
outlook
correctly. I think "WMS" throws them off and they assume WMS =
messaging
=
email. I believe it refers to error/alert messages. It could still be
Logitech though.
Do you have the latest sun/java software?
Best bet is to make sure affected systems have the latest software
updates
and drivers, starting with these two things.
--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks?
http://www.outlook-tips.net/beginner/
Outlook 2007:
http://www.slipstick.com/outlook/ol2007/
Exchange Messaging Outlook newsletter:
(e-mail address removed)
You can access this newsgroup by visiting
http://www.microsoft.com/office/community/en-us/default.mspx or point
your
newsreader to msnews.microsoft.com.
To whomever may know the answer to this question:
We have Office 2007 Professional deployed within our organization. We
are
unable
to determine why at inconsistent times, with many users, when shutting
down a
PC, the OUTLOOK.EXE process does not exit because a warning dialog
appears
with
a message that a process identified as 'WMS ST Notif Window
[hexadecimal
number]' is unable to be closed.
Thereafter, when relaunching Outlook, we encounter a message saying
that
Outlook
did not close properly and would we like it to open in Safe Mode.
I have noted that this question has been posted on and off at various
forums on
the Internet over the past four years, but noone seems to have
published
what
the cause of this error message is due to.
Also TechNet does not appear to have any information regarding this
error
message.
I have tried Ending various processes at shutdown but none of them
appear
to
resolve the error.
I have searched the Registry but none of the entries appear to be
identified
with this string.
I would like to identify which DLL or Process is 'WMS ST Notification
Window';
and whether a fix or patch is available, or a procedure identified, to
correct
this shutdown, if known.
Many thanks.
Abrey Myers
Help Desk/Senior PC Support Specialist
Lowe Enterprises IT Department
11777 San Vicente Blvd. Suite 900
Los Angeles, CA 90049
Telephone: (310) 571-4357
Direct Line: (310) 571-4273
