"Test Page failed to print" error with Mobility Print and PaperCut Pocket/Hive
“Help! I just tried printing a test page from my Windows computer, and ran into an error message “Test page failed to print”. Why did this happen with Mobility Print, PaperCut Pocket or PaperCut Hive?”
We’ve heard of this happening after a user is trying to set up PaperCut Mobility Print, but an administrator has configured Group Policy to block IPP Printing. If so, you will see Event 372 with this error message in the Windows event logs:
“Win32 error code returned by the print processor: 1260. This program is blocked by group policy.”
In Pocket and Hive, the format of the spool file results in Windows hiding the actual error code and the message will appear as
“Data type: NT EMF 1.008. Win32 error code returned by the print processor: 0. The operation completed successfully.”
Check Group Policy
This setting can be found in Group Policy under Computer Configuration > Administrative Templates > System > Internet Communication Management > Internet Communication settings. Look for Turn off printing over HTTP and set this to disabled.
Some customers have stated they found the ADMX files from Microsoft security articles.
November 2021 and MDM connectivity policies
Check the Registry
Another way to check to see if this is configured is to look at the registry on the affected workstation.
- Open regedit.exe
- Navigate to
- Look for the key
DisableHTTPPrinting. If the value of this key is set to 1, the Print Spooler will block any IPP printing.
- Ask yourself if something on the workstation (such as Group Policy) is managing this setting and make the necessary changes.
Still have questions?
Let us know! We’d also love to find out if you’ve discovered a new cause for this error message. Feel free to leave a comment below or visit our Support Portal for further assistance.
Categories: Troubleshooting Articles , Mobility Print ,PaperCut Pocket and Hive KB Articles , Pocket & Hive Troubleshooting Articles