A few issues with the Reports database files in that the SQL scripts at the end of setup do not run correctly against it and you get a message to call Cisco TAC.
Remedy: 1) Disconnect the Reports.mdf database from SQL Enterprise manager. 2) Rename the Reports.mdf and reports_log.ldf with a .old at the end. If you moved the files to a different Partition follow step 2 but rename the files if they still exisit in the original location. 3) Open up SQL Query Analyzer, goto file and browse to the \CiscoUnity4.2.1CD1\Reports\ReportSQLCreate.SQL script - this will recreate the Reports database. 4) Run through the setup again.
If you open the log files it will also show you you the script it failed on. To manually run all the scripts against the databases which is not recommended you can goto ConfigMgr.exe in the commsever directory.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...