HTTP Error 500.30 - ASP.NET Core app failed to start

Kinetic ERP
1

Hi,

Getting below error while reboot the Kinetic Application Server.

An error occurred while attempting to register the service with the application server: Ice.Api.Exceptions.UnknownRestException:  HTTP Error 500.30 - ASP.NET Core app failed to start 
   at Epicor.ServiceModel.Channels.ImplBase.CallWithCommunicationFailureRetry(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, RestRpcValueSerializer serializer) in C:\_releases\ICE\ICE4.3.100.0\Source\Shared\Framework\Epicor.ServiceModel\Channels\ImplBase.cs:line 1028
   at Epicor.ServiceModel.Channels.ImplBase.CallWithMultistepBpmHandling(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy) in C:\_releases\ICE\ICE4.3.100.0\Source\Shared\Framework\Epicor.ServiceModel\Channels\ImplBase.cs:line 962
   at Epicor.ServiceModel.Channels.ImplBase.Call(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy) in C:\_releases\ICE\ICE4.3.100.0\Source\Shared\Framework\Epicor.ServiceModel\Channels\ImplBase.cs:line 941
   at Ice.Proxy.Lib.SessionModImpl.Login() in C:\_releases\ICE\ICE4.3.100.8\Source\Shared\Contracts\Lib\SessionMod\SessionModProxy.cs:line 239
   at Ice.TaskAgent.Support.ServiceCall.ImplCaller`1.Call[TResult](Func`2 doWork, ExceptionBehavior communicationExceptionBehavior, ExceptionBehavior timeoutExceptionBehavior) in C:\_releases\ICE\ICE4.3.100.8\Source\TaskAgent\TaskAgentSupport\ServiceCall\ImplCaller.cs:line 125
   at Ice.TaskAgent.Support.ServiceCall.ServiceCaller.<>c__DisplayClass52_0.<SessionMod_Login>b__0() in C:\_releases\ICE\ICE4.3.100.8\Source\TaskAgent\TaskAgentSupport\ServiceCall\ServiceCaller.cs:line 393
   at Ice.TaskAgent.Support.ServiceCall.ServiceCaller.CallWithInvalidSessionHandling[TValue](Func`1 makeCall) in C:\_releases\ICE\ICE4.3.100.8\Source\TaskAgent\TaskAgentSupport\ServiceCall\ServiceCaller.cs:line 715
   at Ice.TaskAgent.Support.ServiceCall.SessionManager.CreateInitialServiceCallArguments(ServiceCallArguments callArguments) in C:\_releases\ICE\ICE4.3.100.8\Source\TaskAgent\TaskAgentSupport\ServiceCall\SessionManager.cs:line 154
   at System.Lazy`1.CreateValue()
   at System.Lazy`1.LazyInitValue()
   at Ice.TaskAgent.Support.ServiceCall.SessionManager.CreateServiceCaller(ServiceCallArguments callArgumentsWithoutSessionId) in C:\_releases\ICE\ICE4.3.100.8\Source\TaskAgent\TaskAgentSupport\ServiceCall\SessionManager.cs:line 64
   at Ice.TaskAgent.Support.TaskAgentHelper.VerifyConnectionDetails(SessionManager sessionManager, ServiceCallArguments serviceCallArguments, String& errorMessage) in C:\_releases\ICE\ICE4.3.100.8\Source\TaskAgent\TaskAgentSupport\TaskAgentHelper.cs:line 689.

But it is resolved after recycle the application pool.

Can you anyone facing this issue. Please share the permanent solution.

Kinetic Version : - ERP = 11.3.100.11

Regards,
Sanjeev

2

You might try the solution in this thread. Basically, running a repair on the .NET Core Hosting Bundle.

Installation of Kinetic 2022.2 on Windows Server 2022 - Kinetic ERP - Epicor User Help Forum (epiusers.help)

1 Like
3

Can you please explain what you are saying

4

It’s explained in the posted thread. Let me know if you still have questions after reading it.

5

I have repaired the bundle and even installed latest version but same issue. I am using Windows Server 2022 Standard Edition and SQL Server 2022

1 Like
6

What happens if you try to go to https://? (The root and not the Kinetic app)

7

Check your event viewer for additional errors that may have cause the App Pool to not start up.

I have seen this frequently when the SQL server takes longer than the app server to come online.

The App pool will time out when starting up if it doesn’t get a SQL connection in time.

1 Like
8

Hi All,

I got answer from Epicor Support Team and applied the solution and it is working

Hi Sanjeev,

Is SQL Server installed on the same server/VM as Kinetic? If so, this will happen if the AppPool tries to start before SQL has fully started up.

You may be able to get around this by delaying the start of IIS, e.g. via Services or use an elevated Command Prompt using these commands:

sc config IISADMIN start= delayed-auto
sc config WAS start= delayed-auto
sc config W3SVC start= delayed-auto

If SQL Server is NOT installed on the same server as Kinetic, make sure to always delay the restart of the Kinetic server by a couple of minutes if you are also rebooting the the SQL Server. I would also recommend you check all Epicor related Windows Services and set them all to Delayed Start. This includes the Task Agent, Enterprise Search service etc.:

If you continue to have issues you will need to look into other solutions. For example, use the Windows Task Scheduler to IISRESET after a delay everytime the server is rebooted or use a scheduled batch file to control the startup of AppPools instead of having them auto-start, e.g. via:

%SYSTEMROOT%\System32\inetsrv\appcmd start apppool /apppool.name:“KinetcLive”

Regards,
Sanjeev

2 Likes