We recently upgrade to 2025.2.4 and we’ve had a few users mention an error that they are receiving sporadically form edge agent stating “error received from edge agent: unable to validate report”. I dug through the edge logs and found a bunch of references to this report across different machines for multiple users. Each time it happens the edge logs say that is was “Unable to get report bytes for reportID< different reportID each time>” after doing some digging in the db for some of these report IDs it looks like some of our bartender labels are being sent through edge agent for some reason. They’re setup with a report style and an output location on our bartender server. The weird part is that they are successfully running and getting sent to that server without issue. I suspect the edge agent is caching these reports and repeatedly trying to send them throughout the day, but since that report has already been processed there is no data cached on the server for it to process. Has anyone seen this before or know how to prevent it from sending to the edge agent? I dug through our data directives for our autoprint labels and there’s no custom code, it’s just sending the files to the bartender server via the autoprint widget and using the default printer as the printer. Everything I’m seeing looks like nothing should be getting passed to the edge agent for this at all.
This is the error that I’m seeing in the edge agent logs
fail: 2/3/2026 4:08:38 PM -05:00 Edge.Informants.ClientPrinting.ClientPrintingInformant [0] Unable to get report bytes for reportId 3b939d3a-3340-4ceb-ad3d-bdc6b5d46027
System.InvalidOperationException: Unable to get report bytes.
at Edge.Informants.ClientPrinting.CallValidation.ErpCallValidator.GetReportBytesAsync(BaseSubmitPrintJobMessage message, ValidationResult validationResult) in C:\agent_work\2\s\src\informants\Edge.Informants.ClientPrinting\CallValidation\ErpCallValidator.cs:line 160
at Edge.Informants.ClientPrinting.CallValidation.ErpCallValidator.ValidateReportAsync(BaseSubmitPrintJobMessage message) in C:\agent_work\2\s\src\informants\Edge.Informants.ClientPrinting\CallValidation\ErpCallValidator.cs:line 87
info: 2/3/2026 4:08:38 PM -05:00 System.Net.Http.HttpClient.Default.LogicalHandler [RequestPipel Start processing HTTP request GET https://SERVERURL/kineticlive/api/v2/odata/CX/Ice.BO.ReportMonitorSvc/GetBySysRowID?id=04d33bbc-ab0e-4d33-b98a-360cf4a51509
info: 2/3/2026 4:08:38 PM -05:00 System.Net.Http.HttpClient.Default.ClientHandler [RequestStart] Sending HTTP request GET https://SERVERURL/kineticlive/api/v2/odata/CX/Ice.BO.ReportMonitorSvc/GetBySysRowID?id=04d33bbc-ab0e-4d33-b98a-360cf4a51509
info: 2/3/2026 4:08:38 PM -05:00 System.Net.Http.HttpClient.Default.ClientHandler [RequestEnd] Received HTTP response headers after 13.1511ms - 200
info: 2/3/2026 4:08:38 PM -05:00 System.Net.Http.HttpClient.Default.LogicalHandler [RequestPipel End processing HTTP request after 13.3685ms - 200
info: 2/3/2026 4:08:38 PM -05:00 System.Net.Http.HttpClient.Default.LogicalHandler [RequestPipel Start processing HTTP request POST https://SERVERURL/kineticlive/api/v2/odata/CX/Ice.BO.ReportMonitorSvc/GetReportBytes
info: 2/3/2026 4:08:38 PM -05:00 System.Net.Http.HttpClient.Default.ClientHandler [RequestStart] Sending HTTP request POST https://SERVERURL/kineticlive/api/v2/odata/CX/Ice.BO.ReportMonitorSvc/GetReportBytes
info: 2/3/2026 4:08:38 PM -05:00 System.Net.Http.HttpClient.Default.ClientHandler [RequestEnd] Received HTTP response headers after 11.6729ms - 200
info: 2/3/2026 4:08:38 PM -05:00 System.Net.Http.HttpClient.Default.LogicalHandler [RequestPipel End processing HTTP request after 11.843ms - 200
it is a bug, Bartender files should not be sent to Edge Agent at all. It is fixed in 2026.1
Ah fun thank you, do you know if there’s any workaround for this in the mean time? We’re getting complaints about the error, luckily it doesn’t actually cause any issues but still annoying as it’s persisting even when not running the report or printing anything since it seems to be caching in the edge agent and repeatedly trying to print even when they’re doing completely unrelated tasks
No workaround, just ignore it
We experience this too. Painful.
Kinetic Bartender Issue - Edge Agent - Kinetic ERP - Epicor User Help Forum
I’ve reached out to EpicCare support countless times, our CAM, professional services. Never heard a peep about an associated PRB or a resolution date. Glad to hear something Olga
Do you have the associated PRB? I would like to forward to our CAM.
I have internal story number only, It is usually enough if you share this: ERPS-302516
Thank you Olga