Integration Builder - Print Command Script fails to print
Hi, I'm using BarTender 2016 R1 on a Windows 7 Professional SP1 X64 computer and printing to a Zebra Z4M (300dpi). I'm logged on as a local Administrator and have full administrative privileges. The Zebra Z4M (300dpi) is networked and the drivers have been installed and normal printing via BarTender designer works with no issues.
I'm using Integration Builder and following the tutorial at https://support.seagullscientific.com/hc/en-us/articles/227354787-Print-Document-Using-Print-Command-Script-Video-9-40-
and I'm experiencing printing issues.
A template with the name 20X30mm_TEST.btw was prepared and connected via database connection to a Test001.txt file (following the instructions in the video tutorial on the link provided). The Test001.txt file contains the below information.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
BusinessName,ContactName,Position,Address1
Around the Town,Jerome Davis,Buyer,1220
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
When using BarTender designer, the template prints with no issues. However, when using a script named Text001.dat that has the following scripting contents:-
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
%BTW% /AF=C:\LabelTemplates\20X30mm_TEST.btw /D="C:\BarTender_StarlimsTrigger\Test001.txt" /PRN="Zebra Z4M (300 dpi)" /R=3 /P /DD
%END%
BusinessName,ContactName,Position,Address1
Around the Town,Jerome Davis,Buyer,1220
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I'm getting an error message of
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
A Windows error code was returned: 1722
Error message: The RPC server is unavailable.
There are several possible reasons:
1) The printer is not turned on or is off line. Try printing a test page from Windows.
2) The printer does not exist on your system or network.
3) Security settings prevent access to the printer.
4) If you use a network for printing, there may be a problem with the network connection or the printer driver.
5) There may not be enough memory available. Try closing files and programs you aren't using.
6) The printer driver is installed incorrectly. Try reinstalling the printer driver.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
From the BarTender Administration Console, the message history shows that the trigger works with the input data file 'Test001.dat' being detected and renamed as 'Test001.txt'. The 'Print Command Script' is executed but BarTender cannot use the printer to design, print or export a template due to a printer setup problem.
We have tested The BarTender Integration Service and also BarTender System Service as being logged on a local account (NT authority) and also as local administrators. We are still getting the same error message. Under 'devices and printers', the 'Zebra Z4M (300 dpi)' printer has security set to allow Administrators and users printing rights. The relevant folders in the C: drive that contains the 20X30mm_TEST.btw template and Test001.dat files are also set such that standard users and administrators have full rights.
I'm out of ideas on what else to try and I'd appreciate anyone may provide any advice on how to troubleshoot this issue. Feel free to let me know if more information is required on the described issue.
-
Not sure, certainly sounds like permissions issue, have you tried give full access not just printing rights to the printer, and/or tried printing to a different printer to see if that works? Also as Windows by default loads the Zebra ZDesigner driver, try installing and testing it using the Seagull driver instead if you haven't already,
0 -
Hi Peter, thank you for your suggestions. We did think it looked like a permissions issue. We tried giving full access to the user account and to the relevant folders. We also tried printing to a different printer. We uninstalled and re-installed the Zebra printer drivers. We uninstalled and re-installed BarTender 2016 R1. We did all of these even on a different computer that had the same setup. None of the above resolved the issue. I submitted a ticket to Seagull support. They indicated that there were bugs in BarTender 2016 R1 and that BarTender 2016 R7 should be installed. We followed their suggestion. We uninstalled BarTender 2016 R1. Restarted the computer. Installed BarTender 2016 R7. The issue was then totally resolved. We didn't change anything other than installing version R7. Seems like the issue was due to some bugs in version R1. Hope this helps someone else if they face the same issue. Thanks again Peter for your suggestion.
0 -
No worries, I should have picked up that you were running R1 and not the latest version and suggested you upgrade to that as in the past has fixed the odd issue I have come across. Glad you are now up and running.
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
3 commentaires