Re: Printing issues
- From: "Ketchup" <ketchup@xxxxxxxxxxx>
- Date: Tue, 4 Nov 2008 15:03:18 -0500
Vera,
I agree on the printer driver issue. The problem seems to spread after the
spooler service crashes. I get applications that won't start because of
error 1018. 1018 is the "Illegal operation on a registry key marked for
deletion." error.
My issues with printer is that they are all installed on the Terminal
Server. All clients with the exception of 2 are thin clients (Wyse
Winterms, RDP 5.1). I have disabled the Terminal Services UserMode Port
Redirector service for now. This should stop any client printers from
being installed.
Do you think that the Easy Print driver would help in this case, considering
all printers are local and not redirected?
Thanks,
Dmitry
"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns9B4CD1C95C10Bveranoesthemutforsse@xxxxxxxxxxxxxxxx
Smells like an incompatible printer driver to me. Most 3rd party
drivers are not compatible with TS.
Have you tried using EasyPrint?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"Ketchup" <ketchup@xxxxxxxxxxx> wrote on 04 nov 2008 in
microsoft.public.windows.terminal_services:
I am having a strange issue with a Windows 2008 Terminal Server.
For the last few days now, printing seems to stop functioning.
The symptoms are inability to view properties for a printer,
and general communication issues with the spooler service. When
I attempt to restart the Print Spooler service, I get the
following error message and associated EventLog entry:
The Print Spooler service failed to start due to the following
error: Illegal operation attempted on a registry key that has
been marked for deletion.
The only way to fix this is to restart the server. I have been
trying to figure out what the registry key could be and what the
process is that is locking the key. I have not yet been able
to identify the culprit. I do get a few Event ID 1530 messages
regarding "leaked registry handles." I am not entirely sure
what these pertain to. Eventid.net doesn't seem to place much
importance on these.
I appreciate any help troubleshooting these issues.
Thanks!
Dmitry
.
- Follow-Ups:
- Re: Printing issues
- From: Jeff Pitsch
- Re: Printing issues
- References:
- Printing issues
- From: Ketchup
- Re: Printing issues
- From: Vera Noest [MVP]
- Printing issues
- Prev by Date: TS 2008 Web Access with RDP
- Next by Date: Re: Printing issues
- Previous by thread: Re: Printing issues
- Next by thread: Re: Printing issues
- Index(es):
Relevant Pages
|