Prev: Software Restriction Policies and logging
Next: Error connecting to existing session for <username> (Id 0)
From: JayKon on 7 Dec 2006 14:45
We have been having a problem where our Terminal Services box hangs,
sometimes to the point of having to press the reset button on the hardware.

Windows 2003 5.2 (SP1)
Terminal Services 5.2 (SP1) (always the same?)
SQL Server 2000
About 15-25 users logged in at a time.

I've been watching the event logs carefully and have found that between 3-7
minutes before the system hangs, we get an Application error on spoolsv.exe
(pasted in at the bottom). This puts a popup on the system console and the
computer room is not easily accessible.

It seems like, if we do go to the console and click OK, the problem clears.
However, if we do a remote desktop, that session will also hang and the
server hangs a little faster (speculation).

We also have the problem of users default printer changing when they login
to the Terminal Services server; however, we believe we know how to fix that
(http://support.microsoft.com/default.aspx/kb/302361/en-us). Still, I believe
that this is somehow related (we'll be fixing that next week).

A tech at the vendor supplying our primary software believes someone
installed printer drivers that are not TS compliant and feels that the popup
on the console reinforces that line of thinking. I have no clue and can't
tell one print driver from another.

I'm the DBA, not a Windows (or TS) Admin, so I'm a bit out of my league and
need some help.

Thanks,
Jay

-----------------------------------------
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 12/6/2006
Time: 3:45:25 PM
User: N/A
Computer: PEIDB
Description:
Faulting application spoolsv.exe, version 5.2.3790.1830, faulting module
rpcrt4.dll, version 5.2.3790.1830, fault address 0x00021861.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 73 70 6f ure spo
0018: 6f 6c 73 76 2e 65 78 65 olsv.exe
0020: 20 35 2e 32 2e 33 37 39 5.2.379
0028: 30 2e 31 38 33 30 20 69 0.1830 i
0030: 6e 20 72 70 63 72 74 34 n rpcrt4
0038: 2e 64 6c 6c 20 35 2e 32 .dll 5.2
0040: 2e 33 37 39 30 2e 31 38 .3790.18
0048: 33 30 20 61 74 20 6f 66 30 at of
0050: 66 73 65 74 20 30 30 30 fset 000
0058: 32 31 38 36 31 21861

From: Vera Noest [MVP] on 7 Dec 2006 15:02
Sounds like the vendor technician is on the right track.

A crashing printer spooler on a Terminal Server is nearly always a
sign that you are using a 3rd party printer driver which is not TS-
compatible.
The remedy is to uninstall all 3rd party printer drivers and map
all printers that don't autocreate to a native printer driver on
the server, by creating a custom ntprintsubs.inf file. Details are
explained here:

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

Since you are running 2003 SP1, you can also define a Fallback
Printer driver.
http://www.printingsupport.com/mambo/index.php?
option=com_content&task=view&id=56&Itemid=49
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?SmF5S29u?= <JayKon(a)discussions.microsoft.com> wrote on
07 dec 2006 in microsoft.public.windows.terminal_services:

> We have been having a problem where our Terminal Services box
> hangs, sometimes to the point of having to press the reset
> button on the hardware.
>
> Windows 2003 5.2 (SP1)
> Terminal Services 5.2 (SP1) (always the same?)
> SQL Server 2000
> About 15-25 users logged in at a time.
>
> I've been watching the event logs carefully and have found that
> between 3-7 minutes before the system hangs, we get an
> Application error on spoolsv.exe (pasted in at the bottom). This
> puts a popup on the system console and the computer room is not
> easily accessible.
>
> It seems like, if we do go to the console and click OK, the
> problem clears. However, if we do a remote desktop, that session
> will also hang and the server hangs a little faster
> (speculation).
>
> We also have the problem of users default printer changing when
> they login to the Terminal Services server; however, we believe
> we know how to fix that
> (http://support.microsoft.com/default.aspx/kb/302361/en-us).
> Still, I believe that this is somehow related (we'll be fixing
> that next week).
>
> A tech at the vendor supplying our primary software believes
> someone installed printer drivers that are not TS compliant and
> feels that the popup on the console reinforces that line of
> thinking. I have no clue and can't tell one print driver from
> another.
>
> I'm the DBA, not a Windows (or TS) Admin, so I'm a bit out
> of my league and need some help.
>
> Thanks,
> Jay
>
> -----------------------------------------
> Event Type: Error
> Event Source: Application Error
> Event Category: (100)
> Event ID: 1000
> Date: 12/6/2006
> Time: 3:45:25 PM
> User: N/A
> Computer: PEIDB
> Description:
> Faulting application spoolsv.exe, version 5.2.3790.1830,
> faulting module rpcrt4.dll, version 5.2.3790.1830, fault address
> 0x00021861.
From: JayKon on 7 Dec 2006 16:01
So, how do I figure out which print drivers to reinstall? This is a very
distributed enviornment (6 buildings, some several miles apart) and when I
look in the printer list I see well over 100 printers (though I know many are
duplicates).

I've looked at the print drivers and they say nothing about being third
pary, or non-microsoft. I asked the guys that have been here a while and they
tell me that just about anyone could have installed a printer and couldn't
tell me who, or what they did.

I've tried (to no avail) to watch the System portion of the event log to see
if I see the same printer printing just before the popup and have see three
seperate printers in three events.

Do we have to reinstall ALL print drivers to be sure? If so, would we do
this on the print server, the TS server, or the workstation (yes some
printers are locally installed and available on the network).


"Vera Noest [MVP]" wrote:

> Sounds like the vendor technician is on the right track.
>
> A crashing printer spooler on a Terminal Server is nearly always a
> sign that you are using a 3rd party printer driver which is not TS-
> compatible.
> The remedy is to uninstall all 3rd party printer drivers and map
> all printers that don't autocreate to a native printer driver on
> the server, by creating a custom ntprintsubs.inf file. Details are
> explained here:
>
> 239088 - Windows 2000 Terminal Services Server Logs Events 1111,
> 1105, and 1106
> http://support.microsoft.com/?kbid=239088
>
> Since you are running 2003 SP1, you can also define a Fallback
> Printer driver.
> http://www.printingsupport.com/mambo/index.php?
> option=com_content&task=view&id=56&Itemid=49
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?SmF5S29u?= <JayKon(a)discussions.microsoft.com> wrote on
> 07 dec 2006 in microsoft.public.windows.terminal_services:
>
> > We have been having a problem where our Terminal Services box
> > hangs, sometimes to the point of having to press the reset
> > button on the hardware.
> >
> > Windows 2003 5.2 (SP1)
> > Terminal Services 5.2 (SP1) (always the same?)
> > SQL Server 2000
> > About 15-25 users logged in at a time.
> >
> > I've been watching the event logs carefully and have found that
> > between 3-7 minutes before the system hangs, we get an
> > Application error on spoolsv.exe (pasted in at the bottom). This
> > puts a popup on the system console and the computer room is not
> > easily accessible.
> >
> > It seems like, if we do go to the console and click OK, the
> > problem clears. However, if we do a remote desktop, that session
> > will also hang and the server hangs a little faster
> > (speculation).
> >
> > We also have the problem of users default printer changing when
> > they login to the Terminal Services server; however, we believe
> > we know how to fix that
> > (http://support.microsoft.com/default.aspx/kb/302361/en-us).
> > Still, I believe that this is somehow related (we'll be fixing
> > that next week).
> >
> > A tech at the vendor supplying our primary software believes
> > someone installed printer drivers that are not TS compliant and
> > feels that the popup on the console reinforces that line of
> > thinking. I have no clue and can't tell one print driver from
> > another.
> >
> > I’m the DBA, not a Windows (or TS) Admin, so I’m a bit out
> > of my league and need some help.
> >
> > Thanks,
> > Jay
> >
> > -----------------------------------------
> > Event Type: Error
> > Event Source: Application Error
> > Event Category: (100)
> > Event ID: 1000
> > Date: 12/6/2006
> > Time: 3:45:25 PM
> > User: N/A
> > Computer: PEIDB
> > Description:
> > Faulting application spoolsv.exe, version 5.2.3790.1830,
> > faulting module rpcrt4.dll, version 5.2.3790.1830, fault address
> > 0x00021861.
>
From: Vera Noest [MVP] on 7 Dec 2006 16:59
I'm afraid that you have quite some work ahead of you :-(

To be absolutely clear: you should *not* re-install those 3rd party
drivers, just uninstall them.
And then *only* use drivers that came with the Windows OS CDrom.

You can identify the vendor by searching for the .dll file for that
printer, right-click it - Properties - Version - Company.
Everything that does *not* say "Microsft" as the company is a 3rd
party driver.

Since you have so many different printers, you might consider a 3rd
party "driver free" printing solution, like ThinPrint, triCerat or
Print-IT.
For more information and URLs check my website, under "Printing"
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?SmF5S29u?= <JayKon(a)discussions.microsoft.com> wrote on
07 dec 2006 in microsoft.public.windows.terminal_services:

> So, how do I figure out which print drivers to reinstall? This
> is a very distributed enviornment (6 buildings, some several
> miles apart) and when I look in the printer list I see well over
> 100 printers (though I know many are duplicates).
>
> I've looked at the print drivers and they say nothing about
> being third pary, or non-microsoft. I asked the guys that have
> been here a while and they tell me that just about anyone could
> have installed a printer and couldn't tell me who, or what they
> did.
>
> I've tried (to no avail) to watch the System portion of the
> event log to see if I see the same printer printing just before
> the popup and have see three seperate printers in three events.
>
> Do we have to reinstall ALL print drivers to be sure? If so,
> would we do this on the print server, the TS server, or the
> workstation (yes some printers are locally installed and
> available on the network).
>
>
> "Vera Noest [MVP]" wrote:
>
>> Sounds like the vendor technician is on the right track.
>>
>> A crashing printer spooler on a Terminal Server is nearly
>> always a sign that you are using a 3rd party printer driver
>> which is not TS- compatible.
>> The remedy is to uninstall all 3rd party printer drivers and
>> map all printers that don't autocreate to a native printer
>> driver on the server, by creating a custom ntprintsubs.inf
>> file. Details are explained here:
>>
>> 239088 - Windows 2000 Terminal Services Server Logs Events
>> 1111, 1105, and 1106
>> http://support.microsoft.com/?kbid=239088
>>
>> Since you are running 2003 SP1, you can also define a Fallback
>> Printer driver.
>> http://www.printingsupport.com/mambo/index.php?
>> option=com_content&task=view&id=56&Itemid=49
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?SmF5S29u?= <JayKon(a)discussions.microsoft.com> wrote
>> on 07 dec 2006 in microsoft.public.windows.terminal_services:
>>
>> > We have been having a problem where our Terminal Services box
>> > hangs, sometimes to the point of having to press the reset
>> > button on the hardware.
>> >
>> > Windows 2003 5.2 (SP1)
>> > Terminal Services 5.2 (SP1) (always the same?)
>> > SQL Server 2000
>> > About 15-25 users logged in at a time.
>> >
>> > I've been watching the event logs carefully and have found
>> > that between 3-7 minutes before the system hangs, we get an
>> > Application error on spoolsv.exe (pasted in at the bottom).
>> > This puts a popup on the system console and the computer room
>> > is not easily accessible.
>> >
>> > It seems like, if we do go to the console and click OK, the
>> > problem clears. However, if we do a remote desktop, that
>> > session will also hang and the server hangs a little faster
>> > (speculation).
>> >
>> > We also have the problem of users default printer changing
>> > when they login to the Terminal Services server; however, we
>> > believe we know how to fix that
>> > (http://support.microsoft.com/default.aspx/kb/302361/en-us).
>> > Still, I believe that this is somehow related (we'll be
>> > fixing that next week).
>> >
>> > A tech at the vendor supplying our primary software believes
>> > someone installed printer drivers that are not TS compliant
>> > and feels that the popup on the console reinforces that line
>> > of thinking. I have no clue and can't tell one print driver
>> > from another.
>> >
>> > I’m the DBA, not a Windows (or TS) Admin, so
>> > I’m a bit out of my league and need some help.
>> >
>> > Thanks,
>> > Jay
>> >
>> > -----------------------------------------
>> > Event Type: Error
>> > Event Source: Application Error
>> > Event Category: (100)
>> > Event ID: 1000
>> > Date: 12/6/2006
>> > Time: 3:45:25 PM
>> > User: N/A
>> > Computer: PEIDB
>> > Description:
>> > Faulting application spoolsv.exe, version 5.2.3790.1830,
>> > faulting module rpcrt4.dll, version 5.2.3790.1830, fault
>> > address 0x00021861.
From: TP on 7 Dec 2006 17:05
Many of the printer driver files that ship with the OS are
not Microsoft, for example HP.

-TP

Vera Noest [MVP] wrote:
> I'm afraid that you have quite some work ahead of you :-(
>
> To be absolutely clear: you should *not* re-install those 3rd party
> drivers, just uninstall them.
> And then *only* use drivers that came with the Windows OS CDrom.
>
> You can identify the vendor by searching for the .dll file for that
> printer, right-click it - Properties - Version - Company.
> Everything that does *not* say "Microsft" as the company is a 3rd
> party driver.
>
> Since you have so many different printers, you might consider a 3rd
> party "driver free" printing solution, like ThinPrint, triCerat or
> Print-IT.
> For more information and URLs check my website, under "Printing"
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___

 |  Next  |  Last
Pages: 1 2
Prev: Software Restriction Policies and logging
Next: Error connecting to existing session for <username> (Id 0)