Windows Server 2016 Group Policy Printers errors
Hello! I have a Windows Server 2016 print and file server, and I am using Group Policy to publish about 40 network printers to approximately 150 computers/users.
The printers are published using Group Policy on a Windows Server 2016 domain controller. The printer queues are defined on a Windows Server 2016 file and print server. There are about 28 Canon Printers, all using the latest ‘Canon Generic Plus v2.40 PCL 6’ driver. All of the client workstations are running Windows 10. I have seen that some of the client computers are running Windows 10 21H2 .
The problem we are seeing is on the client workstations, not on the Server.
The printers have been working (mostly) fine for a year. A couple days ago, the users started experiencing printing issues. One of the definite problems we are seeing is the Print Spooler service on about half of the workstation/client computers is crashing.
In the Windows logs, I am seeing several errors listed. Mostly, when I see an error message indicating the workstation print spooler has crashed, it is immediately preceded by an error with the source from CanonPrinterDriver3
Here is an example of the type of error I am seeing on a client workstation
-------------------------------------------------------
Log Name: Application
Source: CanonPrinterDriver3
Date: 6/28/2021 12:26:55 PM
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: xxx
Computer: xxx
Description:
Entry Function: DrvPrinterEvent, Base Address: 00007FFD25170000, Exception Address: 00007FFD9CC9D990, Exception Code: ACCESS_VIOLATION
-----------------------------------------------------------
Here is the next log entry, where the print spooler crashed:
------------------------------------------------------------
Log Name: Application
Source: Windows Error Reporting
Date: 6/28/2021 12:26:55 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: xxx
Description:
Fault bucket 1497040562230863077, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: spoolsv.exe
P2: 10.0.19041.1052
P3: 3a1aec78
P4: StackHash_afeb
P5: 10.0.19041.1023
P6: 7977b9de
P7: c0000374
P8: PCH_D0_FROM_ntdll+0x000000000009D974
P9:
P10:
Analysis symbol:
Rechecking for solution: 0
Report Id: 22e299fc-0495-4fbb-a935-6148d6e70317
Report Status: 268435456
Hashed bucket: ea484d68673c3afa64c68e75ae1f24e5
Cab Guid: 0
--------------------------------------------------------------------------
I don’t know if the Canon error is the cause of the workstation spooler crashing, or it the Canon error is a symptom of the problem.
I also see Warnings on some computers regarding Group Policy issues with the printers. Here is an example:
--------------------------------------------------------------------
Log Name: Application
Source: Group Policy Printers
Date: 6/28/2021 1:45:38 PM
Event ID: 4098
Task Category: (2)
Level: Warning
Keywords: Classic
User: SYSTEM
Computer: DERMDC01.dermatologyinc.com
Description:
The user 'P16-Meth Front Ofc' preference item in the 'Derm - Printers {80B56EE4-5063-4C72-98D4-FA4BD0CBC9AB}' Group Policy Object did not apply because it failed with error code '0x80070bc4 No printers were found.' This error was suppressed.
----------------------------------------------------------------
I appreciate any thoughts you may have!
Brian
The printers are published using Group Policy on a Windows Server 2016 domain controller. The printer queues are defined on a Windows Server 2016 file and print server. There are about 28 Canon Printers, all using the latest ‘Canon Generic Plus v2.40 PCL 6’ driver. All of the client workstations are running Windows 10. I have seen that some of the client computers are running Windows 10 21H2 .
The problem we are seeing is on the client workstations, not on the Server.
The printers have been working (mostly) fine for a year. A couple days ago, the users started experiencing printing issues. One of the definite problems we are seeing is the Print Spooler service on about half of the workstation/client computers is crashing.
In the Windows logs, I am seeing several errors listed. Mostly, when I see an error message indicating the workstation print spooler has crashed, it is immediately preceded by an error with the source from CanonPrinterDriver3
Here is an example of the type of error I am seeing on a client workstation
-------------------------------------------------------
Log Name: Application
Source: CanonPrinterDriver3
Date: 6/28/2021 12:26:55 PM
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: xxx
Computer: xxx
Description:
Entry Function: DrvPrinterEvent, Base Address: 00007FFD25170000, Exception Address: 00007FFD9CC9D990, Exception Code: ACCESS_VIOLATION
-----------------------------------------------------------
Here is the next log entry, where the print spooler crashed:
------------------------------------------------------------
Log Name: Application
Source: Windows Error Reporting
Date: 6/28/2021 12:26:55 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: xxx
Description:
Fault bucket 1497040562230863077, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: spoolsv.exe
P2: 10.0.19041.1052
P3: 3a1aec78
P4: StackHash_afeb
P5: 10.0.19041.1023
P6: 7977b9de
P7: c0000374
P8: PCH_D0_FROM_ntdll+0x000000000009D974
P9:
P10:
Analysis symbol:
Rechecking for solution: 0
Report Id: 22e299fc-0495-4fbb-a935-6148d6e70317
Report Status: 268435456
Hashed bucket: ea484d68673c3afa64c68e75ae1f24e5
Cab Guid: 0
--------------------------------------------------------------------------
I don’t know if the Canon error is the cause of the workstation spooler crashing, or it the Canon error is a symptom of the problem.
I also see Warnings on some computers regarding Group Policy issues with the printers. Here is an example:
--------------------------------------------------------------------
Log Name: Application
Source: Group Policy Printers
Date: 6/28/2021 1:45:38 PM
Event ID: 4098
Task Category: (2)
Level: Warning
Keywords: Classic
User: SYSTEM
Computer: DERMDC01.dermatologyinc.com
Description:
The user 'P16-Meth Front Ofc' preference item in the 'Derm - Printers {80B56EE4-5063-4C72-98D4-FA4BD0CBC9AB}' Group Policy Object did not apply because it failed with error code '0x80070bc4 No printers were found.' This error was suppressed.
----------------------------------------------------------------
I appreciate any thoughts you may have!
Brian
Last Comment
ASKER
Because there were indications the problem may be the Canon printer driver, yesterday I deleted all of the printer queues on the print server that were using that Canon printer driver. I was not able to easily delete the printer driver, but eventually was able to remove it. I downloaded a new copy of the printer driver, and installed it. Then I re-created all of the printer queues . Then in the GPO that publishes the printers, I re-pointed each entry to point to the respective "new" printer queue.
This morning, I saw the same errors on the client workstations.
This morning, I saw the same errors on the client workstations.
ASKER
Mr. Porter, thank you for the reply. I called Canon Support Helpdesk earlier today, and he confirmed that I am using the latest "Canon Generic Plus PCL 6" driver, version 2.40 .
I will look at the link you provided, thank you.
I should also note that I saw a Windows 2016 Server Cumulative update had been applied 8 days ago, so I removed that update from the server early this morning, in case that was the cause of the problem. Removing that update didn't seem to have any affect, and the problem continued.
I will look at the link you provided, thank you.
I should also note that I saw a Windows 2016 Server Cumulative update had been applied 8 days ago, so I removed that update from the server early this morning, in case that was the cause of the problem. Removing that update didn't seem to have any affect, and the problem continued.
Hello,
most of the printer drivers support server side rendering vs client side rendering.
You may check if it changes something, if you choose server side rendering (what moves the workload from the client to the server).
most of the printer drivers support server side rendering vs client side rendering.
You may check if it changes something, if you choose server side rendering (what moves the workload from the client to the server).
The Canon driver is only a part of the equation. What are you running for firmware on the Canons? I just went through this issue, so I can appreciate your frustration.
ASKER
Hello! Thanks for the question Mr. Porter. I checked on one of the larger Canon printers (imageRunner Advanced 6555 III ) and it shows the last firmware update applied 04/07/2021.
I checked on this particular MFP, because I had a call from a person who couldn't print to it through the network printer queue. As with many of the Windows computers we have looked at, the local workstation Printer Spooler service was crashed. I configured the Printer Spooler service to restart after every failure. What I see in the logs after that is the spooler crashing and restarting constantly.
For this user, I created a "local" printer queue that prints directly to the TCP/IP address of the printer, instead of using the printer queue defined on the print server and published via Group Policy. Since I created that local printer queue, I no longer see errors in the WIndows Application log that indicate the spooler has crashed. Coincidence?
I checked on this particular MFP, because I had a call from a person who couldn't print to it through the network printer queue. As with many of the Windows computers we have looked at, the local workstation Printer Spooler service was crashed. I configured the Printer Spooler service to restart after every failure. What I see in the logs after that is the spooler crashing and restarting constantly.
For this user, I created a "local" printer queue that prints directly to the TCP/IP address of the printer, instead of using the printer queue defined on the print server and published via Group Policy. Since I created that local printer queue, I no longer see errors in the WIndows Application log that indicate the spooler has crashed. Coincidence?
What about the printer queue on the local machine now? Is here the spooler stable?
I would always connect spooler problems to the according driver or at least left over fragments.
The ACCESSS_VIOLATON points me the a memory execption.
You may have a look here:
https://blog.pcrisk.com/windows/12957-print-spooler-keeps-stopping
You can stop at the CCleaner and what follows.
But i can make sense to clean up an client, as you set everything via policy, the client gets back what it needs.
I would always connect spooler problems to the according driver or at least left over fragments.
The ACCESSS_VIOLATON points me the a memory execption.
You may have a look here:
https://blog.pcrisk.com/windows/12957-print-spooler-keeps-stopping
You can stop at the CCleaner and what follows.
But i can make sense to clean up an client, as you set everything via policy, the client gets back what it needs.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Windows OS
This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
I know Windows Updates have done a few things recently that are causing all sorts of problems with PCL6 drivers. The first thing I would do is look to Canon's website to see if they have released both driver and firmware updates for the printers that you are having problems with. It looks like they have released driver updates on 4/19/2021, so that's probably worth a look:
https://sg.canon/en/support/0100952701