Articles in this section
Category / Section

Resolving the Specified CGI Application Error in Azure App Service

Published:
Updated:

Encountering the The specified CGI application encountered an error and the server terminated the process error in Azure App Services can severely disrupt your application’s functionality. This issue typically arises from problems within a CGI (Common Gateway Interface) application running on a web server, often due to resource limitations such as exceeding memory or execution time limits.

To address this issue, you can adjust the request timeout settings in the web.config files using the following steps:

  1. Begin by stopping the Azure App Service to prevent conflicts during configuration adjustments.

  2. Locate and open the following web.config files within your application directory:

    • wwwroot\reporting\Api\web.config
    • wwwroot\reporting\reportservice\web.config
    • wwwroot\reporting\Viewer\web.config
    • wwwroot\reporting\Jobs\web.config
  3. In each web.config file, within the aspNetCore section, add the requestTimeout property as shown below:

    <aspNetCore processPath="dotnet" arguments=".\Syncfusion.Server.API.dll" requestTimeout="00:20:00" stdoutLogEnabled="false"     stdoutLogFile=".\logs\stdout" hostingModel="inprocess" />
    
  4. Set the requestTimeout attribute to “00:20:00” to establish a 20-minute limit for request timeouts, accommodating longer processing durations.

    <?xml version="1.0" encoding="utf-8"?>
    <configuration>
         ....
          <aspNetCore processPath="dotnet" arguments=".\Syncfusion.Server.API.dll" requestTimeout="00:20:00" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" />
         ....
    </configuration>
    
  5. Save the changes made to each web.config file after inserting the code snippet and updating the request timeout.

  6. Once all modifications are saved, restart the Azure App Service to implement the adjustments effectively.

Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Please  to leave a comment
Access denied
Access denied