Printer Redirects, But No Output

[Guest]

User connects to a TS server (W2K) with an XP client that has a USB printer
attached (Dell all-in-ine 962). Printer session is successfully created on
the TS server and client is able to access the printer from applications.

When user attempts to prints, there are no errors (displayed) at the
terminal server or client, the print queue shows one document (for a short
time) then goes to 0 documents and the document does not print. The event
log on the client doesn’t show any errors, however the event log on the TS
shows the following:

Event Type: Error

Event Source: Print

Event Category: None

Event ID: 61

Date: 1/17/2006

Time: 9:15:08 PM

User: S-1-5-21-823518204-813497703-1202660629-1151

Computer: SERVER

Description:

The document Test Page owned by admin failed to print. Win32 error code
returned by the print processor: 6 (0x6).



For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.



Event Type: Information

Event Source: Print

Event Category: None

Event ID: 10

Date: 1/17/2006

Time: 9:15:11 PM

User: S-1-5-21-823518204-813497703-1202660629-1151

Computer: SERVER

Description:

Document 3, Test Page owned by admin was printed on Dell Photo AIO Printer
962/MAXIMUS/Session 6 via port TS001. Size in bytes: 1562344; pages printed:
1



For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.



I’ve tried updating the printer drivers on both the client and server and
various solutions in the knowledgebase pertaining to Event ID 61, but have
had no luck resolving this issue.

Does anyone have any ideas?

Thanks,

KAM

 

[Vera Noest [MVP]]

All-in-one printers don't work well (if at all) on a Terminal
Server, and the Dell printers seems to be notorious for this
behaviour, judging from similar posts in these newsgroups.

It is *not* recommended to install 3rd party printer drivers on a
TS, since such drivers are often not TS compatible and are known to
crash your print spooler or the whole server.
Uninstall the driver completely from the server and map the printer
driver to a native driver on the server, by creating a custom
ntprintsubs.inf file.
Detailed information here:

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

_________________________________________________________
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 ___

 

[Guest]

On local machine, login as Admin. Go printers, - properties. Set every one
full permissions.

For future, do not use home printers on TS boxes.