Why does my project database show an error message after upgrading to 2024 and the Map View does not display any data?
In MIKE+ 2024 opening an existing MIKE+ 2023 or older setup (previously imported from MIKE URBAN) prompts a "Map initialization synchronization" issue. See Fig. 1.
/msdyn_blobfile/$value)
Fig. 1. Initialization issue with the Map View in a corrupted database.
We have observed this issue in MIKE+ 2024 Update 1, which gives an unexpected message when opening the 'Background map' editor, or which apparently resets the map projection to 'Local coordinates'.
The problem is caused by the wrong data in msm_ST table. There are two rows in msm_ST table in the MIKE+ database although MIKE+ GUI assumes the database can only have one row. See Fig. 2.
Fig. 1. Initialization issue with the Map View in a corrupted database.
We have observed this issue in MIKE+ 2024 Update 1, which gives an unexpected message when opening the 'Background map' editor, or which apparently resets the map projection to 'Local coordinates'.
The problem is caused by the wrong data in msm_ST table. There are two rows in msm_ST table in the MIKE+ database although MIKE+ GUI assumes the database can only have one row. See Fig. 2.
Fig. 2. msm_ST Table
The problem actually originates from MIKE URBAN, which sometimes allows two records in this table although it should only have one. The problem arises with MIKE+ model setups that have originally been imported from an old MIKE URBAN model, even if they were subsequently imported into MIKE+.
The problem actually originates from MIKE URBAN, which sometimes allows two records in this table although it should only have one. The problem arises with MIKE+ model setups that have originally been imported from an old MIKE URBAN model, even if they were subsequently imported into MIKE+.
To fix this, please use MIKE+ General SQL command tool (under ‘Tools’ menu) to execute below SQL syntax (rows after the first one will be deleted).
DELETE FROM msm_ST
WHERE rowid NOT IN (
SELECT rowid
FROM msm_ST
ORDER BY rowid
LIMIT 1); See Fig.3.
WHERE rowid NOT IN (
SELECT rowid
FROM msm_ST
ORDER BY rowid
LIMIT 1); See Fig.3.
Fig. 3. SQL command tool
Please remember to save the changes and restart the MIKE+ application to make sure everything is working as expected.
Alternatively, the modeler can open the SQLite database in a Database management software (in this case DB Browser for SQLite is used, see Figures 4 and 5).
Fig. 4. DB Browers for SQLite
/msdyn_blobfile/$value)
Fig. 5. Searching for Database tables in SQLite
Open the table msm_ST and search for more entries other than the first one. See Fig. 6.
Fig. 6. Duplicated entries in msm_ST Tables
Hoover the MOUSE over the table and do a "right-click" on the second row and use the option "Delete Record" to remove the conflicted entries. See Fig. 7.
Fig.7. Deletion of duplicated entries
After deleting the entries, the condition of the table is recovered, and the map can be projected again. See Fig. 8. and 9.
Fig. 8. Recovered table
Fig. 9. Projected map
Conclusion
Not all models in MIKE+ 2024 Update1 will present this issue, only those imported from MIKE URBAN in which the msm_ST Tables have been modified as described in this article. Nonetheless if this problem occurs in your model follow the workflow explained above.