Print problem event id 13

[rogriob26]

Hi,

I'm trying to print to a server (Windows 2000 Server) printer with generic

text (SAP,Word ) and I get this event log error:

Event Type: Information

Event Source: Print

Event Category: None

Event ID: 13

Date: 17/4/2006

Time: 10:41:17

User: AM\administrador

Computer: EXCSABR01

Description:

Document 170, Local Downlevel Document owned by administrador was deleted on

Xerox 423 Secretaria.

Printer name : XeroxSec

Server name : Excsabr01 IP 206.44.135.12

All of the printers that are installed in this servert have the same

problem.

I have all the proper permissions security set on the printer. Any clues?

Thank you

Rogério

[Zartach]

Hi,

I'm trying to print to a server (Windows 2000 Server) printer with generic

text (SAP,Word ) and I get this event log error:

Event Type: Information

Event Source: Print

Event Category: None

Event ID: 13

You might want to check out this article:

http://support.microsoft.com/default.aspx?...kb;en-us;282420

I know you have a Xerox and the article is about IBM printers, but the error was the same, no harm in checking it out.

Also, there might be an issue when you have the printer connected through a USB connection, use either LPT cable or ethernet connections if the above MS article does not help, if you have USB that might solve the problem.

Hope it helps,

[rogriob26]

Hi

I checked the System event logs on the server and I find the Event ID 13 for when the print job is deleted, but no Event ID 10 for when the job is printed.

So the job gets to the print server, is spooled, and then deleted without being printed.

I use ethernet connections for printer don't use USB printer .

It follows configuration of the printer below

Port Settings

Port Name : XeroxSec

Protocol = Raw

Port Number 9100

Driver WorkCentre Pro 423 PCL 6

Spool print documents so program finishes printing faster

If cancels the option Spool print documents so program finishes printing faster and to mark the option Print directly to the printer gets to print usually in any station.

Any clues?

Thanks

Rogério

[cluberti]

If printing directly to printer works, but the spooling option does not, that would mean that there is either an issue with the print driver being used, or some security issues with the two-way communication between the client and server.

If you create a new queue pointing to an existing port, using one of the built-in Windows HP drivers *not currently in use*, does printing to that queue have the same issue? If so, then it's a security issue. If not, then it's a print driver issue.