Posted by: Jeremy Benisek (CyberAxe) Don't Panic Business Technologies | July 2, 2014

Nasty Windows 2008 R2 RDP Redirect Printer works but printing fails bug

Event ID 372: The document failed to print
The client printer shows up on Windows 2008 R2 but can’t print

The client printer shows up on Windows 2008 R2 but can’t print

Situation: The client installed TS on their DC running on Windows 2008 R2. After that the remote clients using RDC can’t send print job to the printer connecting to remote computer. The printer redirection works fine and we can see them, but when we try to send the print job, it doesn’t print. The Event Viewer also logs this message:

Log Name: Microsoft-Windows-PrintService/Admin
Source: Microsoft-Windows-PrintService
Event ID: 372
Task Category: Printing a document
Level: Error
Keywords: Classic Spooler Event,Document Print Job
User: chicagotech.local\blin

The document Untitled – Notepad, owned by blin, failed to print on printer 041hp4050 (redirected 4). Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: 23044. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\laptop. Win32 error code returned by the print processor: 5. Access is denied.

Troubleshooting: It is not recommended to install Terminal Services on a Domain Controller for the security reason. For many small business, they don’t have choice, the resolution is using cacls command to assign permission to spool by following these steps:

1. Click Start, search for cmd.exe

2. Right click on cmd.exe

3. Click on ‘Run as Administrator’

4. Type “C:\” w/o the quotation marks and then Press Enter.

5. Type CD\Windows\System32\Spool and then Press Enter.

6. Type Cacls.exe PRINTERS /e /g users:C and then Press Enter.

7. Restart the computer (I didn’t have to reboot)



  1. Thanks for sharing this information. This particular method didn’t work, but I found a workaround that worked reliably. I manually set up a local printer on the terminal server, using the LPT1 port, and then changed that port to the TS001 port for the remote user that was failing. The printer works, and the user can log off and back on and the remote printer will redirect properly.

  2. Hi and THANKS ALOT!
    This worked great for me. I have a 2008 R2 with DC and Terminal on. I have tried to figuere out this error for many hours now. The worst part is that if I used RDP Client 5.2 it worked great, but newer (Rdp 6.1 (or 6.3.6900)) it failed… But this solution made my day! Thx again.
    Regards, Roar

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


%d bloggers like this: