Bartender 2016: Failure to print after long freeze and successful sent to printer log 追蹤

0

About 1 in every 50 Bartender.ibtformat.printout() commands fail to print. The bartender automation will log a "BarTender successfully sent the print job to the spooler." and the corresponding print job information matches what is to be expect. However, it will not print. There are no errors thrown at bartender or print logs. On these cases were it fails it will take roughly 1.5 to 2mins from initial Bartender.ibtformat.printout() command to the logging of the "BarTender successfully sent the print job to the spooler." and print job info. Normally this 5-10 seconds. The templates are able to connect to the database to return proper values to data sources. 

Any help is greatly appreciated! 

4 意見

0
Avatar
Xabier Clemente
版主
評論操作 永久連結

Hello Marc,

Thank you for reaching us via our BarTender Community Forums!

In order to properly troubleshoot this issue, we would benefit from learning a little bit more about this issue you are having:

  • When did the issue first appear? Was this issue always present?
  • Can you print directly via BarTender Designer or does it fail as well?
  • Are there any other integrations running in your BarTender environment? Are all affected by this issue?
  • This being an intermittent issue we are experiencing, is there anything in particular about your environment which could be affecting the printing? Active AV's or the like?
  • Have you tried restarting the BarTender Integration Service? If this is a recent issue, perhaps restarting the service might do the trick.
  • Finally, what BarTender service release are you currently using? You can find this information by navigating to the "Help > About" tab on any of the BarTender companion apps.


Also, issues related to automating BarTender can be tricky to solve, if you have an active maintenance agreement with us, we would recommend reaching our support engineers here.

Thank you!

0
Avatar
Marc Popp
評論操作 永久連結

Thanks for the reply Xabier,

  • When did the issue first appear? Was this issue always present?

This has been happening since 11/21, and we have been running the same same setup for years with no issue. The have been code changes to the app since then, but nothing with regards to our print logic.

  • Can you print directly via BarTender Designer or does it fail as well?

We can print directly via BarTender Designer.

  • Are there any other integrations running in your BarTender environment? Are all affected by this issue?

Not sure what you mean by other integrations running. We have ~15 computers running this setup. It isn't happening on just one instance. The frequency in which it freezes up has been increasing since then. It used to be 2-3 a day when it first start and has now begun to happen 10-20 times a day. 

  • This being an intermittent issue we are experiencing, is there anything in particular about your environment which could be affecting the printing? Active AV's or the like? & What BarTender service release are you currently using? You can find this information by navigating to the "Help > About" tab on any of the BarTender companion apps.

Our setup is a .Net application that calls Bartender.ibtformat.printout() via Interop.BarTender.dll version 9.40.0.0. This uses a template created via the BarTender Designer 2016 R1 version 11.0.1.3045. This template has a database connection to a local MS SQL server to populate 3 data sources. Typically this call will take ~5 seconds. About every 1 in 50 will fail to print. It will freeze up the .Net application while it waits the ~1.5 min and will not receive an error from the service. I turned on logging in the Log Setup for both Log Messages and Log Print Job Information and in both I receive successful message with proper data in the print job information. Meaning it pulls the data out of the database fine so I dont believe the issue lies in the database connection. While it has the right data and has a message stating "BarTender successfully sent the print job to the spooler." it never actually prints.

  • Have you tried restarting the BarTender Integration Service? If this is a recent issue, perhaps restarting the service might do the trick.


The server running the service has been restarted multiple times since the issue began and that has not resolved the issue.

 

0
Avatar
JW LAW
評論操作 永久連結

Hi ,

I was experiencing the similar issue, may I ask is there a resolution for this issue?

0
Avatar
Peter Thane
評論操作 永久連結

As there have been no more comments on this for 2 weeks it looks to me like they may have raised a support ticket to try and resolve it. 

A couple of things I would suggest is make sure you are running the latest version of 2016 (R9) and possibly update the drivers too. 

登入寫評論。