Printer GPO - [ hr = 0x80070706 "The print processor is unknown." ]

1

Having some trouble on Windows Server 2012 / Windows 8 getting a Printer GPP (computer) to work.

Printer GPP is created in:

Computer config -> Preferences -> Control panel -> Printers

but fails with the error:

[ hr = 0x80070706 "The print processor is unknown." ]

Any suggestions what might be causing this?

group-policy
windows-server-2012
windows-8
printer
asked on Server Fault Apr 15, 2013 by NickC • edited Mar 1, 2014 by (unknown user)

3 Answers

2

See: Print Processor

Either the default print processor is missing or corrupt (KB153355) or that driver you are trying to install with that print queue requires its own print processor that is unavailable on your client machine. This can be caused for a number of reasons, but in my experience it is most commonly a 32-bit/64-bit mismatch or you are missing the driver's specific print processor. I generally unpack print drivers that come in .EXEs using 7Zip, locate the appropriate DLLs and the .INF file to avoid installing all the other packaged crap that comes with print drivers these days. Unfortunately, this method of manual driver installation will not install that drivers print processor and not all drivers can use the default Windows print processor.

You can use Print Management to see what drivers are available and what print processor you are using. Verify that the print processor is available on the client. Try attaching ProcMon to the spoolsv.exe on your client and manually add the printer. Printing Services errors are notoriously vague and misleading. Looking at the logs in Microsoft-Windows-PrintService should help you narrow your search in ProcMon, as often Windows will log what .DLL from the driver failed to find the print processor.

answered on Server Fault Apr 15, 2013 by (unknown user)
0

I've seen that when there is issues with the print driver. You might manually add a printer to test out the driver is good.

I also found this http://support.microsoft.com/kb/153355

answered on Server Fault Apr 15, 2013 by Nixphoe
0

Answer now found!

The answer is to change the Print Processor on the Server-side

GLS60APR, RAW to Winprint, RAW.

It seems that the Printer GPP does not deal correctly with a non winprint processor whereas a manual connection to the printer does install the GLS60APR print processor.

Note: Looks very much like a bug that will require a Microsoft fix.

answered on Server Fault Apr 16, 2013 by NickC

User contributions licensed under CC BY-SA 3.0