Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Upgrade from UM 4.0.4 to UM 4.2.1

Does anyone has any issues when upgrading from UM 4.0.4 to UM 4.2.1? Thanks.

3 REPLIES

Re: Upgrade from UM 4.0.4 to UM 4.2.1

Hi -

You can use this Unity reconfiguration and upgrade guide link - http://www.cisco.com/en/US/customer/products/sw/voicesw/ps2237/products_upgrade_guides_chapter09186a0080205abd.html

Plus there are several forums that discuss this - not that they all apply to you, but just an FYI and consideration. Here is one - http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=IP%20Communications%20and%20Video&topic=Unified%20Communications&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddb3bd9

You didn't mention what version Exchange or SQL/MSDE for Unity database, but upgrades such as Exchange 2003 SP2 and SQL/MSDE SP 4 could also apply to your environment.

Ginger

New Member

Re: Upgrade from UM 4.0.4 to UM 4.2.1

Hi,

We have Exchange 2003 SP1 and SQL Server 2000 SP4. Thanks.

New Member

Re: Upgrade from UM 4.0.4 to UM 4.2.1

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.

103
Views
0
Helpful
3
Replies