Before you install or upgrade Cisco Unity versions, a Microsoft SQL Desktop Edition (MSDE) Service Pack installation is often required. This document describes how to install MSDE Service Packs for Cisco Unity.
There are no specific requirements for this document.
This document is applicable to any server running a Cisco approved application that utilizes an instance of MSDE 2000 such as Cisco Unity 3.0, 3.1, or 4.0 with 32 ports or less.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
Service Packs for SQL Server 2000 are provided in three parts to reduce the size of downloads.
Analysis Services Components
Desktop Engine (MSDE)
The installation process for SQL Service Pack from the Microsoft web site is in three parts. This document covers only the portion of the installation that relates to MSDE. The installation of Service Pack 3 is used as an example.
To install a MSDE Service Pack for Cisco Unity, complete these steps.
If you already have a version of Cisco Unity 3.0, 3.1, or 4.0 running, stop Cisco Unity to properly apply the patch.
Go to Microsoft's web site and download the patch.
Service Packs for SQL Server 2000 are provided in three parts to reduce the size of downloads. The Desktop Engine is the necessary download to apply the Service Pack to MSDE. For this example, you need SQLDeskSP3.exe..
Once you download the file, run the executable by double clicking on the file name SQLDeskSP3.exe.
When prompted to extract the compressed files to C:\sql2ksp3, accept this default location.
Insert the Cisco Unity Data Store 2000 CD.
This is required for this installation to complete successfuly. If the SQL Installation menu starts automatically, close it before you proceed.
To properly install MSDE Service Pack 3, run the patch from a command prompt. Open a command prompt window and navigate to C:\sql2ksp3\MSDE.
Note: You cannot run the MSDE version executable from Windows Explorer. If you attempt to run it from Explorer, this error message appears:
Type setup /upgradesp sqlrun in the command prompt window and press Enter.
If you experience any problems installing this patch, refer to the Read Me file that is included with the files. The local path is C:\sql2ksp3\MSDE\sp3readme.htm. This file contains information on all three of the downloadable Service Pack 3 files, not just the SQLDeskSP3.exe file. The section name for this information is "Install Desktop Engine SP3".
If you have Internet access, you can also reference Microsoft Knowledge Base Article - 810826 (INF: New Switches in MSDE Service Pack 3 Setup) instead. This article contains information that is specific to this patch and is easier to read.
When the installation has finished, you receive a notification that the patch has been applied and that you need to reboot the server to complete the installation process. Reboot now.
Once the reboot is complete, Cisco Unity starts as expected.
If the installation of MSDE Service Pack 3 causes the error "Instance name is invalid," complete these steps:
Browse to the folder that you extracted the MSDE service pack files to.
Browse to the MSDE directory.
Right-click on the Setup.exe file and select Create Shortcut.
Right-click on the shortcut to Setup.exe and select Properties.
In the target field add /upgradesp sqlrun blanksapwd=1 after Setup.exe.
If you extracted the files to c:\temp, the string is "c:\temp\sql2ksp3\MSDE\setup.exe /upgradesp sqlrun blanksapwd=1".
Double-click on the shortcut to Setup.exe to run the upgrade.
Refer to Checking SQL Server or MSDE Version and Service Pack Level to verify the details of an instance of MSDE.
The Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers.
Refer to Cisco Technical Tips Conventions for information on conventions used in this document.