Re: Print Spooler issues
- From: Hank Arnold <rasilon@xxxxxxx>
- Date: Sun, 09 Apr 2006 04:22:20 -0400
The URLs were probably wrapped. If you clicked on the "link", you missed the rest of the url on the second line...
Regards,
Hank Arnold
Mike Davis wrote:
Vera,.
Both links went to "page not found". Can you update?
Mike
"Vera Noest [MVP]" wrote:
The fault lies actually with the printer driver manufacturers, not Microsoft. And 3rd party drivers are all drivers which are not included with the OS (your Windows CD).
Check this article by Stefan, it should help you to find the most likely culprit amongst your printer drivers:
Surviving Printing on Citrix
http://www.msterminalservices.org/articles/Surviving-Printing-
Citrix.html
And this one, by Wilco van Bragt, explains some of the problems with installing 3rd party printer drivers:
http://www.msterminalservices.org/articles/Can-Third-Party-
Software-Solve-Terminal-Server-Printing-Problems.html
I would map the printers one by one to a native driver. Or why not uninstall them one at a time and use the Fallback Driver which is available in 2003 SP1? That should enable you to identify which printer driver is crashing the spooler.
Once you have a stable driver for a printer, make sure that you configure your Group Policy or local policy to "Prevent Users from installing Print Drivers". If this is NOT enabled, a user with a newer signed driver will unknowingly and automatically propagate its' driver to the terminal server, which means that your servers will use different driver versions, even though you didn't intentionally install newer drivers.
I'm puzzled by your statement about Citrix. Which version of PS have you abandonned? If you have PS4, you can use the UPD (Unified Printer Driver) to map printers.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?TWlrZSBEYXZpcw==?= <MikeDavis@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 08 apr 2006 in
microsoft.public.windows.terminal_services:
So what you both are saying is that the drivers I downloaded
from HP, Lexmark and Brother that state 2003 drivers are not
exactly 2003 TS drivers?
These are common printers in many workplaces. Uninstall 3rd
party printer drivers? What exactly are "3rd party printer
drivers"? Are they the drivers from HP, Lexmark and Brother?
So Microsofts "solution" is that there is no fix, go buy a third
party software to handle printing? That's not gonna fly at my
company. They have already purchased Citrix Presentation server
(which menu items are running VERY slow) and then agreed to go
to Windows TS so that we could get out of the latency hole. Now
you're telling me to go back to them and tell them that they
also need to purchase a 3rd party solution (which costs $1500 or
higher)?
I think we'll be better served at restoring to the 2000 image I
have and then move on. Windows 2K3 just isn't the quality I
thought it would be.
Thanks anyway
"Vera Noest [MVP]" wrote:
Both Cláudio and Stefan have already pointed out the cause of
your problem: 3rd party printer drivers, and you can't get
better advice than from these 2. But if it helps, I can chime
in.
FYI: the fact that a printer driver is 2003 compatible does
*not* mean that it is 2003 TS compatible.
So I can only fully agree with Stefans advice: uninstall all
3rd party printer drivers and map your printers to a native
driver. Alternatively: buy a driver-free printing solution,
like ThinPrint, tricerat, UniPrint or Print-IT
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?TWlrZSBEYXZpcw==?=
<MikeDavis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 08 apr 2006 in
microsoft.public.windows.terminal_services:
I spent 6 hours yesterday updating the drivers on all 3
servers. Today, we had the same exact problem. I seriously doubt
that this is an issue with a 3rd party driver since ALL drivers
have been updated to 2003 drivers. We have brother 1440
printers, HP2300 and 4200 series and Lexmark Optra T
printers. Every single one of them have been updated.
I had already run the TSPrinter fix and updated whatever was
there (Adobe PDF Writer?) that wasn't even loaded. I have
disabled the client mappings (per other hotfixes).
The 2000 machines ran flawlessly for 3 years, so I highly
doubt luck had anything to do with it.
Maybe someone else wants to give it a shot?
"Stefan Vermeulen" wrote:
Installing third party printer drivers on the server can
lead to undesired results, like killing the spooler service,
hitting cpu spikes, crashing sessions etc etc.
Only use third party drivers as a last resource if drivers
from the OS cdrom in combination with mapping clientside
printer names fail, or that functionality is crucial to the
business. And even then, that driver should have been
tested, before installing on a production system.
The fact that it worked flawless on your 2k servers just
means that you've been lucky so far.
mapping drivernames:
Windows 2000 Terminal Services server logs events 1111,
1105, and 1106: http://support.microsoft.com/default.aspx?scid=kb;en-us;23908
8
Redirect drivernames via a gui:
http://download.microsoft.com/download/9/f/2/9f237742-e057-4e
00- a0d5-62de2ebf9fbd/tspdrw_package.exe
Steps to Manually Remove and Reinstall a Printer Driver
http://support.microsoft.com/?kbid=135406
Stefan
http://www.printingsupport.com
"Mike Davis" <MikeDavis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:AC363CBC-E101-4FE7-948F-DA54A7FD497D@xxxxxxxxxxxxxxxxI installed all printer drivers (2003 versions) on the TS.
Update - I installed 2003 standard on another "test"
machine. I installed Symantec and my ERP application "shortcut"
pointed to a share on another server. Without any updates
run, I still get the same problem. Lockup central -
doesn't matter if there are 5 or 50 users. I have noticed
that the
print spooler grows to 200+ MB, then freezes. I then run
the "fix" (copying,
pasting, stopping and starting the spooler) and it runs OK
for about 2 hours.
Then it freezes again. No rhyme or reason, no common
driver or process being run besides printing in general.
I really need a fix for this or I'm going to have to
revert back to 2000 server (because it worked fine
before).
Thank you for the help.
"Cláudio Rodrigues" wrote:
Did you install any printer driver on the TS?
--
Cláudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services
"Mike Davis" <MikeDavis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:886DB1D0-9880-4FF6-A3AB-29117EC2DE4C@xxxxxxxxxxxxxxxxGood afternoon,
I am running Windows 2003 SP1 using terminal services. We've been having
a
terrible time with the print spooler locking up and
then locking up RDP sessions. I found a solution by
going into C:\%windows%\system32\spool\printers, cut
and pasting the files into a temp
file.
What I want to know - Is there a definate fix to this? I can't keep going
into the server, stopping the service, cut and pasting
the files and then
starting the service again. There has to be a fix for
this problem as I've
seen so many people complaining about it.
Please respond.
- References:
- Re: Print Spooler issues
- From: Cláudio Rodrigues
- Re: Print Spooler issues
- From: Stefan Vermeulen
- Re: Print Spooler issues
- From: Mike Davis
- Re: Print Spooler issues
- From: Vera Noest [MVP]
- Re: Print Spooler issues
- From: Mike Davis
- Re: Print Spooler issues
- From: Vera Noest [MVP]
- Re: Print Spooler issues
- From: Mike Davis
- Re: Print Spooler issues
- Prev by Date: Re: Print Spooler issues
- Next by Date: How to avoid automatic username in Remote Desktop?
- Previous by thread: Re: Print Spooler issues
- Next by thread: Re: Print Spooler issues
- Index(es):
Relevant Pages
|
Loading
