An operation was attempted on a nonexistent network connection

Mitchell Taylor

• 22 de julio de 2018 23:55

Hi,

We have an integration that's deployed as a webservice for the purpose of integration with our ERP application.

We've encountered an issue where, sometimes during a label print request, the integration will error with the following Messages:

The I/O operation has been aborted because of either a thread exit or an application request

An operation was attempted on a nonexistent network connection

When this happens, subsequent print requests from the integration will fail, with an error along the following lines:

Print job 'LABEL_TEMPLATE.btw' did not complete due to the following error: The print job for document 'C:\Users\Public\Documents\BT\Labels\ENV\LABEL_TEMPLATE.btw' and printer 'Test_Label_Printer' has stalled. A restart will be attempted. If the problem persists verify that the printer is online, able to process the print job, and the network connection (if present) is valid. If the print job is known to take a significant amount of time to print consider increasing the print scheduler's unresponsive job timeout. See Seagull's online knowledge base at support.seagullscientific.com for more details.

In order to restore service, the Bartender Print Scheduler service needs to be restarted. Note, that a restart does not complete using the BarTender Administration Console, instead the process itself must be termined using Task Manager.

After the Bartender Print Scheduler has been killed and restarted, print requests are able to continue... until the issue recurrs. Usually about once per day.

Any help on this issue would be greatly appreciated.

0

• 

  Peter Thane

  ★ BarTender Hero ★

  • 23 de julio de 2018 15:57

  Hi Mitchell,

  I have seen something similar to this a while back with Commander (the forerunner of Integration Builder) and the issue turned out to be a problem with a networked printer I believe, where it was either dropping off the network periodically or else there was an IP conflict. I think it was the former but it was few years ago now so I cannot remember exactly anymore.

  It maybe worth monitoring the status of the printer, if you can and see if you notice anything untoward, plus it may also be worth contacting your local regional Seagull Tech Support team as it maybe something they can help you out with better than this user forum. There maybe more information hidden away in the various log files which the Tech guys can interrogate etc.

  Pete  

  0

Iniciar sesión para dejar un comentario.