In this article tutorial, we will continue to discuss about other error that you can find when deploy your Asp.net core application. In previous tutorial, we have discussed about how to fix ASP.NET Settings has been Detected that does not Apply in Integrated Managed Pipeline Mode.
This error happened for example you deploy minor HTML update to a .NET core website whe you hosting your site. When you load your site, it will throw this error message below:
Failed to start application '/LM/W3SVC/####/ROOT', ErrorCode '0x8007023e’.
Here is some information that you can find on Event Viewer:
Application 'D:\home\site\wwwroot\' failed to start. Exception message:
Executable was not found at 'D:\home\site\wwwroot\%LAUNCHER_PATH%.exe'
Process Id: 10848.
File Version: 13.1.19331.0. Description: IIS ASP.NET Core Module V2.You can reproduce this error if you login to the server, but if you are using shared hosting, then you need to ask your hosting provider to check this error for you.
How to Fix it
It would seem that no one else on the planet experienced this issue when Googling the error message and error code. After a lot of fumbling around, the fix ended up being relatively straight-forward. The detail provided by the Event Log pointed me in the right direction and the clue was in the %LAUNCHER_PATH% placeholder. The %LAUNCHER_PATH% placeholder is set in the web.config and this is normally replaced when the application is run in Visual Studio or IIS.
Both %LAUNCHER_PATH% and %LAUNCHER_ARGS% variables need to be explicitly set. The following line in the web.config needs to be changed from:
<aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false" startupTimeLimit="3600" requestTimeout="23:00:00" hostingModel="InProcess">
To:
<aspNetCore processPath=".\Site.Web.exe" arguments="" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false" startupTimeLimit="3600" requestTimeout="23:00:00" hostingModel="InProcess">
The executable created by the project is now where the processPath is pointing. “Site.Web.exe” in this instance. Additionally, the arguments attribute is empty because in my build no arguments are being parsed. The error ought to be fixed when you push up your following release.
It is recommended for you to set your deployment mode from “Framework-Dependent” to “Self-Contained”. This will ensure the application will always run in its current framework version.
Conclusion
We hope article above helps you to fix the issue if you encounter same error message.
If you are looking for fast and secure ASP.NET hosting, you can visit our site at https://www.asphostportal.com. Our fully featured hosting already includes
- Easy setup
- 24/7/365 technical support
- Top level speed and security
- Super cache server performance to increase your website speed
- Top 9 data centers across the world that you can choose.
Andriy Kravets is writer and experience .NET developer and like .NET for regular development. He likes to build cross-platform libraries/software with .NET.
