Trouble with Long Lasting Transactions

The DTC transaction timeout is 60 seconds by default that should be enough for the majority of operations to be completed. But, if a transaction timeout exception regularly occurs and stops data processing due to a huge number of objects being attempted to be processed by the application, the default transaction timeout value can be increased as follows.

1. Click Start and then type "run" to open the Run application.

2. In the Run application, type the dcomcnfg command to open Component Services.

   

3. In Component Services, go to Computers > My Computer
   

4. Right-click My Computer and select Properties.

5. Go to the Options tab, and increase the Transaction Timeout value.
   

6. Click OK to save the changes made and close Component Services.

7. Click Start and then type "run" to open the Run application.

8. In the Run application, type the services.msc command to open Services.

9. Find the service Distributed Transaction Coordinator and restart it to apply the changes made.
   

   Notes: If you have to change the DTC transaction timeout, please, do that across all the servers involved into the solution including the AVEVA NET Gatekeeper or AVEVA Change Manager web server, the AVEVA NET Workhub and Dashboard server, the AVEVA WorkMate server (if it is used), and the database server. If you have to change the DTC default transaction timeout, it would be worth to update a value of the configuration Internal.ServiceRequest.StoredProcedures.CommandTimeout accordingly as described in the chapter 5 Application Factory Settings: Application Domain of the AVEVA NET Gatekeeper and AVEVA Change Manager Configuration Guide.