Saltar al contenido principal

Búsqueda

Búsqueda

Integration failing - Bartender giving no useful error messages!

Comentarios

8 comentarios

  • Avatar
    Kellan Marvel

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

    0
  • Avatar
    Peter Thane

    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? 

     

    0
  • Avatar
    Greg Iverson

    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  

     

    1
  • Avatar
    Kellan Marvel

    @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
    Peter Thane

    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:

     

    0
  • Avatar
    Ekin Tertemiz

    I am having the same issue with Bartender Automation 2016 on Windows 10. Unfortunately, there is no "Error Handling" available for me. Is there a way to enable?

    0
  • Avatar
    Jose Zamarripa

    Hello gentlemen:

                I have the same issue but I'm trying to run the Integration builder on Bartender 2022, I have the next error, but my templates folder isn't that folder my templates folder is different location, how I can change that path ??

               The correct path is in the 2nd picture.

    0
  • Avatar
    Peter Thane

    If you haven't already done so I would suggest updating to R5 and see if that fixes the path issue. There are some references to path bug fixes in the release notes

    0

Iniciar sesión para dejar un comentario.