FIX: You receive an incorrect result when you execute a DISCOVER request or call the AdomdConnection.GetSchemaDataSet method against a SQL Server 2005 Analysis Services server (912446)
The information in this article applies to:
- Microsoft SQL Server 2005 Analysis Services
Bug#: 144 (SQL Hotfix)
NoticeMicrosoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.This article describes the following about this hotfix release: - The issues that are fixed by this hotfix package
- The prerequisites for installing the hotfix package
- Whether you must restart the computer after you install the hotfix package
- Whether the hotfix package is replaced by any other hotfix package
- Whether you must make any registry changes
- The files that are contained in the hotfix package
SYMPTOMSWhen you try to obtain information and metadata from a Microsoft SQL Server 2005 Analysis Services server by using one of the following methods, you receive an incorrect result: - You execute a DISCOVER request by using the MDSCHEMA_MEMBERS rowset in the RequestType tag and the restriction on the MEMBER_CAPTION restriction column in the Restrictions tag.
- You call the AdomdConnection.GetSchemaDataSet method by using the AdomdSchemaGuid.Members field to specify which schema information to return and by applying a restriction on the MEMBER_CAPTION restriction column to filter the information.
These methods return only the first member that matches the restrictions that you specify. These methods ignore the other members that match the restrictions. RESOLUTIONService pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005
Hotfix informationPrerequisitesTo apply this hotfix, you must have SQL Server 2005 Analysis Services installed on the computer.
Restart informationIf the installer must replace files that are being used, you must restart the computer. To avoid restarting the computer, close all the SQL Server Analysis Services tools and clients. Additionally, stop Microsoft Internet Information Services (IIS) if the server is configured to provide HTTP access. If you have installed SQL Server Analysis Services as a named instance, stop the SQL Server Browser service because the Msmdredir.dll component of the SQL Server Browser service is updated when you install the hotfix. Registry informationYou do not have to change the registry. Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of 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 2005 Analysis Services, 32-bit version|
Msmdlocal.dll | 9.0.1520.0 | 15,589,080 | 28-Jan-2006 | 04:54 | x86 | Msmdpump.dll | 9.0.1520.0 | 3,913,944 | 28-Jan-2006 | 04:54 | x86 | Msmdredir.dll | 9.0.1520.0 | 3,927,256 | 28-Jan-2006 | 04:54 | x86 | Msmdsrv.exe | 9.0.1520.0 | 14,567,128 | 28-Jan-2006 | 04:54 | x86 | Msmgdsrv.dll | 9.0.1520.0 | 5,935,832 | 28-Jan-2006 | 04:54 | x86 | Msolap90.dll | 9.0.1520.0 | 4,204,760 | 28-Jan-2006 | 04:54 | x86 |
SQL Server 2005 Analysis Services, 64-bit version|
Msmdlocal.dll | 9.0.1520.0 | 30,019,288 | 30-Jan-2006 | 05:24 | x64 | Msmdpump.dll | 9.0.1520.0 | 4,959,448 | 30-Jan-2006 | 05:24 | x64 | Msmdredir.dll | 9.0.1520.0 | 4,832,472 | 30-Jan-2006 | 05:24 | x64 | Msmdsrv.exe | 9.0.1520.0 | 29,343,960 | 30-Jan-2006 | 05:24 | x64 | Msmgdsrv.dll | 9.0.1520.0 | 8,910,040 | 30-Jan-2006 | 05:24 | x64 | Msolap90.dll | 9.0.1520.0 | 5,668,568 | 30-Jan-2006 | 05:24 | x64 |
SQL Server 2005 Analysis Services, Itanium architecture version|
Msmdlocal.dll | 9.0.1520.0 | 48,428,248 | 30-Jan-2006 | 06:52 | IA-64 | Msmdpump.dll | 9.0.1520.0 | 6,528,728 | 30-Jan-2006 | 06:52 | IA-64 | Msmdredir.dll | 9.0.1520.0 | 6,073,560 | 30-Jan-2006 | 06:52 | IA-64 | Msmdsrv.exe | 9.0.1520.0 | 47,461,592 | 30-Jan-2006 | 06:53 | IA-64 | Msmgdsrv.dll | 9.0.1520.0 | 12,842,200 | 30-Jan-2006 | 06:53 | IA-64 | Msolap90.dll | 9.0.1520.0 | 7,687,384 | 30-Jan-2006 | 06:52 | IA-64 |
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2005 Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
---|
Keywords: | kbsql2005sp1fix kbsql2005olapsp1fix kbsql2005presp1fix kbsql2005bi kbsql2005as kbfix KBSQLServ2005fix kbExpertiseAdvanced kbHotfixServer kbQFE kbpubtypekc KB912446 kbAudDeveloper kbAudITPRO |
---|
|