Applies To:
  • CitectSCADA 5.30, 5.31, 5.40, 5.41 
Summary:
My CTAPI application is running remote from the Citect Server. It has been working for a couple of months but we have seen a deadlock detected error 302 as per article Q3494. However the solution does not seem to apply because we are not running the CTAPI application from the Citect Server. What can I do about this? 

Solution:
Deadlock detection is described in articles Q3163 and Q3494. If you are noticing deadlock detected errors you should see if the CTAPI timeout is sufficient. As mentioned in Q3138, the default was increased to 300 seconds in Citect version 5.30 and you can adjust the timeout by setting the [CTAPI]QueryTimeout parameter in your Citect.ini file. You can also disable the message display if you wish by using a new batch mode in the ctopen call. The mode is CT_OPEN_BATCH or 0x00008. It can be appended to another open mode using ampersand. Beware this message is not logged elsewhere. 
Keywords:
 

Attachments