i4SCADA Knowledge Base

Studio crashes when deleting Signals from a Signal Group

Abstract

Having troubles when deleting Signals from a Signal Group. Check out this article and learn how to overcome this issue.

On attempt to delete a signal, the system performs a check, looking for signal(s) associated dependencies (e.g. translations, alarm conditions, alarms, logs, etc).

Signals having alarm conditions or log conditions associated, cannot be deleted, until those dependencies are also removed. If there are other type of dependencies, the Signal Dependencies dialog will ask the user to confirm the deletion of the signal and all the corresponding dependencies. If the delete operation is finally approved, an attempt to delete the signal and all the corresponding dependencies is initiated.

Hence, the Signal deletion can be a long running operation. Most of the errors, encountered when deleting signals, are caused by time-outs of the queries executed against the database.

Solution

Studio exposes some of the properties, involved when such queries are run against the database.

Warning

There is no general recipe to fix these type of failures, but rather a trial and error process, by changing the values of the SQL command properties, until time-out errors stop occurring.

Since the time-out period of the SQL commands, involved in signals and signal dependencies deletion operations, are set to a default of 30 seconds, the i4SCADA system administrator can increase this value, if some of the operations fail, as follows:

  1. Open a File Explorer window and locate the WFStudio.exe file under the i4SCADA / Studio folder.

    WFStudioexe.jpg
  2. Open the WFStudio.exe file using an editor tool.

  3. If Studio crashed after selecting the delete signals option from the Signals grid, the most appropriate properties to modify, should be:

    1. GetDependenciesOnDeleteSignalsClassicCommandTimeOut

      GetDependencies.jpg
    2. DeleteSignalsBulkClassicCommandTimeOut.

      Delete_Bulk.jpg

    The default value for these two properties is set to 30 seconds, but it can be increased to a higher value.

    Important

    The XML code for the SQL command properties is commented, by default, thus the time-out value is set to 30 seconds. To change the time-out value, the XML code needs to be uncommented.

  4. If Studio crashed after selecting the delete signal option, on attempt to delete one of the ancestors, the most appropriate property to modify, should be:

    • DeleteAllSignalsOfGroupClassicCommandTimeOut

      Delete_all_signals_of_group.jpg

    Important

    The XML code for the SQL command properties is commented, by default, thus the time-out value is set to 30 seconds. To change the time-out value, the XML code needs to be uncommented.

  5. If none of these command properties lead to the expected result, the user can scroll through the WFStudio.exe file, to identify other command time-out properties, that can be associated to the error.