I have been having problems with Outlook 2003. Outlook has been hanging and I
get the followig message when shutting down Windows XP Pro, "WMS Ide not
responding".

I have been try to resolve this the last week since installing a Linksys
WRT54G wireless router and the installing Spy Sweeper 4.5, the following day.

Outlook 2003 is part of Office Professional Editio 2003 with Business
Contact Manager.

I first suspected the SpySweeper installation and got a solution from
Webroot to " diable Spy Sweeper " at start up". This worked for 1 or2 boots.
now it's back with the hang and the WMS Idle- not responding at Shut Down
or Restart.

Prior to disabling SS at startup. I had tried Outlook Repair and had
reinstalled Outook, neither of which had worked.

Most of the info I have gleaned form other sites has pointed to Outlook or
Microsoft Exhange Server 2003, although I did see some reference to Out look
and multiple Network DNS. But no specific questions or answers regardind Spy
Sweeper 4.5.

I would like very much to continue using Outlook 2003, if I can find a
solution to this problem. Thanks very much for assistance

d snively d wrote:

I have been having problems with Outlook 2003. Outlook has been
hanging and I get the followig message when shutting down Windows XP
Pro, "WMS Ide not responding".

Google shows that this can be caused by Norton Internet Security. SYmantec
doesn't have a good track record of playing well with Outlook.
--
Brian Tillman

Thanks Brian. Your post didn't say what specifically you found or where on
google you found that info.

I have had had this computer for 1.5 years. It came with Norton Internet
Security installed and I updated to 2005 about 1 year ago with no problems
since then. Only after installing the WRT54G Router, then Spy Sweeper did I
have a problem.

"Brian Tillman" wrote:

d snively d wrote:

I have been having problems with Outlook 2003. Outlook has been
hanging and I get the followig message when shutting down Windows XP
Pro, "WMS Ide not responding".

Google shows that this can be caused by Norton Internet Security. SYmantec
doesn't have a good track record of playing well with Outlook.
--
Brian Tillman

d snively wrote:

Thanks Brian. Your post didn't say what specifically you found or
where on google you found that info.

I entered the error in your subject and started reading. Every post I saw
that said the problem was fixed named NIS as the culprit.
--
Brian Tillman

I may have already resolved the problem thru deactivating Outlook

Addin: Exchange Extensions Propery Pages &

Com Addins: Norton Antispam Outlook Plug-in &
Pdf Converter 3.0 Outlook Addin

I'm not sure if SS added the Exchange Extensions Propery Pages add-in or
some other program did. Theworld of software is a bit too complex these days.
For some reason all this came about after installing SS. The world of
software has become a bit too compex for the non-professionals these days.

Thanks again for your imput, I wasn't familar with Google Groups. K. Orland
had a post on HOWTO-OUTLOOK.COM.


"Brian Tillman" wrote:

d snively wrote:

Thanks Brian. Your post didn't say what specifically you found or
where on google you found that info.

I entered the error in your subject and started reading. Every post I saw
that said the problem was fixed named NIS as the culprit.
--
Brian Tillman

I spoke too soon. After about 3 startups WMS Idle stoped responding again and
after a couple more startups Outlook 2003 started haning on start again. If
anyone else has any thoughts I would be interested.

I still don't understand what "WMS Idle" is. I have seen reference to
Windows Messenger, as well as Exchange Server.

"d snively" wrote:

I may have already resolved the problem thru deactivating Outlook

Addin: Exchange Extensions Propery Pages &

Com Addins: Norton Antispam Outlook Plug-in &
Pdf Converter 3.0 Outlook Addin

I'm not sure if SS added the Exchange Extensions Propery Pages add-in or
some other program did. Theworld of software is a bit too complex these days.
For some reason all this came about after installing SS. The world of
software has become a bit too compex for the non-professionals these days.

Thanks again for your imput, I wasn't familar with Google Groups. K. Orland
had a post on HOWTO-OUTLOOK.COM.


