Integration failing - Bartender giving no useful error messages! フォローする

0
Avatar
Greg Iverson

Hi all!

I am not getting a 2nd response from tech support so I'm going to put this out there in case anyone can lend a hand :)

I'm running Bartender Enterprise Automation 2016 on Windows 10

I have a LIVE system that runs integrations great. I drop the .txt file into the scanned dir, it gets processed,and printed, the file goes away.

I have a new TEST system that will eventually replace the LIVE system. I've got the same version of Bartender installed. Running a 30-day trial so it's not activated yet and there's no license server running (as I can't deactivate the live system yet)

All printers are installed and named exactly as they are on the live system.

I copied the integration file from the live system, as well as all .btw files.

When I drop files into the dir on the test system they fail to run/print (and the file gets renamed with a ".failed" extension per my integration settings)

When I go into Integration Builder and view the results, it says:

--> "The input data file 'SHIPPER_ME.txt' was not processed because one or more actions failed to run. Review all integration actions, correct any failures, and resend the input data file."

Which integration action failed? What was the error? This is not helpful at all...

It also says:

--> "Failed to run action 'Print Command Script'. Details: "  (and then NOTHING here where the details would be helpful!)

These error messages are useless if they don't tell me what’s actually wrong! It's like the "Engine Light" of error logs :)

Here's the very simple file I'm trying to process. If I drop this into the live system it prints no problem:

%BTW% /AF="C:\LABELS\FORMS\SHIPPER_NEW.BTW" /D="C:\Labels\SHIPPER_ME.dat" /PRN="S4MWBS3" /C=1 /R=3 /P /DD
%END%
<CR>Test Company Name<CR>1234 Test Road<CR>SUITE 100<CR>Golden Valley, MN 55427|<CR>DEPT OF TOURISM<CR>DAMARI ACOSTA<CR>111 TEST ST<CR>STE 7<CR>FREDERIKSTED, VI 00841|700193616||00006509340002418341

 

When I first opened the ticket a week ago I assumed my problems stemmed from the fact that I was running an un-activated version without a license server so I asked for a test activation code.

They responded that I didn't need a test code and that the 30-day trial would function exactly the same as a fully licensed copy, and that my integration was not failing because of that....OK, but then WHY is it failing?

Printer problem? (it prints fine when I do a manual test from within Bartender)

License problem? (they say I don't need a license and the 30-day test will do)

The system knows what caused the error but it just isn't telling me anywhere I can see.

Does anyone know if there's a log file anywhere that will actually tell me what it doesn't like about the scripts?

I've included a couple pics of the screen showing the errors..

Thanks everyone!

-Greg

 

 

5 コメント

0
Avatar
Kellan Marvel
コメントアクション Permalink

Please, please, please tell me you solved this one?  I'm experiencing the exact same problem, pulling my hair out...

0
Avatar
Pete Thane
コメントアクション Permalink

Are you running it as a test in Integration Builder to make sure it works first rather than just deploying it as it looks like the OP has done as you may get more information from this? 

 

1
Avatar
Greg Iverson
コメントアクション Permalink

Hey Kellan!

At some point with a new version of Bartender they really messed up error-handling. I think they were trying to improve it, but it ended up being very unpredictable and really messed up our forms! :)

Here's what I had to do to fix the issue:

Go into PROPERTIES on each of the fields on your form (I had to do this manually for about 150 fields because the new error-handling options were added by default to all of them). 

Go into ERROR HANDLING

A box will come up that says "ERROR CONDITION" and will list 5 different options.

Choose "CONTENT DOES NOT FIT" and UNCHECK every option listed except CLIP TO FIT - leave that one checked.

Next go into "DATA IS EMPTY" and uncheck ALL those options as well (clip to fit will probably be grayed out and checked)

There are also 3 additional categories called DATA IS INVALID, FILE IS NOT FOUND, and SCRIPT ERROR...I didn't change anything in those. It was just the CONTENT DOES NOT FIT and DATA IS EMPTY categories that caused me a ton of problems.

That should hopefully fix your issue. If you keep getting it you could also try changing the options for the additional 3 categories.

The biggest culprit is the "WRITE MESSAGE TO LOG" option. Even if you have ALL the other options unchecked as I mentioned them, if it writes an error to the log it will cause the dreaded ".error" extension to be added to your integration data file, and it will not execute it.

Sure, it stores the (very undetailed and useless) error in the log, but even though you have told it NOT to display a warning, invalidate label, ask to abort, always abort, it will still bomb if the WRITE MESSAGE TO LOG is checked. Bartender support couldn't explain that one... :)

Make sure after you change a form that you stop and restart the Windows integration-related services. Not sure how you are running your integrations...it's a bit confusing as you can run them via a service with no Bartender program up and running, or you can open up Integration Builder and tell it to start capturing and executing your data files there. That method lets you view errors live which helps for testing, but when you exit Integration Builder I sometimes have a hard time getting it to "run in the background" and watch for my data files from that point on.

Anyways, sorry to babble on!

Let me know if any of this helped :)

-Greg  

 

0
Avatar
Kellan Marvel
コメントアクション Permalink

@Greg Iverson,

 

Thanks for taking the time to write that up, I really appreciate it.  I'm going to try what you suggested over the weekend when I have downtime to mess with the system.

 

Best,

Kellan

0
Avatar
Pete Thane
コメントアクション Permalink

You dont need to adjust every field individually, if you select multiple fields you can adjust the settings for all the fields at once but only where those options apply to all the field types selected, as per the image below:

 

サインインしてコメントを残してください。