[KBA-79008] IONodes decoders stop displaying video after upgrading to Security Center 5.8 - Security Center 5.8

series
Security Center 5.8
revised_modified
2019-10-24
TFSnum
2280256

[KBA-79008] IONodes decoders stop displaying video after upgrading to Security Center 5.8

This article explains why IONodes decoders no longer display video after you upgrade to Security Center 5.8.x.x.

Applies to: Security Center 5.8

Symptoms

After upgrading to Security Center 5.8, monitors connected to IONodes decoders turn black and do not display video.

Cause

A coding issue.

Workaround

Perform one of the following three workarounds:
  • If you have not yet upgraded to Security Center 5.8.x.x, do the following on your system:
    1. From the home page in Config Tool, open the Video task.
    2. Select the Archiver role and click the Resources tab.
    3. In the lower-right corner, click Advanced settings > Add, and enter the following:
      Name
      DisableAddKnownConfigs
      Value
      True

    4. Click OK > Apply.
    5. Upgrade your system to Security Center 5.8.x.x.
  • If you already upgraded to Security Center 5.8.x.x, do the following on your 5.8 system:
    1. From the home page in Config Tool, open the Video task.
    2. Select the Archiver role and click the Resources tab.
    3. In the lower-right corner, click Advanced settings > Add, and enter the following:
      Name
      DisableAddKnownConfigs
      Value
      True
    4. Click OK > Apply.
    5. Deactivate the Archiver role.
    6. On the primary Archiver server and secondary Archiver server (if you have Archiver failover set up), rename the Cache folder in C:\Program Files (x86)\Genetec Security Center 5.x\Archiver.
    7. Restart the Archiver role.

      The video on the monitors that are connected to IONodes decoders should start streaming.

    8. (Optional) After the decoders are displaying video, you can delete the DisableAddKnownConfigs advanced Archiver role setting.
  • Delete and re-add affected decoders in Security Center.

Status

This issue will be fixed in Security Center 5.9.x.x.