Kinetic Bartender Issue - Edge Agent

So did you get yours working again or not? I couldn’t gather that from your response.

So mine works with the popup error message. Sorry i forgot to put that in.

1 Like

Yeah, our Data Directive have always worked and printed our labels to the correct physical printer. It’s just why the pop ups and errors lol.

Will update this with what EpicCare says when I do get a response.

We are seeing this issue also. Did support provide an update or fix?

no support closed ticket as could not reproduce. I will try again with different support.

2 Likes

My ticket is still open with no response since 10/15. I updated this morning asking for a status update.

1 Like

I would recommend sharing case numbers with each other and then posting the cases that are shared to your case so that support can see it is being reproduced, though we don’t know why or how to do it.

Good idea Utah. Our case is CS0005135567. It has not been associated with any known PRB as of yet.

If everyone else shares their case you can then take theirs and put in your case.

@Devin.Draeger and @mroelandts would you be comfortable sharing your case numbers?

Here is my case CS0005129993

Updating this. I have had an EpicCare representative help look into this again, hoping that it will eventually get turned into a PRB and resolved. Some notes:

I found errors only occur on devices that have the Edge Agent installed (up to the latest version, 1.2.644). If you do not have the Edge Agent installed, you will only get the ‘Report sent to edge agent’ message, but not the errors that you must dismiss. Knowing this, we have temporarily removed the Edge Agent from our Terminal Servers.

While our data directives had report styles that were copies of GenJob and GenShip, I was able to recreate using base fields, report styles, data definitions, etc. and sent this to EpicCare:

On a Windows device with the Edge Agent installed and configured correctly to the appropriate environment:

Add a Network Printer in Printer Maintenance

Create a Standard Data Directive using the ShipHead Table

Add a condition for “The ttShipHead.ShipStatus field has been changed from any to another”

Add an Auto-Print widget and configure for the base GenShip Report

Configure the Selected Options for Queued, Auto-Print, to the added Network Printer:

Update the Selected Parameters to look for ttShipHead.PackNum table and field value and 1 for PackLine:

Save and Enable the Data Directive

Go to Customer Shipment Entry

Create a Packing Slip, import an Order and Order Line, then Close the Pack. The act of Closing/Opening the pack should fire off the BPM, and it should have the Edge Agent pop ups for ‘Report Sent to Edge Agent’ and an Error slide out saying 'Error received from Edge Agent: Unable to validate report

Let’s hope it goes somewhere.

1 Like

Billy, I have had issues making those auto-print data directives using Kinetic screen, if you make them in classic does it work?

1 Like

I do remember a thread with some of your issues Utah, and yes we have similar issues.

We recently upgraded our Print Server and ended up giving it the same domain name as our old one, due to the fact that we couldn’t update the data directives in Kinetic. I tested in Classic and the updates stuck, but we went the easier route of just shutting down the old print server and renaming the new one the same name, keeping all of our share names intact and not requiring updates to the data directive.

Did you ever get a PRB on the ticket you submitted? I need to also submit a ticket and will reference yours if so.

2 Likes

I did a teams session to show the steps to replicate, haven’t checked the ticket yet to see if they could re-produce with newer version (2025.2) as opposed to 2024.2 and then assign a PRB.

1 Like

@utaylor We had the same issue with our EDI files. Grabbing for straws I changed the BPM’s run schedule of Queued to immediate. It worked, but since then I had to pause on troubleshooting for other issues, so I haven’t been able to do any additional testing since… I just know it worked when I tried it that one time for a few transactions. Good luck and hope that works for you.

1 Like