I will most likely run into this as well.
Saved my bacon @Mark_Wonsil, instead of going down that rabbit warren. I just did the repair and it worked. It clearly must have something to do with the order of things⦠Did you follow the install guide verbatim. eg. SDK, Hosting, 4.8, SQL, SSRS then Epicor App?
I did. I have found that I have had to do it again and it may be around the same time that Wndows Updates come⦠![]()
This just happened, I had a clean server fully updated, then I did all the installs. It broke the first time I tried to connect to the app server in the EAC.
Legend. This fixed the issue for me as well.
Quick update on this. I was seeing this on my dev box and, I think @olga may have mentioned this in another thread, there can be a timing issue of when IIS is starting and the AppServer starts and the .NET bundle may not be instantiated yet. So, if I delay the launch of Kinetic a bit to make sure IIS is setup, I donāt get this issue. The other thing Iāve done is to restart IIS and often the AppServer will start up afterwards. I think installing the .NET bundle was doing a restart, so maybe that was masking the issue.
I also think there can be timing issues if IIS starts up before SQL server is finished starting up. I have been seeing launch errors on my dev 2025.1 environment after rebooting the box (which has SQL and appserver on it), and I need to bounce the app pool to resolve. Iāve run into this before over the years but itās been a while.