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

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

Aaryan — Thu, 16 May 2024 07:52:07 GMT

If your Qlik Sense Enterprise on Windows version is not compatible with the QSR database.

This may occur if:

You have upgraded Qlik Sense (for example: from May 2023 to November 2023) and have started the services. This will have migrated your QSR database from the May 2023 schema to the November 2023 schema.

You have then decided to roll back to May 2023 and are attempting to restore the November 2023 QSR. They are not compatible and the migration will fail.

the DbMigrationsConfiguration.AutomaticMigrationsEnabled to true to enable automatic migration.
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).

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)

QB-8813

Environment

all versions

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

allann — Wed, 15 Feb 2023 15:57:52 GMT

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?

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

Sonja_Bauernfeind — Thu, 16 Feb 2023 09:15:04 GMT

Hello @allann

There are three options:

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.
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

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

jeremyseipel — Tue, 04 Mar 2025 15:20:46 GMT

@Sonja_Bauernfeind we ran into this issue recently on an upgrade to November 2024. I see that you recently updated this post. Can you clarify what was updated with it, as well as what the current status is of QB-8813? Is there a Qlik approved way to avoid this error, since it essentially causes an upgrade to fail?

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

Sonja_Bauernfeind — Tue, 25 Mar 2025 09:33:03 GMT

Hello @jeremyseipel

The updates done were mostly cosmetic and to add clarity to the text. The Internal Investigation ID given is for reference, it is not indicative of a defect that is being worked on.

Generally speaking the root causes and resolution to this are still accurate.

To prevent this error, avoid the two possible root causes.

If you see the same error with a different root cause, please contact Qlik Support.

All the best,
Sonja