The application process failed to start The application process started but then stopped The application process started but failed to listen on the configured port
Troubleshooting steps:
Check the system event log for error messages Enable logging the application process' stdout messages Attach a debugger to the application process and inspect ___________________________________________________________________
I had this same error come up when trying to run nopCommerce 4.0 through IIS.
After reading an article on https://stackify.com/how-to-deploy-asp-net-core-to-iis/, I reviewed my file layout versus a working nopCommerce 4.0 site, and realized I still needed to publish Nop.Web. Based on how I used to setup sites in 3.9, I published the site directly into the Nob.Web folder, and I was able to load up the site.
I came across the exact same error trying to compile and run the 4.0 source code version for the first time.
For me this error was caused because I had changed the "Platform target" of the nop.web build from the 4.0 default setting of "x86" to what I was used to using which was "Any Cpu". Changing this dropdown back to either x86 or x64 stopped this error from occurring for me and allowed me to run 4.0 without issue.
While the original post is about running 4.0 in iis, I thought I'd add this to the discussion for anyone searching for the error code as in both cases they are the same.
i have publish my app ... it was working fine .... Same problem came across to me even my local system as well published site facing the same problem ...
i am working on my development environment but still not find solution...
i have publish my app ... it was working fine .... Same problem came across to me even my local system as well published site facing the same problem ...
i am working on my development environment but still not find solution...
.
did you check log under Log folder of your root directory?
if not than,
set stdoutLogEnabled="true" under web config and see the error.
Common causes of this issue: The application process failed to start The application process started but then stopped The application process started but failed to listen on the configured port
Troubleshooting steps: Check the system event log for error messages Enable logging the application process' stdout messages Attach a debugger to the application process and inspect
it showing in my local development envoirment and also my live site is down due to same error ... even last 3 days back it was running fine ...
Common causes of this issue: The application process failed to start The application process started but then stopped The application process started but failed to listen on the configured port
Troubleshooting steps: Check the system event log for error messages Enable logging the application process' stdout messages Attach a debugger to the application process and inspect
it showing in my local development envoirment and also my live site is down due to same error ... even last 3 days back it was running fine ...
Are you running on local IIS ?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.