Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 9/12/2005
Time: 8:49:03 AM
User: N/A
Computer:
Description:
Application popup: drwtsn32.exe - DLL Initialization Failed : The
application failed to initialize because the window station is shutting down.
----------------------------------------------------------------------------------------------
This is a pretty normal message, except my server is not shutting down, nor
has anyone attempted to shut it down. I started getting this message on the
9th. Over the weekend I restarted the server, but Dr. Watson still thinks
the server is attempting to shutdown.
My question is simple: has anyone seen this behaivor before? If so, is
there a solution?
Server stats:
Windows Server 2003 (pre-sp1)
Metaframe presentation server 4
KB837018 (pre-sp1 Dr. Watson fix.)
Right now my plan is to re-install Dr. Watson, my guess is a part of the
program 'broke.' No other applications report this error message.
--
NDadabo
Network Support Specialist
Federal Signal Environment Products
--
---
Giuseppe Nacci
Microsoft Certified System Engineer
Microsoft Certified Trainer
Security Manager
Begin here:
http://www.computerhope.com/software/drwatson.htm
Did you cannot run both drwatson.exe and drwtsn32.exe?
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 9/19/2005
Time: 11:32:43 AM
User: N/A
Computer: EPG-CITRIX-AD2
Description:
Application popup: drwtsn32.exe - DLL Initialization Failed : The
application failed to initialize because the window station is shutting down.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I am not certain why Dr. Watson thinks the system is shutting down. Dr.
Watson did successfully record three service crashes before this started.
I made one change to the environment before Dr. Watson stopped working: I
copied an updated version of CpSvc.exe to Citrix's program files. This is
their print management service that works with the print spooler. I do not
think this caused the problem, but I suppose stranger things have happened.
--
NDadabo
Network Support Specialist
Federal Signal Environment Products