Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: An Analysis Services server appears to stop responding when a complex query that takes a long time to complete is run against a SQL Server 2000 Analysis Services server
Article ID: 872934 - View products that this article applies to.
Bug #: 14363 (Plato7X)
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
This article describes the following about this hotfix release:
When a complex query that takes long time to complete is run against a Microsoft SQL Server 2000 Analysis Services server, and you try to connect to the Analysis Services server or you try to run a query against an Analysis Services cube, you may notice that the Analysis Services server appears to stop responding (hang). Additionally, you may notice a timeout error.
This problem causes a long delay for the processing of an object like a cube, a dimension, or a partition in the Analysis Services server to complete.
For a list of previous hotfixes, see the "Microsoft SQL Server 2000 post-Service Pack 3 or Microsoft SQL Server 2000 post-Service Pack 3a hotfixes" section in the following Microsoft Knowledge Base article:
(http://support.microsoft.com/kb/290211/ )How to obtain the most recent SQL Server 2000 service pack
When Analysis Services processes an object in an Analysis Services server, the server creates a copy of the object that is being processed and then operates on the copy until the Analysis Services server receives a commit request. When a commit request is received, the Analysis Services server obtains a write lock on the objects that are processed in the current transaction and then replaces those objects with the corresponding updated versions of the objects. If queries are running against one or more of the objects that are to be replaced, the write lock request waits for the existing read locks that are held by the queries. Any subsequent read lock requests that the Analysis Services server receives for the objects that are in the commit request are queued behind the waiting write lock request for the commit operation. This behavior causes the processing operation to wait until the query processing is complete. Therefore, you notice the behavior that is mentioned in the "Symptoms" section.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To resolve the problem, follow these steps:
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/290211/ )How to obtain the latest SQL Server 2000 service pack
(http://support.microsoft.com/kb/290211/ )How to obtain the latest SQL Server 2000 Service Pack
Note You must restart the MSSQLServerOLAPService service after you apply this hotfix.
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.
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Date Time Version Size File name ------------------------------------------------------- 06-Apr-2004 07:56 18,800 Msmd.h 29-Jul-2004 13:31 8.0.966.0 221,760 Msmdcb80.dll 29-Jul-2004 13:31 18.104.22.1686 4,063,808 Msmddo80.dll 29-Jul-2004 13:31 8.0.966.0 1,036,864 Msmdgd80.dll 29-Jul-2004 13:31 8.0.966.0 172,608 Msmdpump.dll 29-Jul-2004 07:16 8.0.966.0 446,524 Msmdsgn.rll 29-Jul-2004 13:31 22.214.171.1246 9,642,564 Msmdsgn80.dll 29-Jul-2004 13:31 8.0.966.0 1,843,780 Msmdsrv.exe 29-Jul-2004 13:31 8.0.966.0 2,085,456 Msolap80.dll 29-Jul-2004 06:57 8.0.966.0 213,068 Msolap80.rll
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/ )New naming schema for Microsoft SQL Server software update packages
(http://support.microsoft.com/kb/824684/LN/ )Description of the standard terminology that is used to describe Microsoft software updates