Base solution for your next web application
Open Closed

Asp.Net Core - In-Process Hosting Model - Error 500.30 #7025


0
abarref created

Has somebody tried using InProcess hosting model? It's supposed to be faster than OutOfProcess: ASPNET-Core-Hosting-on-IIS-with-ASPNET-Core-22

The problem is that when enabling in it the following happens:


7 Answer(s)
  • 0
    maliming created
    Support Team

    https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/troubleshoot?view=aspnetcore-2.2#50030-in-process-startup-failure

    Can you look at Event log or standard output logs?

  • 0
    aaron created
    Support Team
  • 0
    leonkosak created

    ANZ is currently not prepared for In-Process hosting model. There was an issue on GitHub for this particular feature, but was not implemented because of some difficulties.

  • 0
    aaron created
    Support Team

    @leonkosak Thanks for the reminder.

    Tracked in aspnetzero/aspnet-zero-core#2019.

  • 0
    jguldemond created

    @abarref I have In-Process working, if you need help with this, let me know

  • 0
    abarref created

    Hi @jguldemod,

    Thanks for offering your help :)

    The other day I followed the suggestion made in a comment in the following thread: AspNetCoreModuleV2 and hostingModel="InProcess" in IIS sub application failing to start

    The most common issue people have been running into is the CurrentDirectory() being set to C:\Windows\System32\inetsrv rather than the app directory. Our current recommendation is to use https://github.com/aspnet/Docs/blob/master/aspnetcore/host-and-deploy/aspnet-core-module/samples_snapshot/2.x/CurrentDirectoryHelpers.cs to work around this until a future patch release.

    Is the same recomendation made by "neuhausf" in that other thread that aaron provided.

    Your fix is the same or is something else?

  • 0
    jguldemond created

    Hi @abarref,

    My solutions is even simpler. I added this line as the first line to Program.cs -> Main:

    Directory.SetCurrentDirectory(Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location));

    (and a extra using)