FIX: A Decision Support Objects (DSO) connection attempt fails after you install SQL Server 2000 Analysis Services Service Pack 4 (903030)

CAUSE

This problem occurs because SQL Server 2000 Analysis Services SP4 does not automatically encrypt new values in the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\Server Connection Info\Repository Connection String

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\Server Connection Info\RemoteRepositoryConnectionString

After you install SQL Server 2000 Analysis Services SP4, a DSO connection attempt fails after you modify a repository connection string by inserting a new value programmatically.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 Analysis Services service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

To apply this hotfix, you must have SQL Server 2000 Analysis Services SP4 installed on the computer.

Restart information

You do not have to restart the computer after you apply this hotfix. However, the Analysis Services service is stopped and then restarted during the installation of this hotfix.

Registry information

You do not have to change the registry.

File information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.SQL Server 2000 32-bit versions

File name	File version	File size	Date	Time	Platform
Msmddo80.dll	8.0.0.2157	4,090,656	02-Sep-2005	00:52	x86
Msmdsgn80.dll	8.0.0.2157	9,646,153	02-Sep-2005	00:51	x86
Msmdsrv.exe	8.0.2157.0	1,970,176	02-Sep-2005	00:00	x86
Msolap80.dll	8.0.2157.0	2,120,408	02-Sep-2005	00:52	x86

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

MORE INFORMATION

When you install Microsoft SQL Server 2000 Analysis Services Service Pack 3 (SP3), the registry keys that are mentioned in the "Cause" section are encrypted to improve security. SQL Server 2000 Analysis Services SP3 contains the code that is required to detect and to automatically encrypt a repository connection string value in the registry during a DSO connection attempt.

When you modify a repository connection string value in the registry, SQL Server 2000 Analysis Services SP3 encrypts the repository connection string value when the next DSO connection attempt occurs. This functionality is not available after you install SQL Server 2000 Analysis Services SP4.

This hotfix includes a new RepositoryManager object in the DSO library (Msmddo80.dll) to provide an automated technique to modify the repository connection string. The RepositoryManager object contains the following methods:

The GetRepositoryConnectionString method
The GetRemoteRepositoryConnectionString method
The UpdateRepositoryConnectionStrings method

The following code example illustrates how to use the RepositoryManager object to retrieve the repository connection string values.

set RepCnStrMngr = CreateObject("DSO.RepositoryManager")
cnStr = RepCnStrMngr.GetRepositoryConnectionString( <servername> ) 
remoteCnStr = RepCnStrMngr.GetRemoteRepositoryConnectionString( <servername> )

Note In this code example, <servername> is the name of the server.

The following code example illustrates how to use the RepositoryManager object to update the repository connection string values.

set RepCnStrMngr = CreateObject("DSO.RepositoryManager")
RepCnStrMngr.UpdateRepositoryConnectionStrings ( <servername> ), (connetionStr), ( remoteConnectionStr )

Note In this code example, <servername> is the name of the server.

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about the terminology that Microsoft uses when Microsoft corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates