Desktop Manager (all versions) installation fails when opening the database on the server

If you try to install Desktop Manager by email, or opening directly the Desktop Manager database on the server, but the installation fails, always open the DskMgrLog.txt file to understand the reason ( %temp%\dskmgrlog.txt up to v2.6 ; %temp%\dskmgr\dskmgrlog.txt for v2.7 and up)

If the DskMgrLog.txt ends-up like the following example, read the rest of the article :

2010/07/29 18:14:46 [45]
2010/07/29 18:14:46 [47]      - Install Start Database :
2010/07/29 18:14:46 [48]          + Extract DskMgrStart database on disk
2010/07/29 18:14:46 [48]              o Get DskMgrStart.nsf binary document by UNID
2010/07/29 18:14:47 [59]
2010/07/29 18:14:47 [60]
2010/07/29 18:14:47 [61]      - Search for Notes shortcuts
2010/07/29 18:14:47 [65]

>>> End of the DskMgrLog.txt, the Init process isn't completed, and you don't know where the issue comes from.

Please, open Desktop Manager database (using an ID listed with the [Admin] role) and check the properties of the "Desktop Manager Start Database" document from the Install Files view. You must have the File Name field value DskMgrStart.nsf : See attachement.

This issue has been seen on customers that saved 2 DskMgrStart.nsf databases in the "Desktop Manager Start Database" document when you need to extract it and sign it with your Server ID (our signature ID).

To update the "Desktop Manager Start Database" document correctly with a DskMgrStart db that you have just signed : edit the document, remove the old DskMgrStart.nsf (don't save the document), re-attach the new signed DskMgrStart.nsf and save the document.

At last, some frequent issues on this Start database come from either encrypted DskMgrStart.nsf database, wrong ODS version,  or even zipped DskMgrStart.nsf. Please, be careful when manipulating this binary.