I am still dipping my toe into the web version of Kinetic, trying to test it out before I move any users into it full time. I have a question about the Epicor Edge Agent.
I had it installed on 2024.1.x. We upgraded to 2024.2 over the weekend on cadence in the cloud. Now, Edge Agent appears to require user interaction and download/installation to update, different from how the smart client works.
Is this my future if I want people using the web version of Epicor?
How frequently does the Edge Agent client require manual updating per year?
If you’re not trying to direct-print when you get this error, the error probably isn’t actually edge agent. When a menu item isn’t configured correctly to open on the web client, the web agent attempts to punt that app to desktop via edge agent. If that fails, no context was preserved, so the web client can only throw a “something happened while trying to edge agent” error message.
The desktop’s end is nigh, especially for us SaaS users. It’s a good time to follow those error messages back to menu maintenance and get things configured to play along with the web client before the desktop fallback option goes away.
Another fun fact… as I was tasked with testing out Edge Agent as well… so I started with me as the guinea pig, and then tested with our accounting department. All went fine until I got to our AP Clerk… and kept getting this popping up every time she tried to print something.
Unbeknownst to me, my predecessor had tried installing it on her computer… and thus she had an old version installed. I ended up completely uninstalling Edge Agent from her computer, deleting out ALL edge agent files of any kind, and then installing Edge Agent on her computer properly… and it worked without any issue.
Epicor Support isn’t going to be able to tell you that. Their base assumption is that you did something wrong installing it. Newer versions of Edge Agent don’t “overwrite” the older versions when installed. So just be aware if one specific user’s computer is resulting in that error, when everyone else is working just fine… they may have ended up somehow getting a different version installed from the one deployed on your server.