Jump to content

Recommended Posts

Posted

Really odd I have had complaints of random users not being able to print from random computers to a specific printer.

 

The problem seems to follow the user to different computers that have this printer attached. Print credits aren’t deducted and paper cut doesn’t report the job being sent.

 

If I log on as a test student account on to the same computer and print the same document as the problem student is, the print out is successful.

 

I have had some success in removing the local cached profile but symptoms seem to return.

 

It’s a hp laserjet m553 running on a server 2008r2 server deployed to windows 7 x64 clients. We have paper cut running on the server.

 

Some history

I recently changed the print driver to UPD following a problem where the original print driver caused desktop loading issues.

 

Since I have been having these random issues

 

Thanks

Posted

I have a student it happen too right next to me. Nothing appears in the application event log. I log her off and I log on to the same computer then print the same document it prints fine.

 

I remove her profile ask her to log on again resolved the issue. But I don’t know why.

 

There is a problem somewhere but haven’t got to bottom of what’s causing it.

 

It must be something in the cached profile but what???

Posted
What about the my settings folder on the server. rename it .old and allow a new one to be created at next log in? Before hand I would get her to log into a machine in which hasn't got her profile cached to pull the clean profile down.
  • 4 weeks later...
Posted
[ATTACH=CONFIG]48492[/ATTACH]

 

You may need to upgrade your papercut version as seen above.

 

If you need any help/further information message me.

 

Thanks for the suggestion. I have resolved the issue now. turned out to be a driver conflict on the workstations that had the printer deployed to.

 

I had changed the Driver from the HP model driver to the UPD and it basically made the originally problem mutate.

 

Clearing down the drivers on the computer and redeploying a rolled back HP model driver resolved my issue

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...