I/NET events / alarms stop updating in EcoStruxure Building Operation

NOTICE

POTENTIAL FOR DATA LOSS.
The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure, please contact Product Support Services prior to attempting the procedure below.

NOTICE

COMPLEX PROCEDURE REQUIRED.
The resolution of this article has many complex steps that may result in unforeseen results if not performed correctly. If you are at all unfamiliar with the requirements, please contact Product Support Services for assistance.

Issue

After upgrade of Building Operation and / or I/NET, I/NET alarms and events have stopped updating within WorkStation.

Product Line

TAC I/NET, SmartStruxure Solution

Environment

I/NET Seven 2.4x Integration with Enterprise Server

EcoStruxure Building Operation 1.8 and above.

Cause

Within the I/NET Seven SQL database table [InetDb].[dbo].[Events].[EventId], the EventId has not incremented correctly, so there is a missing EventId (causes unknown).

Because of this missing EventId Building Operation waits at this missing ID to appear before updating its own event.db database.  Since this ID will never show, no events will ever be passed through to Building Operation and effectively stops any I/NET events appearing within Building Operation WorkStation

This EventId is seen in a registry entry called NspAmtEventId under the following path:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\CSI - Control Systems International\I/Net 2000\Configurations

Resolution

Current workaround is to manually edit this registry key NspAmtEventId value to:

  1. A value above the highest [InetDb].[dbo].[Events].[EventId].value - if the past events are not required.  OR
  2. Increment its value by 1 if all past values are required to be retained. i.e. If NspAmtEventId = 82237682 typically only needs to be changed to 82237683 to correct this issue.  If not then you should check the [InetDb].[dbo].[Events].[EventId].value

After editing this registry value the Enterprise Server service needs to be restarted, after which events will then start to be processed by Building Operation.

It should be noted if you use option 2 above that there will be some time for all this data to be updated within Building Operation and there may be some bogus (old) alarms appear, which should be taken into consideration before implementing this resolution.