Troubleshooting timeout errors

Note: This topic applies only to on-premises environments.

If you receive timeout errors when executing long-running processes, use this section as a troubleshooting guide. The items listed are listed in the order you should check them. It is a good idea to keep track of the original settings so you can change them back if you like.

  1. Edit the Query Timeout value in the Configuration Manager:
    1. On the application server, select Start > All Programs > Infor > Tools > Configuration Manager.
    2. Select the configuration and click Edit.
    3. For the application database, ensure Query Timeout is set to 0 to make the timeout unlimited.
  2. On the SQL Server (database server), set the Query Wait value:
    1. Open SQL Management Studio and log in.
    2. Right-click on your SQL Server and select Properties.
    3. Click Advanced.
    4. Set the value of Query Wait to 0 to make the timeout unlimited.
  3. Set the MSDTC Transaction Timeout value:
    1. On the application server, select Start > All Programs > Administrative Tools > Component Services.
    2. Expand until you find My Computer.
    3. Right-click on My Computer and select Properties.
    4. Click the Options tab and set Transaction Timeout value to 0.
  4. Set the httpRuntime executionTimeout value in the web.config file on the application server where IIS is running:
    1. In C:\Inetpub\wwwroot\IDORequestService, find the web.config file. This file is delivered with Mongoose.
    2. Open the file and look for this section:
      <httpRuntime executionTimeout="number" maxRequestLength="16384"/>
    3. Change number to 7800, which is the maximum.
  5. Set the machineSettings maxTimeout value in the machine.config file on the application server:
    1. In C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG, find the machine.config file. This file is not delivered with Mongoose.
    2. Open the file and find the </configuration> element. Just to the left of it, add this section of code, which changes the timeout value to 2 hours:
      <system.transactions>
      <defaultSettings distributedTransactionManagerName="" timeout="02:00:00"/>
      <machineSettings maxTimeout="02:00:00"/>
      </system.transactions>