Last post Mar 13, 2017 08:08 PM by pgatto
Mar 05, 2017 10:54 PM|pgatto|LINK
after you publish a site on a Windows Server
2012 and IIS 8.5 and follows
the indications of a previous post when I try to
open the home page http://sitovirtuale:2134
I get the following error:
HTTP Error 502.5 - Process Failure
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
Check the system event log for error messages
Enable logging the application process’ stdout messages
Attach a debugger to the application process and inspect
Mar 06, 2017 01:59 AM|Radomir|LINK
Did you do any of the suggested troubleshooting steps? Check the Application event log first and see if it shows you any errors..
Mar 07, 2017 06:01 PM|pgatto|LINK
Hi Radomir, in the
event viewer I found this error:
Log Name: Application
Source: IIS AspNetCore Module
Date: 07/03/2017 18:45:55
Event ID: 1000
Task Category: None
Application 'MACHINE/WEBROOT/APPHOST/virtualsitename' with physical root 'C:\Web\virtualsitename\' failed to start process with commandline '"dotnet" .\virtualsitename.dll', ErrorCode = '0x80070002 : 0.
<Provider Name="IIS AspNetCore Module" />
<TimeCreated SystemTime="2017-03-07T17:45:55.000000000Z" />
<Data>Application 'MACHINE/WEBROOT/APPHOST/virtualsitename' with physical root 'C:\Web\virtualsitename\' failed to start process with commandline '"dotnet" .\virtualsitename.dll', ErrorCode = '0x80070002 : 0.</Data>
Mar 07, 2017 06:49 PM|Radomir|LINK
That looks like a file not found error. a few things to check -- does the command "dotnet virtualsitename.dll" work from command prompt if you type it in (when you're in that c:\web\virtualsitename folder)?
Did you install .NET Core runtime (and/or SDK) onto this machine? There are a few troubleshooting steps you could do (such as using Process Monitor) but I'd start with simple stuff such as making sure things are correctly installed (and are in PATH environment
variable) and things like that to ensure that everything is correct.. pointing to right folder etc....
Mar 07, 2017 11:16 PM|pgatto|LINK
Hi Radomir, I re-installed
".NET Core Windows Server
Hosting" rebooted the server
but it does not change anything and also do not
recognize the command "dotnet"
when I run "dotnet nomevirtualsitename.dll". Everything seems to be
in its place. What can I check
Mar 07, 2017 11:45 PM|Radomir|LINK
Check that it's installed -- check contents of C:\Program Files\dotnet -- make sure dotnet.exe is there.
Second, make sure that path (C:\Program Files\dotnet) is in the PATH environment variable (add manually if it's not there)... I'd start with those two things.
Mar 09, 2017 10:17 AM|pgatto|LINK
inside the folder "C:
\ Program Files \ dotnet"
I found "dotnet" but lacked
in the environment variables path.
Below is the result of the command "dotnet
Hosting environment: Production
Content root path: C:\Web\virtualsitename
Now listening on: http://localhost:5000
Application started. Press Ctrl+C to shut down.
Mar 09, 2017 01:06 PM|Radomir|LINK
Good.. at least that's working now.. Is it working through IIS?
Mar 09, 2017 08:19 PM|pgatto|LINK
The site has been published
on IIS 8.5 on Windows Server 2012
Mar 13, 2017 08:08 PM|pgatto|LINK
I SOLVED by following this article:
<?xml version="1.0" encoding="utf-8"?>
Configure your application settings in appsettings.json. Learn more at https://go.microsoft.com/fwlink/?LinkId=786380
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
<aspNetCore processPath="C:\Program Files\dotnet\dotnet.exe" arguments=".\CustomersApp.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false" />
It was not correct the
"ProcessPath" of AspNetCore.