Page 1 of 1

ASP.NET Core Module Log file not created

Posted: Fri May 05, 2017 7:02 pm
by ashraf4

I need help for this issue as I can't run the application using Testing Web Server "Other"

Operating system is Window Server 2008 R2 Standard

Error HTTP Error 502.5 - Process Failure

The application responds normally at the Kestrel endpoint address localhost:5000


Re: ASP.NET Core Module Log file not created

Posted: Sat May 06, 2017 11:02 am
by motfs

Make sure:

  1. You have installed Windows Server Hosting (x64 & x86) on the server.
  2. You have created web application in IIS Manager.
  3. You have published the application and uploaded the published files (not the generated scripts). Read "Generate Settings" in the help file.

log file not created

Make sure you have enabled the option "Enable ASP.NET core stdout log" (click Tools -> Advanced Settings -> Enable ASP.NET core stdout log) and you have setup read/write permission for the log file folder. Also, post the generated file "web.config" here.

Create a subfolder named "logs" under the application folder.

HTTP Error 502.5 - Process Failure

This is a generic error message. Trouble shoot the cause as recommended in publishing to IIS (https://docs.microsoft.com/en-us/aspnet ... ishing/iis). Check this out as well (https://github.com/aspnet/Hosting/issues/844) and search the issue relate to Window Server 2008 R2.


Re: ASP.NET Core Module Log file not created

Posted: Sat May 06, 2017 7:18 pm
by ashraf4

I already installed Microsoft .Net Core 1.0.4 & 1.1.1 – Windows Server Hosting

The application is working with Kestrel without any issue but the error HTTP Error 502.5 - Process Failure is shown when [Testing root URL] with Other

Project folder
C:\inetpub\wwwroot\project1\
In Advance Settings
Publish output : C:\inetpub\wwwroot\poutput\
Enable ASP.Net Core stdout log - selected
Logs subfolder have been created under the applicaion folder

localhost/poutput/
HTTP Error 502.5 - Process Failure


Re: ASP.NET Core Module Log file not created

Posted: Mon May 08, 2017 12:24 pm
by motfs

After installing Windows Server Hosting, make sure you have restarted your IIS.

Make sure you have created a web application in your IIS Manager properly, set the .NET CLR version to "No Managed Code", read "publishing to IIS" for details.

Make sure you have enabled the option "Enable ASP.NET core stdout log" (click Tools -> Advanced Settings -> Enable ASP.NET core stdout log) and you have created the log file folder and setup read/write permission for the log file folder. Also, post the generated file "web.config" here.

Did you setup the read/write permission for the log file folder? Post the generated file "web.config" so as to confirm the setting.

motfs wrote:
HTTP Error 502.5 - Process FailureThis is a generic error message. Trouble shoot
the cause as recommended in publishing to IIS (h+ttps://docs.microsoft.com/en-us/aspnet
... ishing/iis). Check this out as well (h+ttps://github.com/aspnet/Hosting/issues/844)
and search the issue relate to Window Server 2008 R2.

Process Failure is a generic error message. Follow the recommendation from the document "Publishing to IIS" to trouble shoot. Make sure you have followed the instruction from "Publishing to IIS" to deploy the application.