Summary
SMID is installed successfully, but first-time initialization fails.
All files are copied, configuration files are modified, and there is no error message during installation. However, one of the following symptoms is also present:
- Database creation failure logs are found in smdtemp/dbsetup.log.
- The dbsetup.log file is empty.
- The dbsetup.log file does not exist.
Details
This issue occurs when the value of the ServerTasks parameter in the notes.ini file exceeds 255 characters. Because of a Domino server limitation, only the first 255 characters of a value in notes.ini will be read by the server. If ServerTasks has more than 163 characters before SMID installation, this number will exceed 255 after the installation process, and cause the database creation to fail.
As a workaround to this Domino limitation:
- Open the notes.ini file.
- Locate the ServerTasks parameter and copy the values starting from “dbsetup”.
For example, from the following values:ServerTasks=Update,Replica,Router,AMgr,AdminP,CalConn,Sched,RnRMgr,LDAP,HTTP,CA,ndsrep notes1,ndsrep notes2 -f e:\notes\data\dsluxcfg.nsf,ndsrep metanotes -f e:\notes\data\metacfg.nsf,OnTimeGC SHBCalendar\OnTimeGC.nsf,dbsetup "D:\Notes\notes.ini" $Central_Admins 0 AC-75JA-UYUAB-12345-ABCDE-EUFEL-5UD7L 11111 1...copy this portion:dbsetup "D:\Notes\notes.ini" $Central_Admins 0 AC-75JA-UYUAB-12345-ABCDE-EUFEL-5UD7L 11111 1
- Run the copied values on the Domino console.
For example:> load dbsetup "D:\Notes\notes.ini" $Central_Admins 0 AC-75JA-UYUAB-12345-ABCDE-EUFEL-5UD7L 11111 1
SMID will now be able to start.
