Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/247641

From BetaArchive Wiki
Knowledge Base

Article ID: 247641

Article Last Modified on 3/14/2006


  • Microsoft SQL Server 7.0 Standard Edition

This article was previously published under Q247641

BUG #: 56445 (SQLBUG_70)


Under certain situations, a client may fail to connect to SQL Server 7.0 when using TCP/IP sockets and Microsoft Windows NT authentication (trusted connection), and the following error message is displayed:

Error 18452: Login failed for user 'null'. Reason: Not associated with a trusted SQL Server connection.

When using full-text search, the error message displayed is as follows:

Server: Msg 7619, Level 16, State 1, Line 1 Access is denied.

Typically, after this error message occurs, no other clients can make new connections until SQL Server is restarted. Both TCP/IP sockets and Multi-Protocol clients may experience this problem. Named pipes clients are not affected.


This problem is more likely to occur when both Multi-Protocol and TCP/IP sockets trusted connections are attempted from the same client computer. Connection stress also makes the problem more likely to occur.


Use one of the following workarounds:

  • Use trusted connections over named pipes where appropriate.
  • Disable multiprotocol for SQL Server using the Server Network Utility.


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

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

For more information, contact your primary support provider.


This same error message may occur under normal SQL Server operations when many simultaneous trusted connections are attempted through TCP/IP sockets. This is due to the server and network being too busy, causing SSPI communication timeout, which in turn causes trusted connection timeouts. However, these intermittent connection timeouts will not affect SQL Server accepting new connections, and should not be a cause for concern.

Additional query words: integrated security RPC

Keywords: kbbug kbfix KB247641