Re: Print spooler problems on termnal server.
- From: Joeb <joeb1nospam@xxxxxxxxxxxxxx>
- Date: Wed, 16 May 2007 05:49:00 -0700
Thanks,
the KB article you mention here says that the fix is included in windows
server 2003 , but obviously this isn't working , so do i have to do the
registry modification that it describes.
If the print spooler is corrupted or not working properly can it be
reinstalled.
Also, when these problems happen, it eventually causes the Domain Controller
server to use up all its resources and beging shutting down applications. One
of the first to go is the MS Exchange. As this client relies heavily on
emails for their business is there anyway that this can be avoided. Is there
an option to make MS exchange a high priority application so that it doesn't
get shutdown.
"Vera Noest [MVP]" wrote:
I think that what you see is that the print spooler continuously.
crashes, automatically restarts and tries to print the same jobs
over and over again.
You can prevent that behaviour by automatically discarding all
print jobs when the spooler restarts:
313733 - Spooled files may be printed in an incorrect Terminal
Services session
http://support.microsoft.com/?kbid=313733
But the real cause of the problem is most likely a 3rd party
printer driver, which is not TS compatible and crashes your
spooler.
Check this out:
The Hunt for the Bad Printer Driver - by Stefan Vermeulen
http://www.msterminalservices.org/articles/hunt-bad-printer-
driver.html
_________________________________________________________
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?Sm9lYg==?= <joeb1nospam@xxxxxxxxxxxxxx> wrote on 15 maj
2007 in microsoft.public.windows.terminal_services:
I have 2 servers setup in a domain. One is a SBS2003 Server
(Domain Controller) and the other is a 2003 Server (Terminal
Server).
Users are connecting remotely to the Terminal server using RDP.
In the last few days a major problem has appeared where the
print jobs seem to be wanting to be printed to local printers
even though no print jobs have been selected. If I disable the
printer option on the remote desktop program the problem goes
away for that particular user. At times many thousands of print
jobs are attemtping to be printed and the Domain controller's
system resources are also used. Eventually both servers beging
to close down apps and programs and need to be restarted to
clear the problem.
Once restarted the whole process starts again.
one of the event logs from the system log on the domain
controller that appeared many hundreds of time is shown here.
EVENT ID 6161
The document Remote Desktop Redirected Printer Doc owned by
Elenita failed to print on printer HPLaserJet 1022n. Data type:
RAW. Size of the spool file in bytes: 0. Number of bytes
printed: 0. Total number of pages in the document: 1. Number of
pages printed: 0. Client machine: \\192.168.1.126. Win32 error
code returned by the print processor: 0. The operation completed
successfully.
In my opinion the problem may be coming from the terminal server
because the print jobs are continually appearing when connected
to it.
I would really appreciate is someone could help with this
problem as it is causing a great deal of frustration.
- Follow-Ups:
- Re: Print spooler problems on termnal server.
- From: Vera Noest [MVP]
- Re: Print spooler problems on termnal server.
- References:
- Re: Print spooler problems on termnal server.
- From: Vera Noest [MVP]
- Re: Print spooler problems on termnal server.
- Prev by Date: Re: Terminal Server User Access permissions
- Next by Date: Re: Accessing from a WEB page
- Previous by thread: Re: Print spooler problems on termnal server.
- Next by thread: Re: Print spooler problems on termnal server.
- Index(es):
Relevant Pages
|
