What is a difference between built-in Default Web Site and a Custom Website RRS feed

  • Question

  • User-809270565 posted

    Our ASP.NET MVC Core web application works under built-in Default Web Site in IIS 8.5 on Windows Server 2012 R2. But when we create our own custom website CompanyName.com, on the same IIS, with one of our company DSN and deploy the exact same application on this custom website, we get the http 502.5 - Process Failure error. Question: What is the difference here, why the same app is working under built-in Default Web Site but not under our custom website?


    Followed this tutorial to make sure windows server is ready for an ASP.NET Core website publishing.

    1. Success: For a test, created a very basic test ASP.NET Core MVC Core web application, published it on a local folder, copy and deployed the published folder on a Windows Server 2012 R2. Right clicked on  "Default Web Site" in IIS --> "Add Application", assigned the physical path to the published folder in Windows server, browsed the application in a browser with http://IP Address/MyPublishedFolder on a company desktop, the app successfully displayed its home page.
    2. Failure: On the same IIS, created a custom website companyName.com and repeated the same procedure as above but this time on Custom website. On a company desktop, browsed the application using http://CompanyName.com/MyPublishedFolder, browser displayed 502.5 - Process Failure error.

    Saturday, October 7, 2017 6:56 PM

All replies

  • User-460007017 posted

    Hi namwam,

    You could compare the application pool identity,loaduserprofile and NTFS permission,ACLS. In addition, try to set the application pool to no managed code.

    This link has provided the steps to fix 502.5 error:


    To host the asp.net core application in the custom website, please ensure you have take all the steps in the link above.


    •Confirm that the application runs locally on Kestrel. A process failure might be the result of a problem within the application. For more information, see  Troubleshooting tips.

    •Confirm that you didn't set a <PlatformTarget> in your .csproj that conflicts with the RID. For example, don't specify a <PlatformTarget> of x86 and publish with an RID of win10-x64

    , either by using dotnet publish -c Release -r win10-x64 or by setting the <RuntimeIdentifiers> in your .csproj to win10-x64

    . The project publishes without warning or error but fails with the above logged exceptions on the system.

    •If this exception occurs for an Azure Apps deployment when upgrading an application and deploying newer assemblies, manually delete all files from the prior deployment. Lingering incompatible assemblies can result in a System.BadImageFormatException exception when deploying an upgraded app.

    Best Regards,

    Yuk Ding

    Monday, October 9, 2017 6:37 AM