If you cancelled the setup program at some point previously, you might be running in this issue. If this is not it, you can parse through the logs listed in that error dialog and look for any errors that jump out.
CSCdz26707
Symptom: On initial Unity installation, when the Cisco Unity Setup program is cancelled and then subsequently run again, this may cause Cisco Unity to think it's an upgrade and therefore, the upgrade scripts are run on a non-existent UnityDb database. This results in a failure near the end of the Unity Setup program.
Tempu.log entry has the following:
2006-06-16T16:22:32 - Beginning to install configuration, new install = 0
new install = 0 is only expected on Unity upgrades. This indicates that Unity thinks it is in upgrade mode, not initial install mode.
OsqlDump_*.Log shows:
"Could not locate entry in sysdatabases for database 'UnityDB'. No entry found with that name. Make sure that the name is entered correctly."
In upgrade mode Unity expects UnityDB to already be created, so this failure occurs.
Condition:
This problem may occur in any version of Unity. It should only occur when installing Unity initially, not on upgrades.
Workaround:
1) Run ConfigMgr.exe, which is located in the Commserver directory.
2) After the initial prompt, choose Advanced and check "Run database
configuration script". This runs C:\CommServer\Localize\DefaultConfiguration\ENU\DefaultDatabase.sql and will create the UnityDb with default settings.
NOTE: If this is run on a system with existing objects (subscribers, call handlers, etc), all non-default Unity objects will be wiped out.
