Bartender Stops Printing After 2 Labels Windows Error 1804 Bartender Error 3721 追蹤

0
Avatar
Legacy Poster

Hi I am seeing a rash of users with errors when printing today that seem to be caused by a recent Windows Security patch.  i had at least 6 clients call today saying the system printed 2 labels then stopped printing.  When i updated commander to run as an application then show all running Bartenders, it prints the first two labels, then on the third puts up an error screen saying windows error 1804 occurred (invalid data type??) and also shows bartender message 3721.  when i close that window it shows bartender error 3628.  nothing will print after that.  Stopping/STarting commander will allow two more labels to print then we get the same error again.

 

We noticed a windows security patch (4 actually) went in last night, so we uninstalled them, rebooted, and the error went away.

 

just thought i would post this in case others are seeing the same errors.

 

thanks

Gary

4 意見

0
Avatar
Gene Henson
評論操作 永久連結

Thanks for the post, Gary.

 

You're correct that the issues are caused by recent Windows updates. We've created a support article on the topic here: https://support.seagullscientific.com/hc/en-us/articles/225047808-Windows-Update-causing-BarTender-errors

 

We're currently engaged with Microsoft and are looking for a permanent solution to the problem.

0
Avatar
Legacy Poster
評論操作 永久連結

I've got fairly important clients who print 1000s of labels a day on a production line, this has now held up there production line. I've noticed if they quit back out of Bartender and get back in it prints again for a couple of times. If there is any solution please let me know asap.

0
Avatar
Ian Cummings
版主
評論操作 永久連結

Rod Bolt: The behavior you mention fits in exactly with the problem in the support article that Gene gave a link to.  We recommend you roll back the offending KB until further notice.  We will update the support article once we know more.

0
Avatar
John McKenzie
評論操作 永久連結

Thank you. This worked for us.

Windows Server 2012 R2

Uninstalled KB3177725, restarted the server and relevant services and we were back in action.

Any E.T.A. on a permanent fix?

登入寫評論。