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

7 месяцев назад
New installation on IIS 10
another site on .Net 7.0 in IIS work perfectly
help please
https://irocket.store/

Publish from Visual Studio.
Visual Studio solution start correct, IIS give Error 500.30.
7 месяцев назад
Enable error logging
See https://selectsystems.com.au/checking-for-errors-on-a-new-installation-of-nopcommerce
7 месяцев назад
Yidna wrote:

In Web.config set stdoutLogEnabled = "false" to true, Republish Application, but folder \Logs\stdout is empty..
7 месяцев назад
Then maybe the .NetCore app is not starting - try and check the windows event logs
7 месяцев назад
Yidna wrote:
Then maybe the .NetCore app is not starting - try and check the windows event logs


Windows Logs/Application:

Application '/LM/W3SVC/5/ROOT' with physical root 'C:\inetpub\irocket.store\' failed to load coreclr. Exception message:
CLR worker thread exited prematurely
7 месяцев назад
two weeks i can't start nopcommerc on IIS
it's very sad :)

i write in https://t.me/NopCommerceDevsGroup too
7 месяцев назад
First do a brand new no-source install and test it.  Then you can publish / overwrite files from VS.
https://docs.nopcommerce.com/en/installation-and-upgrading/installing-nopcommerce/installing-on-windows.html
https://docs.nopcommerce.com/en/installation-and-upgrading/installing-nopcommerce/installing-local.html
6 месяцев назад
even though this an older topic, I figured I'd reply with how I got around this same exact issue.

It ended up being user rights at the IIS level for the domain that the site was installed in.   I had to set the IIS_USER to have the following rights to the directory -

Modify (which was missing for me and I think was causing the issue)
Read & execute
List folder contents
Read
Write

Hopefully this helps
5 месяцев назад
tkolakow wrote:
even though this an older topic, I figured I'd reply with how I got around this same exact issue.

It ended up being user rights at the IIS level for the domain that the site was installed in.   I had to set the IIS_USER to have the following rights to the directory -

Modify (which was missing for me and I think was causing the issue)
Read & execute
List folder contents
Read
Write

Hopefully this helps



THANKS!!!