EdgeAgent 2025.1 not compatible with Kinetic 2024.1?

Kinetic ERP
1

I am just wondering if anyone else is having an issue with the EdgeAgent launched with 2025.1 not working with Kinetic 2024.1?

Support is (even after I told them in the initial ticket description that it made no difference since I found the same KB before I made the ticket) pointing me to an article saying I need to open port 6071 (or 6701, it depends on which part of the article you believe, the text or the screenshot). As noted, either of those ports being open still does not work.

My testing system for 2025.1 direct prints just fine (neither of those ports are open on the 2025.1 App Server either so yeah.) but ‘Fails validation’ when direct printing from my 2024.1 systems.

EdgeAgents for 2024.1 & 2024.2 work perfectly with my 2024.1 system (no longer have an active 2024.2 system to test against but 2024.2 worked perfectly with it when I did) but obviously do not work against 2025.1.

Opening 2024.1 Classic screens from the browser does work perfectly with the 2025.1 Agent, it seems the only thing it doesn’t do is direct print, though it sees all my printers.

I also use Client Side printing in case that is a variable anyone has ever seen.

1 Like
2

Typically the Edge Agent has ben version specific and rarely is anything Epicor backward compatible. However Edge Agent is a new-ish feature so I’m not 100% sure.

3

it should be backward compatible. (provided that you use the same 6071 port). What is in the Edge Agent log?

1 Like
4

I know that anything I tested with 2024.2 (I think there was 2 different versions) worked fine for 2024.1. It is of course possible that 2025.1 is not compatible with 2024.* but then I am at a loss as to how I could have both (Live 2024.* and Testing 2025.1) since the 2025.1 installer works like all previous versions in that it over writes an existing EdgeAgent.

Support also did not flag that as a problem, which if it was not supported I would expect.

1 Like
5

This is the EdgeAgent log I attached to my ticket. I understand why they want to point me to KB0120347, it exactly matches the error I get about failing to validate but the steps in it do not make any difference and like I say, I don’t even have those ports open on my 2025.1 App Server that works fine with this.

6

It shows Error not found, so it does not see report you want to print. This is strange. Do you see the report with 6a1496e0-5b7f-4a85-80ff-95a51980f52e SysRowID in the Ice.SysRptLst table?

7

Unfortunately that particular log was from a week or two ago I think, when I opened the case and it has been purged. I’ll do a reinstall of the agent again and run another test and see if that failure shows up in the DB.

Edit to Add:

Just an FYI but this is the Edge Agent version I am using that is not working pre-2025.1

RELEASE NOTES
Version - 1.2.608.0
Date Released: 4/11/2025 19:40

FIXED - App Server Settings - overflow menu should be displayed in expected style
FIXED - Autoupdate - Admin rights
FIXED - Edge Agent Configuration - Validate App Server
FIXED - Rewiew App Server Settings - Paste from Excel

8

Check that you can connect to your server using URL from the log, 404 error is not expected here.

9

Ok, so reinstalling it and doing a direct print it gets submitted, sent to the EdgeAgent and then returned with the error: “Error received from Edge Agent: Unable to validate call”

Running a BAQ against the SysRptList table and looking for SysRowID: d57c93e6-dda3-40c8-8603-343187a73276 which I am fairly certain is what it is looking for does return a result attached here:

EdgeAgentReportExists.xlsx (10.0 KB)

10

If you are reffering to this URL:

***/api/v2/odata//Ice.BO.ReportMonitorSvc/GetBySysRowID?id=d57c93e6-dda3-40c8-8603-343187a73276

Then I just get an error back regarding not passing an API Key:

image
image815×126 7.65 KB

If there is another URL that you are referring to and I am missing can you please point me to it?

11

Try to replace

with api/v1/ this way we will avoid requirement for API key for now.

12

With v1 I get Incorrect Service Name

<ApiExceptionResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<HttpStatus>BadRequest</HttpStatus>
<ReasonPhrase>REST API Exception</ReasonPhrase>
<ErrorMessage>Incorrect service name. Example: Ice.BO.TipSvc</ErrorMessage>
<ErrorType>Ice.Api.Exceptions.ApiException</ErrorType>
<CorrelationId>013e3dd1-c620-4482-a37b-8ff8b8b894ff</CorrelationId>
</ApiExceptionResponse>
13

okay, company is missing from the URL for REST v2. Apparently older Kinetic versions do not provide it.
Please report it, or add to the existing case.

2 Likes
14

Just to clarify, would we have to reinstall the edge agent again once 2025.1 is in live, or will the new pilot edge agent work for the 2025.1 live environment as well? Assuming that it is configured correctly of course.

15

yes, one EA instance will work for all appservers, specified in its settings

2 Likes