[Webinar] Streamline your web hosting managementRegister Today

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4545
  • Last Modified:

Windows 7 Clients - Print Spooler Hang - 1722 RPC Server Unavailable

We are in the course of a migration to Windows 7 Pro 64-bit. Clients print to network printers shared on a Windows Server 2003 R2 SP2 32-bit server. The new clients are experiencing intermittent and sporadic hangs in printing. Restarting the spooler on the client causes all hung jobs to print properly. The local event viewer shows events similar to the following when this occurs:

Event ID 372 in PrintService. Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: XXXXXX. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\JFWRKXXX. Win32 error code returned by the print processor: 1722. The RPC server is unavailable.

We've completely replaced the drivers for the printers on the server with a new driver model, and reinstalled the printers on clients, but that failed to address the problem. Printers are primarily Ricoh multifunction copiers with a smattering of HP LaserJets.
1 Solution
I ran into a similar issue with Ricoh's and XP OS's. We eventually had to delete the printers (and their many) from the print server and re-create them. For some stubborn printer models we had to use alternate drivers. If you can, pick a workstation that is experiencing the print issues, delete a specific network printer then delete and re-create it on the print server. On the test workstation, add the "new" printer and test.
jaredfaulknerAuthor Commented:
Thanks for your reply, David. Some interesting correspondences with our problem, although we have never had a problem on XP. Along the lines you suggested, we created all new shared printers with a different set of drivers (switching from the Ricoh model-specific driver to the Ricoh universal driver) and connected the clients to the new printers. It hasn't resolved our problem.
jaredfaulknerAuthor Commented:
We ended up migrating all of our print queues to a Windows 2008 R2 x64 server (from Windows 2003 R2 x86 server). This resolved the problem, presumably because of the "bitness" of the server, though I don't fully understand why.
Old comment, but I decided to post this anyway.

Check this link to find some details of this problem:

I struggled with this issue myself and discovered this KB article (KB2269469)


Essentially Windows 7 (32 and 64 bit) attempt to use Asynchronous RPC Protocol when trying to print  to the network printer but Windows Server 2003 does not support this protocol.

You can either upgrade your print server to Windows Server 2008 or apply a registry key to the Windows 7 client computer which tells the client computer not to use the asynchronous RPC protocol.

Add this reg_dword:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Printers\EnabledProtocols with a value of 6

I don't think that the problem has anything to do with the "bitness" of the server as described in the solution.

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

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