Over the weekend we updated the Windows Server OS that is hosting our Epicor 10.2.700.34 from Windows Server 2016 to Windows Server 2022. It completed without any issues. We tested many elements of Epicor and everything worked as expected.
Well, we did all of our testing in Classic view and today we discovered that anyone using Active view can’t get in. Their Classic view is fine, but if they try Active view they get:
Unable to log in to the Kinetic Home Page. Error code:-181
and then
The Page Failed to Load
Error code:-181
To customize this message, please handle the WebView’s LoadFailed event and then Set e. ErrorMessage in your event handler based on e.ErrorCode, or call e.UseDefaultMessage if you just wish to display the error message without this help message.
As a quick troubleshooting step, I tried stopping the AppServer and then re-deployed it, however there was no change.
What is odd is that on this same server we have a Test AppServer too. Same version. It uses a copy of the live database but otherwise the same. That environment loads Active view without any issues.
I did some searching on this but no search results anywhere. Any ideas? I don’t know where to even start.
Yes, all good. Nothing about the OS upgrade would have modified any Epicor client .sysconfig files. I checked and it is all still correct, and both Classic and Active view use the same .sysconfig file.
Ah ok, I didn’t realize that was a thing one could do.
I should add that two weeks prior, I upgraded another company’s Epicor server from Windows Server 2016 to Windows Server 2022, same 10.2.700.34 version, almost identical. In that environment no one uses Active view so we never tested it there. Well this morning I tested it there and both Active view and https://server.tldr/EpicorInstance/Home work perfectly. So we at least know it is possible for this to work.
Back to the company in question, when I go to https://server.tldr/EpicorInstance/Home for both the live and test environments, I get the Epicor login page and I can log in ok to both Test and Live. That seems to be working as expected. However, Active view on Live still fails with same error as initially described while Active View in Test works ok. I don’t get it. Between two companies, in 3/4 environments Active view is ok, but it is not ok for Live at this company. It doesn’t seem to make sense.
So if I go into the App Server config and go to Action → Rebuild Site, it rebuilds successfully but still no Active view, I see the same error when trying to launch Active view. Classic view is still fine.
Next I created a new AppServer with identical settings, and it works just fine. So the Active view issue is specific to this one AppServer. I’d rather not have to reconfigure all clients to use a new AppServer if it is possible to fix it.
So it turns out that the fix is super simple. I have no idea why it is affecting only one AppServer and the other is ok, that part really makes zero sense to me, but this is what fixes it:
Go into IIS and expand the tree until you get to Default Website
