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

[utaylor (Utah Taylor)]

That’s cool Haso.

[kylepbsps (Kyle P)]

[scott (Scott Gray)]

Thanks for posting this solution. This happened to one of my app servers on weekly server maintenance during Memorial Day weekend. Like everyone said, it does not make sense. The one app server with the problem runs the task agent. Before this fix, I could get the TEST environment up and running by stop,start, app pool, and stop,start task agent. The LIVE would not allow the Admin Console to connect. The task agent never started. Recycle IIS did not help.
This fix has LIVE running now. 2023.2.11 on prem.

[ctsanis (Christos Tsanis)]

So has anyone find a solution to this? We are facing exactly the same issue on a new 2024.1 installation on windows server 2022.

[hkeric.wci (Haso Keric)]

Try - Launch Epicor and login even if the Admin Console says 500, it may require Conversion Workbench to be ran and then come back to the Admin Console. I had it on 2024.1 (False Error). After Conversion Workbench the Admin Console worked fine. Not sure why that is perhaps due to the ICECommon Database.

[ FAQ ] Epicor ICECommon Database

What does the ICECommon database store? Why was it introduced? The ICECommon Database stores information and system data that Kinetic uses as read-only throughout its applications. This database improves installation and upgrade performance, making more storage available across the platform. Kinetic creates one ICECommon database for each SQL Server instance and major version. Each Kinetic database automatically connects to the ICECommon database matching its version number. Can I remove or ren…

[josephp (Joseph Pisano)]

On the server itself, we redeployed our app server in the administrative console.

This worked for us.

[Olga (Olga Klimova)]

This is common error IIS provides, so “THIS” can be anything, you need to look into additional error information to solve your problem.

[ctsanis (Christos Tsanis)]

Thank you everyone for the replies. By “this” i meant we are getting the same error as @chaddb

@chaddb

System.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.

even though we created an empty and train database with no errors and every connection is testing OK on EAC. We can even regenerate those Databases with no errors. But the App server is simply not connecting. The client is also producing the same error when we tried to connect so it does not seem like a fault EAC error (it works that way sometimes).

[Olga (Olga Klimova)]

Client is connecting to appserver, not to database directly, so it is the same error in AppServer.

I assume EAC and App Server are on the same machine? Check if connection string is correct in Host.config. If you use intergrated security, maybe change account for application pool so it has access to SQL.

[Hally (Simon Hall)]

Have you restarted your whole server? We see these issues where windows updates have applied updates or the .netcore hosting bundle etc has been upgraded (which happens often due to ongoing security concerns by IT)

[ctsanis (Christos Tsanis)]

So turns out that the IT company that provided the servers for installation is using a dynamic TCP port for SQL connection (51910). Is it possible that this might be the reason for the failed connection attempts or is it irrelevant?

[Olga (Olga Klimova)]

It surely can. Because it is one of the reasons of that error, if you google it.