Jump to content

Recommended Posts

Posted

Hi guys me again!! It all seems to be happening this week. Roll on half term!! :wink:

 

We have two network printers that are installed on our server and then shared out to machines depending on their locatin which works fine its just when the user presses print to send to the printer it goes into the print que and dissapears like its been printed but the rpinter dosent do anything!! I have tried from the server and same thing. I have also restarted the print spooler on the server. Restarted the printers themselves. I can ping them logon to the online web interface thingy and everything its bizaare!!

 

Any one got any ideas??

 

Dan

Posted
This happens to me all the time since half term. When i restart the print spooler it works for one print then stops again. have been told it might be due to a print logger i have running so will be takeing it off and trying again on monday.
Posted

The below event log was logged what does it mean?? I have checked the security rights on the printer and every one can print and the administrator has ful control?!?! I am getting the same log for both of my printers that are not working.

 

"The document Test Page owned by administrator failed to print on printer R25_HPIJ1280. Data type: NT EMF 1.008. Size of the spool file in bytes: 196608. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 1. Client machine: \\MCC-FSA-01. Win32 error code returned by the print processor: 5. Access is denied."

Posted
Yes it did and they have been working fine for the past 10 months since we had the new network installed its just suddenly stopped working!!! Would it have anything to do with one of the HDD's dieing in the proliant server that the printers are installed on??
Posted

That's looking a lot like a permissions issue related to the print queue..

 

Has someone managed to "protect" the print queue somehow or altered the permissions in the GPO, etc.. ?

Posted

Gaahhhh - We get this all the time as well. It'll work for random lengths of time then suddenly stop again. It was much worse when the Mac spooler was running as well but I've disabled that. Restarting the service seems to work but it's very annoying that we can't pin it down to anything.

 

Our print server is a beefy Win 2003 R2 box, dual processor doing nothing but dishing print jobs to a dozen printers. No extra software is installed on it at all (except for the BE remote agent thingy).

 

HBJB

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...