Article ID: 2864755 - View products that this article applies to.
Consider the following scenario:
When printing from a Windows client to a network printer, printing fails.
In the PrintService Admin log:
You will see Event 372 logged:
The document <name>, owned by <name>, failed to print on printer <printer>. Try to print the document again, or restart the print spooler. Data type: <type>. Size of the spool file in bytes:<size>. Number of bytes printed: 0. Client computer:<name>. Win32 error code returned by the print processor: 5. Access is denied.
For the driver used by the printer listed in the Application Event Log, the DependentFiles registry key under the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\<architecture>\Drivers\Version-3\<drivername> is blank.
To repair the printer, remove and reconnect the network printer that is using the problem driver.
To prevent the issue from occurring, apply the hotfix for KB 2896881 -
"Long logon time when you use the AddPrinterConnection VBScript command to map printers for users during logon process in Windows Server 2008 R2 SP1"
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Contact us for more help
Connect with Answer Desk for expert help.