This article was previously published under Q330244
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
This article also applies to SQL Server 2000 Service Pack 3a (SP3a).
Because most changes introduced in SQL Server 2000 SP3a are related to setup, you do not have to apply SQL Server 2000 SP3a to instances of SQL Server 2000 or SQL Server Desktop Engine (also known as MSDE 2000) that have already been upgraded to SQL Server 2000 Service Pack 3 (SP3).
If you have instances that have not been upgraded to SQL Server 2000 SP3; however, you must upgrade those instances directly to SQL Server 2000 SP3a instead of SQL Server 2000 SP3. If you have any copies of the SQL Server 2000 SP3 download files that you were planning to use for future upgrades, you must delete those copies and use either the SQL Server 2000 SP3a download files or the SQL Server 2000 SP3a CD-ROM instead.
For applications that distribute and install MSDE 2000, install SQL Server 2000 SP3a instead of SQL Server 2000 SP3.
While you can apply SQL Server 2000 SP3a to instances of SQL Server 2000 SP3 or MSDE 2000 SP3, doing so has little effect on those instances. For more information about SQL Server 2000 SP3a, visit the following Microsoft Web site:
This article has been archived. It is offered "as is" and will no longer be updated.
When you remove Microsoft SQL Server 2000 Analysis Services Service Pack 3 (SP3) or Microsoft SQL Server 2000 Analysis Services Service Pack 3a (SP3a) to revert to an earlier version of Analysis Services, the repository connection strings registry keys values are reset to their default value.
This article describes how to restore the repository connection strings in the Microsoft Windows Registry to their pre-SP3 or pre-SP3a format if they were not backed up before the upgrade to SQL Server 2000 Analysis Services Service Pack 3 or 3a.
Microsoft recommends that you back up these Analysis Services repository connection string registry keys before you upgrade to SQL Server 2000 Analysis Services SP3 or SP3a:
Repository Connection String
After you install SQL Server 2000 Analysis Services SP3 or SP3a, if you want to revert to the previous version of Analysis Services, you must manually reset the repository connection string keys. To restore the repository connections when the keys are not backed up, follow these steps:
In Notepad, or any other text editor, create a file named Temp.udl in the temp folder.
Leave the file empty and save the file.
Double-click the Temp.udl file.
The Data Link Properties dialog box appears.
In the Data Link Properties dialog box, click Provider.
If the repository database is in Microsoft Access format, click to select Microsoft Jet 4.0 OLE DB provider from the OLE DB Provider(s) list box.
If the repository was migrated to SQL Server, click to select Microsoft OLE DB provider for SQL Server from the OLE DB Provider(s) list box.
If the repository database is in Microsoft Access format, click to select MSMDREP.mdb.
If the repository database was migrated to SQL Server, click to select the corresponding name of the server and the database. Type the User Name and the Password.
Click Test Connection to test the connection.
In Notepad, or any other text editor, open the Temp.udl file.
From the Temp.udl file, copy the connection string to the Repository Connection String and the RemoteRepositoryConnectionString registry keys in the following registry path:
If the repository database is in a Microsoft Access format, you must modify the data source in the connection string for the RemoteRepositoryConnectionString registry key. Use the server name and the repository share name instead of the drive letter and path. For example:
"...; Data Source=\\<servername>\MsOLAPRepository$\MSMDREP.mdb;..."