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.
This issue occurs because the DependentFiles registry key for the driver that is used by the printer is blank in the registry. The DependentFiles registry key is under the following registry sub-key:
To work around this issue, use one of the following workarounds:
- You can repair, remove and then reconnect the network printer.
- You can apply the hotfix 2896881. For more information about the hotfix 2896881, click the following article number to view the article in the Microsoft Knowledge Base:
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.
Long logon time when you use the AddPrinterConnection VBScript command to map printers for users during logon process in Windows Server 2008 R2 SP1
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.