Print Spooler Crashing
We have Bartender 9.2 installed on one of our servers using Seagull barcode website, 1.1.19. We have Brady printers using updated Seagull drivers. This has given us intermittent problems for a while but in the last couple of days, it just isn't working. We upgraded the server from Vista to 2008 R2. We are finding we cannot print to any printers defined to this server regardless of whether we use this barcode website or whether we attempt to print to one of the printers on this server using Bartender installed on a desktop or via Commander.
It seems to be bringing down our print spooler. Here are a few messages we've gotten lately:
The Print Spooler service terminated unexpectedly. It has done this 10 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
Error: Attempt to access invalid address.
Caught in [Network_ClientThread::ThreadProc]
MiniDump File: C:\ProgramData\Seagull\Drivers\Dump\sscrash_0012.dmp
The Print Spooler service terminated unexpectedly. It has done this 9 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
Error: Attempt to access invalid address.
Caught in [Network_ClientThread::ThreadProc]
MiniDump File: C:\ProgramData\Seagull\Drivers\Dump\sscrash_0011.dmp
The forums will not permit me to attach the crash dmp file, "Error You aren't permitted to upload this kind of file". Do you know why our print spooler keeps crashing? Any ideas about what we can try to resolve this?
Thanks!
Suzanne
It seems to be bringing down our print spooler. Here are a few messages we've gotten lately:
The Print Spooler service terminated unexpectedly. It has done this 10 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
Error: Attempt to access invalid address.
Caught in [Network_ClientThread::ThreadProc]
MiniDump File: C:\ProgramData\Seagull\Drivers\Dump\sscrash_0012.dmp
The Print Spooler service terminated unexpectedly. It has done this 9 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
Error: Attempt to access invalid address.
Caught in [Network_ClientThread::ThreadProc]
MiniDump File: C:\ProgramData\Seagull\Drivers\Dump\sscrash_0011.dmp
The forums will not permit me to attach the crash dmp file, "Error You aren't permitted to upload this kind of file". Do you know why our print spooler keeps crashing? Any ideas about what we can try to resolve this?
Thanks!
Suzanne
1
-
Today this setup is letting us print - sort of. If we print, the printer displays Ribbon Error. But, if we open the printer and close it, the label will print. I'm not sure our print spooler problem has been resolved, this might just be an additional flavor of the problems we are having with this. 0 -
This might be due to some sort of corruption on your drivers, could you try fully removing them, rebooting the machine and reinstalling them from a new download? Make sure to remove your drivers using our Seagull Driver Wizard (DriverWizard.exe). By default it should be located in the "C:\Seagull" folder (or on the folder you unpacked the drivers when you download them the first time).
You'll be able to download them from the below webpage:
http://www.seagullscientific.com/aspx/download-free-windows-printer-drivers-for-Brady.aspx
Note that it's important that all Seagull drivers on your system (regardless of the printer they are designed for) are of the same version as they use a number of shared resources. If some drives are of a lower version it could get the other ones corrupted and show unexpected behaviour.
If this doesn't solve your issue, please send us the dump file generated to our Tech Support email, you'll find all our emails for our different offices on the below webpage:
http://www.seagullscientific.com/aspx/technical-support.aspx0 -
Thanks for your reply, Fernando.
I confirmed that the print drivers were installed using your recommended method. I have emailed tech support with several recent dump files. Thanks!0
Iniciar sesión para dejar un comentario.
Comentarios
3 comentarios