FIX: MSOLAP Providers Not Displayed in SQL Server Enterprise Manager After You Upgrade to Microsoft Data Access Components 2.7 (317059)
The information in this article applies to:
- Microsoft Data Access Components 2.7
This article was previously published under Q317059 SYMPTOMS
Certain tools, such as the SQL Server Enterprise Manager, may not display the Microsoft OLE DB Provider for OLAP Services and Microsoft OLE DB Provider for OLAP Services 8.0 in the list of providers after you upgrade to Microsoft Data Access Components 2.7 (MDAC).
CAUSE
In MDAC 2.7, the root enumerator component of the core OLE DB services code incorrectly enumerates the registry keys for the Microsoft OLE DB Provider for OLAP Services and Microsoft OLE DB Provider for OLAP Services 8.0.
Essentially, the root enumerator lists all of the OLE DB providers by searching each CLSID registry key for an OLE DB provider key, an OLE DB MD provider key, or an OLE DB enumerator key. If a CLSID registry key contains an OLE DB provider key, then the root enumerator lists the provider associated with that key as an OLE DB provider.
In MDAC 2.7, the root enumerator stops searching each CLSID registry key when the root enumerator encounters an OLE DB provider key, an OLE DB MD provider key, or an OLE DB enumerator key. The root enumerator ignores cases in which an OLE DB provider contains more than one of the three keys.
The MSOLAP providers contain both an OLE DB MD provider key and an OLE DB provider key. In the registry, the root enumerator finds the OLE DB MD provider key first and stops the search without locating the OLE DB provider key. Because the root enumerator does not find the OLE DB provider key, the Microsoft OLE DB Provider for OLAP Services and Microsoft OLE DB Provider for OLAP Services 8.0 are not included in the list of OLE DB providers.
RESOLUTION To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
The English-language version of this fix should have the following file attributes or later:
Date Time Version Size File name
--------------------------------------------------------------
17-Dec-2001 12:50 2.71.8217.0 421,888 Oledb32.dll
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 9/27/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbSQLServ2000sp3fix kbbug kbfix kbSQLServ2000preSP3fix KB317059 |
---|
|