Applies To:
  • CitectSCADA 5.xx

It seems that when the Ethernet cable is pulled from the primary Reports Server, the secondary either takes a long period of time to takeover, or never actually takes over the processing of reports. It correctly takes over if primary has GPF'ed or shutdown. 

The redundant Reports Server starts running reports when theNetBIOS connection to the primary returns an error. If using TCP/IP and relying on the transport layer to send 'Keep Alives', this may take a long time.

A routine has been added to exchange data between servers, at a user definable period (default is 30 seconds).  When sent from primary the redundant will cease running reports. When sent from redundant, and no reply is received within 'Hearbeat' period, it will begin processing of reports.

[REPORT] HeartBeat=1 (default)
[REPORT] HeartBeatTime=30000 (default) range is 500msec to 60000 msec

CIT has confirmed this to be a problem in Citect for Windows versions 5.XX. This problem has been fixed in version 5.01 Service Pack A.