"Brian Tillman" wrote:

d snively wrote:

Thanks Brian. Your post didn't say what specifically you found or
where on google you found that info.

I entered the error in your subject and started reading. Every post I saw
that said the problem was fixed named NIS as the culprit.
--
Brian Tillman

d snively wrote:

I still don't understand what "WMS Idle" is. I have seen reference to
Windows Messenger, as well as Exchange Server.

It's the Windows Messaging Subsystem and it has nothing to do with
Messenger. I don't have any more ideas.
--
Brian Tillman

WMS is, basically, the Windows Messaging Subsytem. Entirely different from
Windows Messenger.
Is Norton Antivirus email integration aslo disabled? I'd try that.

--
Bill R MVP
"d snively" wrote in message
...
I spoke too soon. After about 3 startups WMS Idle stoped responding again
and
after a couple more startups Outlook 2003 started haning on start again.
If
anyone else has any thoughts I would be interested.

I still don't understand what "WMS Idle" is. I have seen reference to
Windows Messenger, as well as Exchange Server.

"d snively" wrote:

I may have already resolved the problem thru deactivating Outlook

Addin: Exchange Extensions Propery Pages &

Com Addins: Norton Antispam Outlook Plug-in &
Pdf Converter 3.0 Outlook Addin

I'm not sure if SS added the Exchange Extensions Propery Pages add-in or
some other program did. Theworld of software is a bit too complex these
days.
For some reason all this came about after installing SS. The world of
software has become a bit too compex for the non-professionals these
days.

Thanks again for your imput, I wasn't familar with Google Groups. K.
Orland
had a post on HOWTO-OUTLOOK.COM.


"Brian Tillman" wrote:

d snively wrote:

Thanks Brian. Your post didn't say what specifically you found or
where on google you found that info.

I entered the error in your subject and started reading. Every post I
saw
that said the problem was fixed named NIS as the culprit.
--
Brian Tillman

Bill

Thanks vey much. I have had Norton Internet Security 2005 installed for 1
year without a problem. I Disabled Email scanning, Spyware/ Adware Scanning &
an Office plug-in. I had reviously Disabled all add-ins in Outlook.

Outlook2003 now runs ok after starting in Safe Mode.

I do how ever still have the continuing problem with WMS Idle not responding
and hangup of the shut down of the system. Is it best to continue this thread
and in General or is the Windows Messaging Subsytem problem better posted
else where?

I'll discontinue the thread in Outlook Installation and Configuration.



"BillR [MVP]" wrote:

WMS is, basically, the Windows Messaging Subsytem. Entirely different from
Windows Messenger.
Is Norton Antivirus email integration aslo disabled? I'd try that.

--
Bill R MVP
"d snively" wrote in message
...
I spoke too soon. After about 3 startups WMS Idle stoped responding again
and
after a couple more startups Outlook 2003 started haning on start again.
If
anyone else has any thoughts I would be interested.

I still don't understand what "WMS Idle" is. I have seen reference to
Windows Messenger, as well as Exchange Server.

"d snively" wrote:

I may have already resolved the problem thru deactivating Outlook

Addin: Exchange Extensions Propery Pages &

Com Addins: Norton Antispam Outlook Plug-in &
Pdf Converter 3.0 Outlook Addin

I'm not sure if SS added the Exchange Extensions Propery Pages add-in or
some other program did. Theworld of software is a bit too complex these
days.
For some reason all this came about after installing SS. The world of
software has become a bit too compex for the non-professionals these
days.

Thanks again for your imput, I wasn't familar with Google Groups. K.
Orland
had a post on HOWTO-OUTLOOK.COM.


"Brian Tillman" wrote:

d snively wrote:

Thanks Brian. Your post didn't say what specifically you found or
where on google you found that info.

I entered the error in your subject and started reading. Every post I
saw
that said the problem was fixed named NIS as the culprit.
--
Brian Tillman