[KBA-78968] Database of the Incident Manager role fails to upgrade - Genetec Mission Control™ 2.9 - 2.10

series
Genetec Mission Control™ 2.9 - 2.10
revised_modified
2019-02-05

[KBA-78968] Database of the Incident Manager role fails to upgrade

This article explains why the database of the Incident Manager role might fail to upgrade when you upgrade from Genetec Mission Control™ 2.9 GA to 2.10 GA.

Applies to: Genetec Mission Control™ 2.8 - 2.10

Symptoms

After upgrading to Genetec Mission Control™ 2.10 GA, the Incident Manager role does not restart. The Database status remains in the Upgrading state in the Resources tab.

You receive the following error messages in the logs:

Cause

In Genetec Mission Control™ 2.8 GA or 2.9 GA, if you configure a Dynamic Standard Operating Procedure (DSOP) step with an apostrophe ('), the DSOP is corrupted after upgrading your Genetec Mission Control™ software.

If you upgraded from Genetec Mission Control™ 2.8 GA to 2.9 GA and a DSOP is corrupted, the database fails to upgrade when you upgrade from 2.9 GA to 2.10 GA.

Workaround

If you upgraded from Genetec Mission Control™ 2.8 GA to 2.9 GA, do the following:
  1. Deactivate the Incident Manager role.
  2. Install Genetec Mission Control™ 2.9 GA Cumulative Hotfix 010.
  3. Activate the Incident Manager role.
  4. Reconfigure the affected DSOP.
If you upgraded from Genetec Mission Control™ 2.9 GA to 2.10 GA and the database failed to upgrade, do the following:
  1. Deactivate the Incident Manager role.
  2. Install Genetec Mission Control™ 2.10 GA Cumulative Hotfix 001.
  3. Activate the Incident Manager role.
  4. Reconfigure the affected DSOP.

Status

This issue is resolved in Genetec Mission Control™ 2.9 GA Cumulative Hotfix 010 and 2.10 GA Cumulative Hotfix 001.