Quantcast
Channel: Print/Fax forum
Viewing all articles
Browse latest Browse all 3156

Users periodically cannot print unless printer is activated from the Windows Server 2008 R2 server first

$
0
0

We are running a print server on Windows Server 2008 R2 to manage our printers. At some point during the day, some, but not all, persons cannot send print jobs to any of the various printers. If I remote into the server and print a test page to a particular printer it will work fine, and only then can the affected users print on that printer. After a period of time, this recurs.

Going through the event viewer the event ID is 513, the category is "Routing print spooler command(s)", the OpCode is "Spooler Operation Failed", the general information supplied is "Group Policy was unable to add per computer connection [printer path and name]. Error code 0x7b. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server." The error code is occasionally 0x709.

Group Policy was unable to add per computer connection \\AROGSERVER\Central BW 3-Dell 2335. Error code 0x7b. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.


Viewing all articles
Browse latest Browse all 3156

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>