Y
Yuranga
Hi all,
I work for a hosting company, we have many Windows 2012 R2 servers that we host for our clients.
We have never had this issue with any of our clients before, but we have brought a new company on board with a Server 2012 R2 Remote Desktop Services server and multiple Printers installed
The communication between the server and printer is through a site to site VPN, same as all of our other clients.
This one client for some reason has random printers stop working for no apparent reason.
When we inspect the printer we can access the web interface from the server going back through the VPN
The client can print to the printer locally fine from a PC
Scan to the server and Scan to email still work from the printer directly.
But any job that is sent to the printer sits there spooling indefinitely.
-Restarting the print spooler service does nothing
-Deleting the jobs does nothing
-Restarting the printer itself does nothing
-Deleting the printer and adding it again via the IP does nothing
The only way to fix it is to reboot the server and bam, its working again for a few days or weeks.
Restarting the server isnt a fix, it disrupts the client.
We do weekly reboots now which seems to have reduced the frequency of the issue, but if it happens during the week we have to reboot.
This guys seems to have the exact same issue as us but the answer for him doesn't work for me
Print job stuck in "spooling" state
Any idea?
This happens on HP, Fuji Xerox and Brother Printers. They have around 15 all up and its random each time.
Event Viewer shows this
Applications and Services Logs \ Microsoft \ Windows \ Print Service \ Operational
Event ID 842 Print Service
The print job 2 was sent through the print processor winprint on printer **PRINTERNAME**, driver FX DocuPrint CM405 df PCL 6, in the isolation mode 0 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox). Win32 error code returned by the print processor: 0x0.
Continue reading...
I work for a hosting company, we have many Windows 2012 R2 servers that we host for our clients.
We have never had this issue with any of our clients before, but we have brought a new company on board with a Server 2012 R2 Remote Desktop Services server and multiple Printers installed
The communication between the server and printer is through a site to site VPN, same as all of our other clients.
This one client for some reason has random printers stop working for no apparent reason.
When we inspect the printer we can access the web interface from the server going back through the VPN
The client can print to the printer locally fine from a PC
Scan to the server and Scan to email still work from the printer directly.
But any job that is sent to the printer sits there spooling indefinitely.
-Restarting the print spooler service does nothing
-Deleting the jobs does nothing
-Restarting the printer itself does nothing
-Deleting the printer and adding it again via the IP does nothing
The only way to fix it is to reboot the server and bam, its working again for a few days or weeks.
Restarting the server isnt a fix, it disrupts the client.
We do weekly reboots now which seems to have reduced the frequency of the issue, but if it happens during the week we have to reboot.
This guys seems to have the exact same issue as us but the answer for him doesn't work for me
Print job stuck in "spooling" state
Any idea?
This happens on HP, Fuji Xerox and Brother Printers. They have around 15 all up and its random each time.
Event Viewer shows this
Applications and Services Logs \ Microsoft \ Windows \ Print Service \ Operational
Event ID 842 Print Service
The print job 2 was sent through the print processor winprint on printer **PRINTERNAME**, driver FX DocuPrint CM405 df PCL 6, in the isolation mode 0 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox). Win32 error code returned by the print processor: 0x0.
Continue reading...