The information in this article applies to:
BUG# NT: 12636 (4.21a) SYMPTOMS
The SQL Server Banyan network library can cause a CPU spin on SQL Server
version 4.21a or an unhandled exception in SQL Server version 6.0 if
it receives an unexpected Vines IPC message from any Banyan client.
CAUSE
When SQL Server's Banyan SPP socket receives an IPC message, it tries to
"flush" it. However, in 4.21a, when we try to discard the message, one of
the parameters we use with VnsSocketReceive to flush this message is
SO_CREC and this, as documented by Banyan, is supported only by the SPP
service. Because we are dealing with an IPC message, not SPP data, we are
unable to flush this message and thus caught in a loop trying repeatedly to
flush the same IPC message.
WORKAROUND
Use other SQL Server net libraries, such as TCP/IP sockets or Named Pipes.
There is no other known workaround for this problem.
STATUSMicrosoft has confirmed this to be a problem in Microsoft SQL Server versions 4.21a and 6.0. This problem was corrected in a hot fix release. Contact your primary support provider to obtain the hot fix or for more information. MORE INFORMATION
SQL Server uses the connection-oriented SPP service provided by the Vines
Transport Layer to communicate with any Banyan network clients. Once this
SPP socket is opened by SQL Server, it can theoretically be used for Vines'
IPC communication also.
Additional query words: sql6 Banyan Vines CPU SPIN hotfix
Keywords : kb3rdparty kbinterop kbnetwork SSrvLAN SSrvNet_Lib kbbug4.21a |
Last Reviewed: March 23, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |