Applies To:
  • CitectSCADA 5.xx

When Citect is being used as an ODBC server with ODBC clients it will cause this error to return after doing many tag reads:

"Error Invalid Lock"

The time it takes for this error dialog to surface is directly related to how often the reads are taken and how often the Citect runtime is restarted. Restarting the runtime will cause the counter that is causing the problem to be reset.


CIT has confirmed this to be a problem in Citect for Windows versions 5.00 to 5.30. This problem has been fixed in version 5.30 Spk A.