4.3 Release - HTTP Error 503.0 - Server has been shutdown

Hello,

I am getting this error anytime the site restarts. This happens with both the source version as well as the no source on a clean install. Here is the additional info:

Module     AspNetCoreModuleV2
Notification     ExecuteRequestHandler
Handler     aspNetCore
Error Code     0x8007045b
Requested URL     http://localhost:80/Admin
Physical Path     Z:\FleetCooling\Admin
Logon Method     Anonymous
Logon User     Anonymous

I can simply refresh the site and it comes back up, but this seems like a pretty big problem. Is anyone else having this issue? It looks the same as https://github.com/nopSolutions/nopCommerce/issues/4405

Thanks,
Kevin

Just a curious question,
are there any warnings here:  yoursite.com/Admin/Common/Warnings

Also, what version of .net core runtime are you using ?
Nop4.3 requires .net core 3.1
Internet Information Service (IIS) 7.0 or above
MS SQL Server 2012 or above OR MySql Server 5.7 or above

up-vote if you found this helpful.

varunnaresh wrote:
The only warning is to disable ACL if not in use, but we do use that.

varunnaresh wrote:
I installed the runtime and SDK of .net core 3.1 and using the latest bits of IIS and SQL Server 2014.

Thanks,
Kevin

the only other thing that comes to my mind is, are there any server updates pending or server restart pending ? Sometimes weird issues get sorted this way. Nop 4.3 restarts are working correctly for me.

You could also try delete website from IIS and also delete from application pool, and then create fresh website once more, incase there was a wrong configuration somewhere.

https://stackoverflow.com/questions/53846550/handler-aspnetcore-has-a-bad-module-aspnetcoremodulev2-in-its-module-list/54539874

https://stackoverflow.com/questions/53729956/aspnetcore-2-2-0-aspnetcoremodulev2-error

upvote if you found this helpful.

I think this is related to the "startupTimeLimit" in the aspNetCore section of web.config. According to the MS docs:

Optional integer attribute.

Duration in seconds that the module waits for the executable to start a process listening on the port. If this time limit is exceeded, the module kills the process. The module attempts to relaunch the process when it receives a new request and continues to attempt to restart the process on subsequent incoming requests unless the app fails to start rapidFailsPerMinute number of times in the last rolling minute.

A value of 0 (zero) is not considered an infinite timeout.

This is a very short time and restarting the website takes longer than the maximum value (and the current value of 3600). The setting defaults to 120 if it's removed and just shuts down even quicker.

Is there another way around this?

Kevin

kevlingo wrote:
Hello Kevin.
Did you find the solution?
Best.