Sign in to follow this  
Followers 0
Almor

Print Spooler Hangs on Windows 7 with Event ID 372 - RPC error

2 posts in this topic

The network configuration is: Windows SBS 2003 server with Windows 7 32-bit clients. There are other servers on the network, but the SBS server is acting as the print server. Periodically various workstations will be unable to print to any printer. The print spooler service appears to be running normally, but the event log shows the following error message:

 

Log Name: Microsoft-Windows-PrintService/Admin

Source: Microsoft-Windows-PrintService

Date: 4/21/2010 12:09:57 PM

Event ID: 372

Task Category: Printing a document

Level: Error

Keywords: Classic Spooler Event,Document Print Job

User: **********

Computer: *************************

Description:

The document Local Downlevel Document, owned by jstartz, failed to print on printer {88F50B3B-808D-4015-9C4B-F340B5609B10}. Try to print the document again, or restart the print spooler.

Data type: RAW. Size of the spool file in bytes: 0. Number of bytes printed: 0. Total number of pages in the document: 0. Number of pages printed: 0. Client computer: \\WSP53. Win32 error code returned by the print processor: 1722. The RPC server is unavailable.

 

Restarting the print spooler service on the workstation solves the problem temporarily, about 90% of the time. Sometimes, however, it requires restarting the spooler service several times, or even restarting the computer. Also, it usually seems to happen with the first print job of the day, although we are not 100% sure that is the case.

 

This is very annoying and disruptive to our users at this site, and we've been unable to find any answers to this one so far. I have tried changing the registry settings on the workstations so that print jobs are rendered on the server rather than the workstation, but that doesn't seem to have helped.

 

Any ideas would be appreciated!

Tnx

0

Share this post


Link to post
Share on other sites

Starting in Windows Vista and in Windows 7 introduced Asynchronous RPC which speeds up communication to a Windows 2008/2008 R2 Server. Windows Server 2003 doesn't support this new protocol and when Windows 7 tries to communicate using Async RPC, this is most likely causing the temporary loss of communication.

 

The result is the blank driver tab and port tab.

 

The work around is to disable Async RPC by adding the following registry key on the Windows 7/Vista clients:

 

 

 

HKLM\Software\Policies\Microsoft\Windows NT\Printers\EnabledProtocols

 

Type: DWORD

 

Data: 6

 

Mark

0

Share this post


Link to post
Share on other sites

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
Sign in to follow this  
Followers 0