Print spooler affecting Word
Hi
We are having issues with a 2016 RDS box that office apps (specifically word) fail to load. We are seeing the print spooler service causing this as when we stop it word loads.
We also had printers failing to map via GPO recently so we think both are related. I managed to get the print driver issue working by copying C:\Windows\System32\spool\DRIVERS from a working RDS server to this one.
Ideas?
ASKER
Here's a couple from Administrative Events:
The print spooler failed to load a plug-in module C:\Windows\system32\spool\DRIVERS\x64\3\CNLB0MUI_D516C.DLL, error code 0x7E. See the event user data for context information.
Group Policy was unable to add per computer connection \\server\Printer11. Error code 0x3EB. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.
Driver install failed, result=0x8024500C for devnode 'SWD\PRINTENUM\{A51E4EF1-005C-4DFE-BFE2-C6F91EC9717B}'
and from - Microsoft - windows - print service - admin:
Group Policy was unable to add per computer connection \\server\Printer1. Error code 0x6. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.
The print spooler failed to load a plug-in module C:\Windows\system32\spool\DRIVERS\x64\3\CNLB0MUI_D516C.DLL, error code 0x7E. See the event user data for context information.
Group Policy was unable to add per computer connection \\server\Printer11. Error code 0x3EB. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.
Driver install failed, result=0x8024500C for devnode 'SWD\PRINTENUM\{A51E4EF1-005C-4DFE-BFE2-C6F91EC9717B}'
and from - Microsoft - windows - print service - admin:
Group Policy was unable to add per computer connection \\server\Printer1. Error code 0x6. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
I would agree that it is driver related from what i have seen. I eventually removed the printers from the GPO that was applying to this RDS box which made no difference (the plan was to use RDP redirect). Eventually we restored from backup which is currently working.
Worryingly i still see some printers applying to the RDS server for users (along with redirected ones) but Admins are not seeing these, and just the redirected printers.
Worryingly i still see some printers applying to the RDS server for users (along with redirected ones) but Admins are not seeing these, and just the redirected printers.
When the problem occurs, check to see what the default printer is and whether it is available.
Check the spool settings for the default printer and if "start printing immediately" is set, change it to "print after job is complete."