Microsoft KB Archive/938750

From BetaArchive Wiki

Article ID: 938750

Article Last Modified on 10/12/2007



APPLIES TO

  • Microsoft SQL Server 2005 Analysis Services



Bug #: 50001235 (SQL Hotfix)

Microsoft 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 the hotfix package
  • The prerequisites for applying the hotfix package
  • Whether you must restart the computer after you apply the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes after you apply the hotfix package
  • The files that are contained in the hotfix package


SYMPTOMS

Consider the following scenario:

  • You run a Multidimensional Expressions (MDX) query against an instance of Microsoft SQL Server 2005 Analysis Services.
  • The query has been running for a long time. For example, the MDX query has been running for 5 minutes.
  • You cancel the MDX query before it returns the result.

In this scenario, you may experience the following problems:

  • The instance of SQL Server 2005 Analysis Services does not respond to any request from the current connection.
  • When you try to connect to the instance of SQL Server 2005 Analysis Services, you receive the following error message:

    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond (System)

This problem occurs if the MDX query queries a distinct count measure.

CAUSE

This problem occurs because a thread for the query does not correctly receive the notification when you cancel the query. SQL Server 2005 Analysis Services does not remove the locks that the query holds. Therefore, a block exists in the SQL Server lock manager.

RESOLUTION

Cumulative update information

To resolve this problem, install Microsoft SQL Server 2005 Service Pack 2 (SP2). Then, install the cumulative update package (build 3175) for SQL Server 2005 SP2.

For more information about how to obtain SQL Server 2005 Service Pack 2, 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


For more information, click the following article number to view the article in the Microsoft Knowledge Base:

936305 Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available


Hotfix information

Note This hotfix is included in the cumulative update package (build 3175) for SQL Server 2005 SP2.

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

You must have SQL Server 2005 SP2 installed to apply this hotfix.

Restart information

You do not have to restart the computer.

Registry information

You do not have to change the registry.

Hotfix 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 item in Control Panel.

SQL Server 2005 Analysis Services, 32-bit version
File name File version File size Date Time Platform
Microsoft.analysisservices.dll 9.0.3175.0 1,217,904 14-Jun-2007 15:05 x86
Microsoft.datawarehouse.dll 9.0.3175.0 1,279,344 14-Jun-2007 15:05 x86
Msadomdx.dll 9.0.3175.0 502,640 14-Jun-2007 15:05 x86
Msmdlocal.dll 9.0.3175.0 15,948,144 14-Jun-2007 14:05 x86
Msmdlocal.dll 9.0.3175.0 15,948,144 14-Jun-2007 15:05 x86
Msmdspdm.dll 9.0.3175.0 202,096 14-Jun-2007 15:05 x86
Msmdsrv.exe 9.0.3175.0 14,916,464 14-Jun-2007 15:05 x86
Msmgdsrv.dll 9.0.3175.0 6,045,552 14-Jun-2007 14:05 x86
Msmgdsrv.dll 9.0.3175.0 6,045,552 14-Jun-2007 15:05 x86
Msolap90.dll 9.0.3175.0 4,299,120 14-Jun-2007 14:05 x86
SQL Server 2005 Analysis Services, x64-based version
File name File version File size Date Time Platform
Microsoft.analysisservices.dll 9.0.3175.0 1,217,904 14-Jun-2007 14:05 x86
Microsoft.datawarehouse.dll 9.0.3175.0 1,279,344 14-Jun-2007 14:05 x86
Msadomdx.dll 9.0.3175.0 502,640 14-Jun-2007 14:05 x86
Msmdlocal.dll 9.0.3175.0 15,948,144 14-Jun-2007 14:05 x86
Msmdlocal.dll 9.0.3175.0 32,184,688 14-Jun-2007 16:41 x64
Msmdspdm.dll 9.0.3175.0 202,096 14-Jun-2007 16:41 x86
Msmdsrv.exe 9.0.3175.0 31,573,360 14-Jun-2007 16:41 x64
Msmgdsrv.dll 9.0.3175.0 6,045,552 14-Jun-2007 14:05 x86
Msmgdsrv.dll 9.0.3175.0 9,803,120 14-Jun-2007 16:41 x64
Msolap90.dll 9.0.3175.0 4,299,120 14-Jun-2007 14:05 x86
Msolap90.dll 9.0.3175.0 5,928,816 14-Jun-2007 16:41 x64
SQL Server 2005 Analysis Services, Itanium architecture version
File name File version File size Date Time Platform
Microsoft.analysisservices.dll 9.0.3175.0 1,217,904 14-Jun-2007 15:05 x86
Microsoft.datawarehouse.dll 9.0.3175.0 1,279,344 14-Jun-2007 15:05 x86
Msadomdx.dll 9.0.3175.0 502,640 14-Jun-2007 15:05 x86
Msmdlocal.dll 9.0.3175.0 15,948,144 14-Jun-2007 14:05 x86
Msmdlocal.dll 9.0.3175.0 49,904,496 14-Jun-2007 19:56 IA-64
Msmdspdm.dll 9.0.3175.0 202,096 14-Jun-2007 19:56 x86
Msmdsrv.exe 9.0.3175.0 48,855,408 14-Jun-2007 19:56 IA-64
Msmgdsrv.dll 9.0.3175.0 6,045,552 14-Jun-2007 14:05 x86
Msmgdsrv.dll 9.0.3175.0 13,169,008 14-Jun-2007 19:56 IA-64
Msolap90.dll 9.0.3175.0 4,299,120 14-Jun-2007 14:05 x86
Msolap90.dll 9.0.3175.0 7,908,720 14-Jun-2007 19:56 IA-64


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

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 software update terminology, 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


Keywords: kbsql2005as kbsql2005bi kbhotfixserver kbexpertiseadvanced kbqfe kbfix KB938750