Microsoft KB Archive/258087: Difference between revisions

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
(2 intermediate revisions by the same user not shown)
Line 52: Line 52:
<div class="errormessage">
<div class="errormessage">


<pre class="fixed_text">SQL Server Assertion: File: &lt;xcbmgr.cpp&gt;, line=1299 Failed Assertion = 'pss-&gt;IsXcbLocked ()'.
<pre class="fixed_text">SQL Server Assertion: File: <xcbmgr.cpp>, line=1299 Failed Assertion = 'pss->IsXcbLocked ()'.
                     </pre>
                     </pre>


Line 77: Line 77:
== MORE INFORMATION ==
== MORE INFORMATION ==


This problem occurs only for non-admin users and only if a transaction is currently active. When the server accepts a T-SQL batch (language_exec) or the '''execrpc''' remote stored procedure call (RPC), a check is made to see if the server is in a shutdown process. If so, and the user is a non-admin user, then a 6002 message &quot;SHUTDOWN is in progress. Log off&quot; is sent back to the client. In the case of a batch, certain types of exception handling logic is also executed which, if the transaction is active, may lead to this assertion.<br />
This problem occurs only for non-admin users and only if a transaction is currently active. When the server accepts a T-SQL batch (language_exec) or the '''execrpc''' remote stored procedure call (RPC), a check is made to see if the server is in a shutdown process. If so, and the user is a non-admin user, then a 6002 message "SHUTDOWN is in progress. Log off" is sent back to the client. In the case of a batch, certain types of exception handling logic is also executed which, if the transaction is active, may lead to this assertion.<br />
<br />
<br />
The problem is benign as the server is already shutting down. No transactional integrity is compromised because of this assertion. Depending on the timing of the problem, there may be some cases where a shutdown message does not appear in the errorlog.<br />
The problem is benign as the server is already shutting down. No transactional integrity is compromised because of this assertion. Depending on the timing of the problem, there may be some cases where a shutdown message does not appear in the errorlog.<br />

Latest revision as of 13:54, 21 July 2020

Knowledge Base


FIX: Non-Admin User That Executes Batch While Server Shuts Down May Encounter Retail Assertion

Article ID: 258087

Article Last Modified on 3/14/2006



APPLIES TO

  • Microsoft SQL Server 7.0 Standard Edition



This article was previously published under Q258087

BUG #: 57532 (SQLBUG_70)

SYMPTOMS

A non-admin user may encounter the following retail assertion when executing a T-SQL batch during a shutdown of SQL Server.

SQL Server Assertion: File: <xcbmgr.cpp>, line=1299 Failed Assertion = 'pss->IsXcbLocked ()'.
                    

Because this problem only occurs when the server is already shutting down, the assertion is a benign error and does not affect transactional integrity.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0


For more information, contact your primary support provider.

MORE INFORMATION

This problem occurs only for non-admin users and only if a transaction is currently active. When the server accepts a T-SQL batch (language_exec) or the execrpc remote stored procedure call (RPC), a check is made to see if the server is in a shutdown process. If so, and the user is a non-admin user, then a 6002 message "SHUTDOWN is in progress. Log off" is sent back to the client. In the case of a batch, certain types of exception handling logic is also executed which, if the transaction is active, may lead to this assertion.

The problem is benign as the server is already shutting down. No transactional integrity is compromised because of this assertion. Depending on the timing of the problem, there may be some cases where a shutdown message does not appear in the errorlog.


Keywords: kbbug kbfix kbqfe KB258087