Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1493
  • Last Modified:

Server 2003 printing problem--Event ID:6161

I have a file/print server that is exhibiting some strange printing behavior.
Server 2003 std SP1 patched.
The server has 25 or so printers setup, mostly HP's, a couple Sharp multi-functions,
a Dell and a Okidata.

I'll use the HP 9150 as the offending printer in my question.

The majority of them print just fine.  But a handful of them don't print.
The client doens't receive an error when the print job fails; it looks like it spools and prints just fine.

The event log however tell a different story.

Event ID: 6161

The document Microsoft Word - Personnel Policies 2006.doc owned by user failed to print on printer network printer. Data type: NT EMF 1.008. Size of the spool file in bytes: 32240. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client machine: \\X.X.X.X. Win32 error code returned by the print processor: 0. The operation completed successfully.

I have an open call with MS about this problem, and have tried so many things I can't remember them all.  With no luck.

Here is where it gets interesting.  
These same printers are setup on another server and print just fine.
When I add the user to the local admin group on the server, they can print.  Take them back out, no luck.
When I change the print drivers on the server from HP 9150 PCL6 (not inbox) to an inbox Laserjet 4,
the printer spits out a blank page.  So at this point SOMEthing is getting spooled.
Printing to the IP address works fine.

Things I've tried:

Every iteration of print drivers I could get my hands on.  MS wants me to use the inbox drivers.  I've tried almost all of them.  Can't get any more generic than the Laserjet 4.  That thing will print to anything.

Full control on C:\WINDOWS\system32\spool\PRINTERS on the server.

Changed the print processor from hpzppXXX to WinPrint, RAW data type.

Disabled bidirectional support.

I'm stumped folks.  And apparently MS is too.  This has been an ongoing issue for more than a few weeks.
So, any suggestions are welcome.  
0
trarthur
Asked:
trarthur
1 Solution
 
haim96Commented:
0
 
gopal_krishnaCommented:
To return the description of any error message in W2K go to a Command prompt and type: NET HELPMSG message# (e.g. "net helpmsg 63" returns "Your file waiting to be printed was deleted.").

I typed in the errors that you received, and voila:

 (0x5) Access is denied.

be back in a sec with more

Regards
Gopal Krishna K
0
 
trarthurAuthor Commented:
haim96:

I tried everything that is applicable to my environment.

I don't have any xerox printers.

The HP port issue doesn't apply.

Already granted Full Control to the Spool directory.

I've installed every driver that ships with Server 2003.

cleanspl.exe looks like it will wipe out all the printers on the server.  Some of them work just fine and are used
daily.  
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
trarthurAuthor Commented:
Gopal,

I know it's a rights issue, I just don't know where.
and from a cmd prompt on the server when I type net helpmsg 6161, I get:
The system cannot find message text for message number 0x1811 in the message file for NETMSG.

How were you able to return 0x5?
0
 
haim96Commented:
some times users need permission on registry keys.
(but it mostly for local connected device.... )
can you check if the driver have one and try to change the permission for it?
0
 
trarthurAuthor Commented:
haim96,

Look on the server or the client?  I'm thinking the server, but want to confirm.
0
 
haim96Commented:
yes,server.
try to look for any keys that relevent to the driver.
again, this issue is common problem for device on local machine not server.
but in your case it's worth to try.
0
 
trarthurAuthor Commented:
OK, I'll take a look.  Thanks!
0
 
trarthurAuthor Commented:
The solution turned out to be running the cleanspl.exe tool from MS.  I had already read the eventID.net tips, and haim96 suggested it also.
Don't know if I'm closing this question exactly right, but haim96 had made the suggestion and had I tried it a while back, I'd already have it solved. ;)

There is another tool called printmig.exe that will backup all of the printers on a server to a .cab file.  If you have a need to clean the print spooler or migrate many printers from one server to another, this tool will do the trick nice and quick.

Thanks everyone!
0
 
haim96Commented:
cheers!

:)
0
 
lhrslsshahiCommented:
Hi the solution requires you to subscribe to the event id site, please can you advise of the solution.

Thanks
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now