LabelFormatDocument.Print taking over 2 minutes - need help with logging 追蹤



We have an application that is using the Print Engine API and at a couple of customers we are running into this issue where some prints are taking from 2 - 7 minutes! I've taken over the project and new to Bartender. Where can I enable logging to see what is going on? I've looked at the System Event Logs for this time frame and don't see anything.

Our software is installed on the same Server as the Bartender service. The printers are all connected to a second Server that has nothing else running on it.

Bartender 2016 Automation edition

This is from our Logs:

2017-05-10 09:34:30.4532939 Before Print

Radley.BarTender.exe Error: 0 : EventMonitor.GetEvents   Socket exception while connecting to DTRLABPRINT.   Exception message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

2017-05-10 09:36:37.0669519 After Print

Here is the code that produces the above log - a lot of the time everything works great - I'm trying to figure out HOW to debug the slow print jobs

Seagull.BarTender.Print.Messages messages;
loggingObject.WriteLog("Before Print");
Seagull.BarTender.Print.Result result = labelFormat.Print(printRequest.PrintJobName, out messages);
loggingObject.WriteLog("After Print");

The result will come back with success so it seems to ultimately print but it's holding up all the other print jobs.

Thanks in advance!

1 意見

Jasper Wen
評論操作 永久連結

 I recommend the following to start troubleshooting:

  • Verify that you are on the latest service release for your version of BarTender. Currently, our latest release is R3 for 2016. You can verify by going to help->about in BarTender.
  • I would also verify if printing the label directly through the BarTender designer application itself also exhibits the same issue to narrow down the issue.
  • You can enable logging in BarTender by going under help->administer->log setup->text file log tab->check log messages->click setup to specify text file logging location.

If you are still running into issues, please contact our tech support so we may open a support ticket to further troubleshoot.