The specified CGI application encountered an error and the server terminated the process

Question

I am hosting a asp.net 5 application on azure, the code is complied for beta8, the application runs fine on the local environment and when i publish the code on the azure site. i get a common error "The specified CGI application encountered an error and the server terminated the process."

I had this problem with an Azure app service. MS Support said "There was worker instance movement event, 204 switched to 211, due to platform upgrade". Restarting the app service fixed the issue. — David Klempfner, Jan 20 '22 at 04:48

score 16 · Accepted Answer · answered Nov 12 '15 at 13:12

I was able to solve this issue by removing forwardWindowsAuthToken from the web.config file under wwwroot.

Navigate to src/ProjectName/wwwroot
Open the web.config
In the httpPlatformremove the forwardWindowsAuthToken="true/false" property

Redeploy and mine worked fine.

See here https://github.com/aspnet/Hosting/issues/364 for plenty of discussion

Shaun Luttin · Answer 2 · 2016-07-11T17:52:50.907

Short Answer

For us the fix was to to UseIISIntegration() on the WebHostBuilder.

public static void Main(string[] args)
{
    var host = new WebHostBuilder()
        .UseContentRoot(Directory.GetCurrentDirectory())
        .UseKestrel()
        .UseIISIntegration() // Necessary for Azure.
        .UseStartup<Program>()
        .Build();

     host.Run();
}

More Details

Our web.config looks like this:

<?xml version="1.0" encoding="utf-8"?>         
<configuration>                                
<system.webServer>                             
    <handlers>                                 
    <add name="aspNetCore"                     
        path="*"                               
        verb="*"                               
        modules="AspNetCoreModule"             
        resourceType="Unspecified"/>           
    </handlers>                                
    <aspNetCore processPath="%LAUNCHER_PATH%"  
        arguments="%LAUNCHER_ARGS%"            
        stdoutLogEnabled="false"               
        stdoutLogFile=".\logs\stdout"          
        forwardWindowsAuthToken="false"/>      
</system.webServer>                            
</configuration>

Our project.json looks like this:

{
  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.0.0",
      "type": "platform"
    },
    "Microsoft.AspNetCore.Server.IISIntegration": "1.1.0-*",
    "Microsoft.AspNetCore.Server.Kestrel": "1.1.0-*"
  },
  "tools": {
    "Microsoft.AspNetCore.Server.IISIntegration.Tools": "1.0.0-preview2-final"
  },
  "frameworks": {
    "netcoreapp1.0": {}
  },
  "buildOptions": {
    "emitEntryPoint": true
  },
  "publishOptions": {
    "include": [
      "web.config"
    ]
  },
  "scripts": {
    "postpublish": [
      "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%"
    ]
  }
}

Our nuget.config looks like this:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="AspNetVNext" value="https://www.myget.org/F/aspnetcidev/api/v3/index.json" />
    <add key="NuGet" value="https://api.nuget.org/v3/index.json" />
  </packageSources>
</configuration>

when the server was taking too long to respond while doing some slow operation I was getting the same error even in localhost, then I added the "UseIISIntegration" and it did work. thanks — Rodrigo Leite, Feb 16 '18 at 20:11

score 8 · Answer 3 · answered Apr 17 '18 at 19:10

8

This can also happen if you have an infinite loop in your code.

answered Apr 17 '18 at 19:10

pim

12,019
6
66
69

Happened to me as well, there was a recursive infinite call. It doesn't log anything, and the app just restarts. – carraua Apr 02 '19 at 12:38
Totally agree, all the other solutions here involves to "redeploy" which is basically cleaning the issue, not a real solution. But what I understand can reproduce the issue is an infinite loop on which you consume more resources than expected from your plan. – Yogurtu Mar 25 '22 at 04:41

score 5 · Answer 4 · answered May 03 '19 at 14:22

5

