After going through a 19-hour session of anguish in getting 4.0(5) upgraded to 5.0(1), I thought I'd share the particular solution in my case. After four failures - each occurring at the very end of the upgrade process, the TAC case was requeued to a very talented TAC engineer named Vladimir. After reviewing the log files I sent, via WebEx he went to Enterprise Manager - Management - SQL Server Agent - Jobs - and saw that SQLNightlyBackupJob showed a failed icon. Then he went to the Commserver directory and renamed UnityDb.bak (which had a Last Updated time stamp over three years old) to UnityDb.bak.old. Next he started SQLServerAgent service, and manually ran the SQLNightlyBackup job, which recreated a fresh UnityDb.bak. The upgrade was started via CUICA for the fifth time, and this time it worked.
Looking back now, knowing the source of the problem, I found clues in two places: In each failure the THIRD-to-the-last OqlDump file - NOT the last one - shows these messages:
The backup data in 'UnityDbDump' is incorrectly formatted. Backups
cannot be appended, but existing backup sets may still be usable.
Msg 3013, Level 16, State 1, Server zzzzzzz, Line 4
BACKUP DATABASE is terminating abnormally.
This particular OsqlDump log has "Running UnitydbEx.sql" as its first line.
Also, the Windows Application log has the following two entries:
3041 :BACKUP failed to complete the command
IF EXISTS(select * from master.dbo.sysdevices where name = 'UnityDbDump')
BACKUP DATABASE UnityDb TO UnityDbDump WITH DESCRIPTION='First Backup, UnityDb', INIT
Cisco Unity Setup encountered an error while running configuration SQL script 'C:\CommServer\Localize\DefaultConfiguration\ENU\UnityDbEx.sql' [Error 0x80004005]
Finally, for any Unity Product Manager reading this - - For a product so well documented and supported, these failures with a generic message are a real anomaly. The causes documented on NetPro could easily be overcome within the upgrade process via scripting.
The 2021 IT Blog Awards, hosted by Cisco, is now open for submissions. Submit your blog, vlog or podcast by Friday, December 3.
To learn what's new in this year's competition or to gain insights into the judging considerations, check out t...
Greetings, Wanted to share a few lessons learned while migrating from a distributed to centralized IMP deployment. Our current setup included many CUCM/IMP distributed clusters with centralized Expressway server for MRA login. We did not wish to perf...
Parsec's Cisco UCCE/PCCE CC Connector application for CRM works as a bridge between the CRM and Cisco UCCE/PCCE CC solution.The CRM can be any cloud based CRM like Salesforce (SFDC), ServiceNow ,MS Dynamics or a 3rd party CRM.The CRM user/Agent will have ...
It’s a feature which allows CUCM to determine whether the phone is in its home location or a roaming station.By enabling this feature users can roam from one site to another site and acquire the site-specific settings such as Codecs, MRGL, Call rout...