Qlik Sense Repository Service fails with Error An exception was thrown while invoking the constructor 'Void .ctor()' on type 'DatabaseContext

[Aaryan]

If an incorrect version was installed during an upgrade of a Qlik Sense Enterprise on Windows multi node environment, such as installing different versions on RIM nodes, the Qlik Sense Repository service will not start on any node (including the central node). 

Environment

• Qlik Sense Enterprise on Windows all versions

An incorrect version of Qlik Sense Enterprise on Windows in a multi node environment will trigger a database migration to this version. The result is that the Qlik Sense Repository service fails to start with the error: 

Fatal exception during startup Unable to update database to match the current model because there are pending changes and automatic migration is disabled. Either write the pending model changes to a code-based migration or enable automatic migration. Set DbMigrationsConfiguration.AutomaticMigrationsEnabled to true to enable automatic migration.↵↓An exception was thrown while invoking the constructor 'Void .ctor()' on type 'DatabaseContext

 

Resolution: 

As database migration started which had caused database corruption, you need to revert back to the old database backup to resolve this issue or contact Qlik Support for assistance.

Internal Investigation ID(s)

1. QB-8813

[allann]

If we accidentally install a newer version (Nov22) on a rim node, while the central and other rim nodes are on an older (May22), do we have to reinstall everything?

[Sonja_Bauernfeind]

Hello @allann 

There are three options:

1. If you have not started the rim node after upgrading it (meaning it has not connected to your central database), then you can uninstall the rim node and re-install it on May 2022.
2. If you have started the rim node after the upgrade (meaning it has connected to your central database and made changes that cannot be reversed), then you will be unable to reconnect the rim node on May 2022. You will need to either:
   1. Revert to a previous backup of your Qlik Sense deployment taken before the rim node was upgraded (see Backup and restore Qlik Sense Enterprise on Windows ), as well as reinstall the rim on the old version. 
   2. Upgrade your entire deployment to November 2022 (recommended).

Hope this helps!

All the best,
Sonja