Dundas.Dashboard.Deployment.InstallationTaskException: The database upgrader has failed.
This error is seen when an attempt to upgrade the dashboard instance fails. The error appears at the end of the installation log.
The known causes and their respective resolutions are given below in this article. However, each scenario is different and to know the exact cause of this failure, the datastore needs to be sent for investigation. Contact Dundas Support to get the upload details of the datastore. See this link on what information is sent with datastore in case there are any concerns: What does the project export contain?
The alternate options listed below can also be tried for upgrading.
Known reasons and resolutions¶
The known reasons for this error to appear are:
- KPI/Dataset used on the dashboards have duplicate names.
The project has dashboards with duplicated Data Information (KPI or Dataset) instance names. Resolve this by renaming the
duplicate names and try the upgrade again. e.g. Rename with a numeric suffix at the end of the name, KPI_name (2)
- Cube structure changes that were applied since the dashboard objects were designed. This applies if OLAP data is being used and might be one or more of the following:
- Date mappings for OLAP cubes are wrong. They must be recreated.
- Date mapping of the cube is looking for an hierarchy level that changed. Redo the date mapping on the old instance instance and then try the upgrade.
- OLAP query parameters are pointing to invalid/missing hierarchies. Remove these parameters and try the upgrade.
- OLAP query parameters are defined for cubes where the Query is empty. Delete these parameters and upgrade.
- Unused cube connectors, datasets, reports and scripts etc. Delete any unused objects and try the upgrade again.
The following options can also be tried out first in order to upgrade before sending the datastore:
Use Clone Existing Databases option
This option is under the installation section of the deployment center and will install a new instance and clone the old instance. After this process, both new and the old version will be running simultaneously. You can deactivate the old version instance if the cloning is successful. See this link for details on the cloning process: Clone existing databases
Use Project Manager
This option will require a new instance of the new version to be installed. Then export all the projects in the old version using the project manager and import them to the new instance:
How to install a new instance: Advanced Intallation
How to use the project manager to import/export the project between instances:
Migrating the Projects and the Dundas Dashboard application
Using the DatabaseUpgradeUtility tool
Use the dashboard upgrader utility tool to upgrade your installation. See this link for details on this tool: DashboardUpgradeUtility
The advantage of this is that it’s a command line utility and is different from the installer.
This option may not be necessary if the project manager option is used as both these options require a new instance of the new version to be installed first.Before you try the steps below, make sure you have a copy of the datastore and sync databases.
To use this tool, follow these steps (In this example, assume upgrading from v4.0 to v5.0):
- Install a new v5.0 instance by creating new databases.
- In the config file of this new v5.0 instance, change the database connection strings to point to the v4.0.x databases:
- Restart IIS after making this change.
- Open the DashboardUpgrader utility and run it using the steps shown in this article.
- Point it to this changed config file.
After the upgrade, check the dbo.ConfigurationKey table for the key value. Each major version has a unique value. For example, for v4.0, it is 98. After upgrade to v5.0, it should be 104.