Assume that you have a printer being shared on a printer server that is running Windows Server 2008 R2. When you try to print a file from a Windows 7 client to the shared printer, printing fails. Additionally, the following event is logged on the printer server:
Product: <Windows operating system>Note
Symbolic Name: MSG_PRINT_ON_PROC_FAILED_EX
The document %1, owned by %2, failed to print on printer %3. Try to print the document again, or restart the print spooler.
Data type: %4. Size of the spool file in bytes: %5. Number of bytes printed: %6. Total number of pages in the document: %7. Number of pages printed: %8. Client computer: %9. Win32 error code returned by the print processor: %10. %11
The printer server may be running Windows Server 2008, Windows Server 2012, or Windows Server 2012 R2 instead.
This issue occurs because, in the registry on the Windows 7 client,
the DependentFiles registry key for the driver that is used by the printer is blank. The DependentFiles registry key is under the following registry subkey:
To resolve this issue, follow these steps:
- Apply hotfix 3001232
- Apply hotfix 2896881
Note Even though the hotfix refers to a Windows Server 2008 R2 issue, the hotfix can also be applied to Windows 7-based computers that encounter this issue.
To work around this issue, you can repair, remove and then reconnect the network printer.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates
When the issue occurs, you can see event 372 is logged in the PrintService Admin log. To do this, follow these steps:
- Open Event Viewer and then expand Applications and Services Logs.
- Expand the Microsoft folder.
- Expand the Windows folder.
- Expand the PrintService folder and then click Admin.