Event Log Errors 1106 and 1111, TermServDevices

  • Thread starter Thread starter Branden Willis
  • Start date Start date
B

Branden Willis

Hello All,
Getting these two errors in the Event log on Windows 2K Servers:

--------------------------------
Source: TermServDevices
Event ID: 1111
Type: Error

Driver HP LaserJet 5000 Series PCL 6 required for printer __nova2_HP
LaserJet 5000 Series PCL 6 is unknown. Contact the administrator to
install the driver before you log in again.

-------------------------------
Source: TermServDevices
Event ID: 1106
Type: Error

The printer could not be installed.

-------------------------------

Appearance of these errors coincides to logging in to the server in
question with a Terminal Services session. I've done a search on the
Microsoft Knowledge Base and did not find anything useful.

There was some indication in another post on this forum that the
problem lies with the server attempting to load drivers on the server
for printers that are locally attached to the client computer. In my
case there are no locally attached printers, so that could not be the
problem. The only printers in the picture are a pair of
network-attached printers. Any help would be appreciated. Thanks
 
Hi,

Are you connecting Windows 2000 client to Windows 2000 TS or another
configuration?

--
--Jonathan Maltz [Microsoft MVP - Windows Server]
http://www.imbored.biz - A Windows Server 2003 visual, step-by-step
tutorial site :-)
Only reply by newsgroup. If I see an email I didn't ask for, it will be
deleted without reading.
 
As long as there is a printer on the client side regardless of connection
type (USB, LPT or Network) the TS will try to create a printer for you under
your session.
The way to fix is to edit NTPRINT.INF on the TS as explained in the article
I wrote that is on the Microsoft website.
Some may not agree as this break the digital signature on it. I have never
had a single issue by doing this.

--
Cláudio Rodrigues, MVP
Windows 2000/NT Server
Terminal Services

http://www.terminal-services.NET

-> The only Terminal Services Client for DOS.
-> The only customized RDP5.1 client with the close button disabled! :-)
-> Developers of SecureRDP, the BEST security utility for TS!

Do NOT email me directly UNLESS YOU KNOW ME or you are a Microsoft
MVP/Employee.
Use my support page on my website to submit your questions directly.
 
Yes...I also got a same error on my W2K server after we
installed a new CANON copy machine on our network.
Actually, this machine also act as a network printer.
Based on the MS Knowledge Base Article - 239088, it has
addressed the reason and solution. U better take a look
on it. However, for now, I haven't try the solution yet,
cos it looks kind of complicated. I will try to contact a
CANON first before modify any registry on my server.
U better try it...
 
Back
Top