I was hoping that maybe you can help me out here please. I already looked on the big internet world but is pretty complex for a simple administrator as I am.
Anyway, I get an error (see error.jpg) and is says HTTP Error 502.5 - ANCM Out-Of-Process Startup Failure at the very moment when I access the website on the local server which means: http://localhost:3800/
I am using the most recent version on Windows Server 2019 Standard, build 1908 with SQL database 2019.The current version of Net.Net is 3.1.201 and I have the follow errors in logs:
APPLICATION ‘/LM/W3SVC/2/ROOT’ WITH PHYSICAL ROOT 'C:\INETPUB\WWWROOT\CVJM' FAILED TO START PROCESS WITH COMMANDLINE ‘%LAUNCHER_PATH% %LAUNCHER_ARGS%’ WITH MULTIPLE RETRIES. FAILED TO BIND TO PORT ‘47709’. FIRST 30KB CHARACTERS OF CAPTURED STDOUT AND STDERR LOGS FROM MULTIPLE RETRIES
APPLICATION ‘/LM/W3SVC/2/ROOT’ WITH PHYSICAL ROOT 'C:\INETPUB\WWWROOT\CVJM' FAILED TO START PROCESS WITH COMMANDLINE ‘%LAUNCHER_PATH% %LAUNCHER_ARGS%’ AT STAGE ‘CREATEPROCESSW’, ERRORCODE = ‘0X80070002’, ASSIGNED PORT 47709, RETRYCOUNTER ‘0’.
Personally I think my current web.config file is some how not good configured yet, it contains:
<?xml version="1.0" encoding="utf-8"?>
I think the variables “%LAUNCHER_PATH%” and %LAUNCHER_ARGS%" need to be changed, but i do not know into what.
I think the variables “%LAUNCHER_PATH%” and %LAUNCHER_ARGS%" need to be changed, but i do not know into what.
%LAUNCHER_PATH% is where your dotnet.exe resides (usually “C:\Program Files\dotnet\dotnet.exe”). %LAUNCHER_ARGS% is your compiled dll (usually ".<project>.dll).
You have set up the application to an application pool with “No Managed Code” in IIS. You may also need to “Enable 32 bit application” depending on your published content (32 or 64 bit).
You have point the application to the “publish” folder of the generated application.
Unlike ASP or PHP, You need to PUBLISH your ASP.NET application for use in IIS, the publish folder (which is NOT the same as the project folder you specified in the Generate settings tab) depends on your publish settings (see Tools → Advanced Settings in the help file), if you do not set any settings, the publish folder is probably: (May not be the same on your PC, but you should easily find it under the bin folder)
\bin\Win32\Debug\netcoreapp3.1\publish
As explained in help file:
under which you should find many files, including a subfolder named wwwroot, you must deploy all subfolder and files under this publish folder to the target folder of your IIS server and set the application at the target (NOT wwwroot) folder containing the web.config.
Secondly, you can try to troubleshoot as follows:
Click Tools → Advanced Settings, enable “Debug”, re-generate the ewcfg*.cs and publish the project again. Run the site with IIS, see the errors shown in the browser, OR
Click Tools → Advanced Settings, enable “Enable ASP.NET Core stdout log”, re-generate the web.config and publish the project again. Create a folder named “logs” at the root folder of your IIS site. Run the site with IIS, see the errors in the stdout_*.log files in the folder.