Installation of Kinetic 2022.2 on Windows Server 2022

Kinetic ERP
1

Attempting to install the DEMO database of 2022.2 on a Windows Server 2022 server. Vanilla install, self-sign cert for now.

Upon first connection to the app server, I get:

Ice.Api.Exceptions.UnknownRestException: HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.

   at Ice.Cloud.ProxyBase`1.CallWithCommunicationFailureRetry(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, RestRpcValueSerializer serializer)
   at Ice.Cloud.ProxyBase`1.CallWithMultistepBpmHandling(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
   at Ice.Cloud.ProxyBase`1.Call(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
   at Ice.Proxy.BO.UserFileImpl.IsPasswordExpired(String userID, Int32& graceCount)
   at Epicor.Mfg.Administration.ServerManagement.ApplicationServerManager.Forms.NewSessionForm.BackgroundWorker_DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

Default bindings:

image

Rebooted the server. Same.
Error message not found in EpicCare

Anyone successfully get Kinetic running on WS 2022?

I’ve seen this error here for previous versions but no solutions. :thinking:

Thanks!!

2 Likes
2

I’ve found, more often than not, that a full reboot cures the IIS related stuff. A basic IIS restart or IISRESET isn’t enough sometimes.

And I would double check that the Windows Defender/Firewall/whatever it’s called now is turned off or has the appropriate rules turned on or created.

3

Yes. I saw that was one of the resolutions and did that. Same error.

Turned off :fire: wall. Same error, This is a demo box so SQL and the AppServer are all together on this one but still worth a shot.

In the EAC, there is this extra text:
image

Where would one get an updated EAC? Don’t see any in EpicWeb… :thinking:

image

4

@Mark_Wonsil It is under the deployment folder.
image

5

Have you also tried to Deploy the Appserver again? I got this response from support often as well.

Inside the Appserver Config window, the Actions menu has a Rebuild Site option - this may work too.

In the EAC, highlight & connect to the appserver - The actions menu on the right side has an option for Reinstalling the App Server manager extension

Reinstall Application Server Manager Extensions

You use the Reinstall Application Server Manager Extensions features to download and reinstall an extension required for an application server currently in use.

You can add application servers from different versions to each Epicor server. To accommodate these different application server versions, the Epicor Administration Console must install application server extensions that allow these versions to run. If different versions are required, these application server extensions are downloaded during the Epicor Administration Console installation. While this program installs, it adds the application server extension that matches the version each application server uses.

However you may later register an application server that uses a version you did not install originally with the Epicor Administration Console. This situation can occur when you update the Kinetic application and you need to connect to multiple application servers. Because these application servers were installed using an older extension, not all functions will work as expected in the Epicor Administration Console.

When this situation occurs, run the Reinstall Application Server Manager Extensions feature. the Epicor Administration Console will detect which application server extension is needed for the current application server and install it if possible. You then can run the application server as expected.

6

Thanks Greg! Updated the EAC.

About a dozen times! :rofl:

And there’s the rub. This is a fresh install (well, installs…from scratch…including OS a couple of times) and have not been able to connect to the AppServer once. :person_shrugging:

I’ve done this many, many times before and just wondering if I should try WS 2019… :thinking:

Things like this make me miss the cloud days… :rofl:

7

I just did 22.2 on 2019 last week and it went smoothly except for EDD not wanting to stay active.

Have you tried changing the App server user and password and then changing them back?

I will see if I can get 2022 server install media.

8

Mark, I’m on Kinetic 2022.2 on a Windows 2022 box…

Initially I did have a bunch of trouble while trying to deploy the Demo database. It ended up being the Admin Console’s xml config files in ProgramData directory… they got all messed up somehow. I did some manual editing of them and it cleared everything up for me.

9

Do you recall what you might have changed? It’s pretty bare in there.

From C:\ProgramData\Epicor\AdministrationConsole\Epicor.Mfg.Administration.ServerManagement.Configuration.xml

<?xml version="1.0" encoding="utf-8"?>
<ServerManagementConfiguration xmlns="http://tempuri.org/ServerManagementConfiguration.xsd" lastSavedOn="05/01/2023 20:39:55">
  <EpicorServers Id="bd577ee3-ea17-4619-bb8b-ba38ce43e587">
    <EpicorServer Id="534b25e1-a3bd-4dba-ad14-025d2fdc686b" EpicorServerName="K2022">
      <ApplicationServers>
        <ApplicationServer Id="8e2955fd-c586-4336-b9f0-065baaebf91f" AppServerName="Kinetic2022_2" Endpoint="https://K2022/Kinetic2022_2" OperationTimeout="300" X509CertificateValidationEnabled="False" DnsEndpointIdentity="K2022" AuthenticationMode="Basic" UserName="epicor" EncryptedPassword="xzr/FPZJTDo1zGPmTwKP8w==" UseSSL="False" LastConnected="" ServerVersionHint="4.2.200" UseEWAClient="False" UseSmartClient="False" SmartClientExePath="" EWABaseUrl="" DeploymentServerUri="C:\epicor\ERP11\ERP11.2.200.0" xmlns="http://tempuri.org/ServerManagementConfiguration.xsd" />
      </ApplicationServers>
    </EpicorServer>
  </EpicorServers>
</ServerManagementConfiguration>
10

It was a while ago but I believe one of the things I changed was the AppServerName. I had named it KineticDemo during deployment but I think it was showing as Kinetic2022_2 in the xml

11

Check web.config and host.config, maybe they are not well-formed xml.

12

I tried an install on Server 2019. Same thing. :thinking: So, this has to be me, right?

@ERPSysAdmin gave me some links to try and that led me down the rabbit hole to a post about the Hosting Bundle for .NET 6. I did have it installed in both Server 2019 and Server 2022.

So, I did a repair for the Hosting Bundle in WS 2019.

Boom! Started right up.

Did a repair for the Hosting Bundle in WS 2022. Boom!

Leaving this out there in case others might need it. Thanks everyone!

12 Likes
13

For me I had to do both the Hosting Bundle and the SDK as well. This is a development server, and I think installing Visual Studio kinda messed things up. After repairing both items, it starts right up.

1 Like
14

I have not installed Visual Studio. :person_shrugging: Very odd.

15

I think when I was setting up our new production server I came across this. I think if you switch the order of installation where Hosting is done second this doesn’t happen.

1 Like
16

I’ve always done the Hosting Bundle second.

1 Like
17

Thank you. I didn’t run into this when setting up our dev, and just about to go to production in a new setup. Of course, ran into this.

Lifesavers!!! I wouldn’t have tried that.

18

Great solution. Worked perfectly.

1 Like
19

I just had the same issue with Kinetic 2024.1 and repairing the hosting bundle fixed it for me too. Thanks for the help!!

2 Likes
20

Thank you!