Windows Spooler Failures Follow
We are currently using Bartender version 9.4 SR3 /Build 2781 on a Windows 2008R2 Server to print around 12-15 K barcode tags daily. We have been having multiple problems with the tags starting/stopping/reprinting since the update to SR3, so we've been running the system in application mode for some time. Application mode seems to better manage the heap resources and keep the system from reprinting tags in the middle of a run.
This being said, we have now found that the system spooler will crash/fail upwards of 5 times a day. This stops the printing to the plants who are waiting for the tags, and is presenting a support nightmare for me....hence my post to the gentle board.
The errors we are seeing in BT indicate that the printer is "no longer available" because the spooler has crashed. When I look into the Windows system log....I can see errors indicating the spooler has stopped, and various errors which point to specific printers stating " port number: XXXX Printer number: XXXX - attempt to access invalid address Caught in statusMon: threadproc"
there is no rhyme or reason to this...as it happens across the board and to multiple printers.
If anyone has any ideas as to where to look while I wait for seagull...I'd appreciate it.
SAP Basis Admin
Please sign in to leave a comment.