09-19-2011 10:16 AM - edited 03-16-2019 07:04 AM
I am at my wits end so hopefully someone has an answer as TAC can not figure this one out.
Upgrading from unity 5 to unity 8.0(3.3)
I'm getting an error at the end of the unity install This error is in reference to a SQL configuration Script.... applications event log says
"Cisco unity setup encountered an error while running configuration SQL script "D:\commserver\localize\defaultconfiguration\ENU\ENU_defaultdatabaseprep.sql (error 0x80004005)
I have tried different service accounts, installed SQL from the unity upgrade once, un installed it, re installed it from Data store 2000 disk,
If anyone has the answer please help! I spent all last week on the phone with TAC and still no further than before, I have re installed the platform config disks as TAC said that would fix it but still the same issue.
Thank you in advance.
09-19-2011 11:53 PM
Hi
Can you post up some logs?
I'd be most interested in the osqldump logs first.
Regards
Aaron
09-20-2011 07:05 AM
Hi Aaron, Here is the latest from yesterday
"Msg 911, Level 16, State 1, Server SU1UM1, Line 22
Could not locate entry in sysdatabases for database 'UnityDB'. No
entry found with that name. Make sure that the name is entered
correctly."
we have went in and tried to attach the unitydb.mdf database to the database folder but it still gives us the same error at the end.
another log is below, kind of long but most are like I posted above, also I believe the unitydb error is after we try the unity upgrade install.
Also I took out alot of the 1 row affected 0 rows affected due to length of log file.
Running UnityDefaultSQLObjects.sql
Amis RestrictionTable is Null in the Configuration table; Reading
value from the registry.
RegQueryValueEx() returned error 2, 'The system cannot find the file
specified.'
Amis RestrictionTable is Null in the registry; Nothing more to do.
Insert ConvHotel, Opt1 and Standard conversations.
(1 row affected)
(1 row affected)
(1 row affected)
Insert alternate custom 2.
(1 row affected)
Insert alternate custom 3.
(1 row affected)
(0 rows affected)
(0 rows affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(0 rows affected)
(0 rows affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(0 rows affected)
(1 row affected)
(0 rows affected)
(0 rows affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
Setup the clean delete objects if not set
CallHandlerecipName is Null in the registry.
Found defined alias for the example admin call handler.
(0 rows affected)
(0 rows affected)
(0 rows affected)
CallHandOwnerName is Null in the registry.
Found defined alias for the example admin call handler.
(0 rows affected)
(0 rows affected)
(0 rows affected)
CallHandAFtMsgName is not Null in the registry.
CallHandExitName is not Null in the registry.
Msg 911, Level 16, State 1, Server SU1UM1, Line 5779
Could not locate entry in sysdatabases for database 'ReportDb'. No
entry found with that name. Make sure that the name is entered
correctly.
Msg 3013, Level 16, State 1, Server SU1UM1, Line 5779
BACKUP DATABASE is terminating abnormally.
(0 rows affected)
(0 rows affected)
(1 row affected)
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