08-27-2008 07:16 AM - edited 03-18-2019 09:32 PM
I am trying to setup a brand new Unity 7.0.2 and am getting an error "Setup was unable to configure default settings", it comes right in the end where it tries to run the "DefaultUnitySQL" Scrips, any ideas?
Solved! Go to Solution.
08-27-2008 07:38 AM
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.
08-27-2008 07:38 AM
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.
08-27-2008 08:16 AM
I have gotten this error many times also on Unity 7.02. You need to make sure that the 2 sql services are running with a local account and not a domain account. If you are installing failover, after you install both servers you change it to a domain account.
You can run the unityuninstall and try again but there are some caveats, you will need to run cuspa again and reinstall at least one program. I can't remember everything but it is obvious.
Hope this help and please post.
Randy
08-27-2008 09:33 AM
I am running SQL services with the local system account and at this time its not part of the failover environment. This is actually a uninstall/reinstall of unity 7.0.2.
08-27-2008 10:38 AM
What are the steps you did to uninstall?
What OS and version of Exchange?
Randy
08-27-2008 11:25 AM
I used the uninstall unity utility, however we found what the problem was, while doing the uninstall, it aparently didn't remove the unitydb from it and contained some old entries in there, after we detached the unitydb and moved the .mdb files to another location, it went fine. Thanks for your help.
08-27-2008 01:00 PM
Glad to see that you got through it. Now I remember that sometimes the UnityDB does not get detached and the commserver dir does not get deleted.
Randy
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide