Article ID: 899025 - Last Review: November 21, 2006 - Revision: 2.3 FIX: The SQL Server 2000 Analysis Services process may stop accepting connections and may appear to stop responding when you stop a SQL Server transaction after that transaction requests a lockMicrosoft distributes Microsoft SQL Server 2000 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 2000 fix release. On This PageSUMMARYThis article describes the following about this hotfix release:
SYMPTOMSWhen you stop a SQL Server transaction after that transaction requests a lock, the SQL Server 2000 Analysis Services process may stop accepting connections and may appear to stop responding. For a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, click the following article number to view the article in the Microsoft Knowledge Base: 810185
(http://support.microsoft.com/kb/810185/
)
SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a
CAUSEBecause locks are frequently requested and released in Analysis Services, the server uses a pool of structures for lock request information. This approach streamlines lock request operations by reusing the lock request structures. The approach does not create and destroy the lock request structures on demand. If a transaction is aborted when a lock request is waiting, the lock request structure may be returned to the pool without being removed correctly from the lock waiter list. Another transaction may request a lock on the same object and may use the same lock request structure. In this case, the Analysis Services process detects that a request exists on the lock waiter list. Then, the Analysis Services process tries to insert the request at the end of the list. The current transaction has the same lock request structure as the transaction that is already on the lock waiter list. Therefore, the next pointer for the lock request structure on the waiter list points to itself. Any subsequent lock request on the object will enter an infinite loop when the Analysis Services process tries to insert the lock request in the lock waiter list. RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft SQL Server 2000 service pack that contains this hotfix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;%5Bln%5D;cntactms)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.Prerequisites
Restart informationYou do not have to restart the server after you apply this hotfix. The Analysis Services service is automatically stopped and restarted as part of the hotfix setup.Registry informationYou do not have to modify 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 2000 32-bit versions for SQL Server 2000 SP3Collapse this table
SQL Server 2000 32-bit versions for SQL Server 2000 SP4Collapse this table
SQL Server 2000 64-bit versions for SQL Server 2000 SP3Collapse this table
STATUSMicrosoft 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 Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages
For more information about the terminology that Microsoft uses when it corrects software after the software is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
| Article Translations
|

Back to the top