I recently had the same issue and was able to solve it by setting the requestTimeout within the web.config:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <location path="." inheritInChildApplications="false">
    <system.webServer>
      <handlers>
        <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
      </handlers>
      <aspNetCore processPath=".\PROJECT.exe" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" requestTimeout="00:30:00"/>
    </system.webServer>
  </location>
</configuration>

answered May 03 '19 at 14:22

Martin Brandl

56,134
13
133
172

1

I'm recommending following the above approach first. It's works for me perfectly. – Harshan Feb 23 '22 at 08:40
1

Thank you, I realize that adding the "requestTimeout" bit worked as you suggested. – Chidi-Nwaneto May 20 '22 at 12:25

score 4 · Answer 5 · answered Aug 02 '16 at 13:53

4

I just ran into this error whilst deploying an ASP.core app using .NET 5.4.2. The fix was to deploy to a fresh app service instance. My guess was that there was some junk left lying around from a previous deployment which used a different framework version.

answered Aug 02 '16 at 13:53

Tom Makin

3,203
23
23

1

This worked for me. But instead of recreating a fresh Appservice I connected on the "dirty" existing one through FTP, deleted all the wwwroot content and republished the app. – Sbu Sep 15 '17 at 06:20
Another option along these lines, which worked for me, is to scale the app service plan up and then back down. It moves you to new infrastructure without needing to scrap the original app service. – ChiefMcFrank Jul 07 '21 at 15:34

score 3 · Answer 6 · answered Jun 12 '19 at 07:33

3

I was facing the same issue following are steps how I resolved.

My application was .NET CORE 2.2 and I was deploying in the Azure web app.
Right Click on the project and click on the publish button.
Select the publish profile which you downloaded from Azure.
Next, change the deployment mode under Summary to Self-Contained.
Now click on publish button it should work.

answered Jun 12 '19 at 07:33

Sagar Patil

469
9
20

Any info as to *why* Self-Contained mode fixes this? – slasky Oct 10 '19 at 16:34
It copies the corresponding .NET framework files to the server. Most likely it ensured that the expected version was available. – Joshua Drake Nov 06 '19 at 15:06

score 0 · Answer 7 · answered Feb 23 '18 at 02:09

0

I have this problem in the azure app service, since the version of asp.net core is preview version, so I update the asp.net core version by NuGet to 2.0.1 and redeploy the app.

The app works again.

answered Feb 23 '18 at 02:09

Crazy Crab

694
6
16

score 0 · Answer 8 · answered Oct 06 '18 at 14:23

0

I'm using .NET Core 2.1 and EF Core deployed to an Azure web app. I got this error when I switched from using a database account with db owner rights to a limited database account. I suspect EF needs a right I'm missing when the app starts.

answered Oct 06 '18 at 14:23

John81

3,726
6
38
58

score 0 · Answer 9 · edited Apr 14 '20 at 08:43

I got the same error. After searching some solutions, I changed the code, replacing the async method calls with non-async ones, regarding the notes that thread pool might exceed the allowed capacity. This did not work. Then I increased the request timeout in web.config to 20 minutes and it is resolved.

Add the string below in web.config file.

requestTimeout="00:20:00"

as

<aspNetCore processPath="dotnet" arguments=".\API.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" requestTimeout="00:20:00" />

score 0 · Answer 10 · answered Nov 03 '20 at 08:08

0

Today we had the same problem. In our case it was caused by a failing Debug.Assert(...).

answered Nov 03 '20 at 08:08

Dejan

9,150
8
69
117

Lesson learned: `dotnet publish` does not take the `Release` configuration by default. Needs to be `dotnet publish -c Release`. – Dejan Nov 03 '20 at 08:09

score -2 · Answer 11 · answered Nov 27 '20 at 16:03

-2

For us its not related with code, appservice redeploy and then restart needs to be done

answered Nov 27 '20 at 16:03

Siva Sudarsan

1

The specified CGI application encountered an error and the server terminated the process

11 Answers11

Short Answer

More Details

Linked