Microsoft KB Archive/214639

= FIX: Multi-Protocol Encrypted Connection Fails with Error 1749 =

Article ID: 214639

Article Last Modified on 3/14/2006

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q214639



BUG #: 18204 (SQLBUG_65)



SYMPTOMS
To set a Multi-Protocol Net-Library to establish an encrypted connection with SQL Server for all users accessing a SQL Server, you define a Windows NT account name and password in the Multi-Protocol connection string.

Such a connection may result in the following error in the SQL Client Configuration Utility on the computer running the client application:

Unable to connect. SQL Server is unavailable or does not exist. General network error. Check your documentation.

OS Error: 1749 ConnectionOpen(RpcBindingSetAuthInfo).



CAUSE
OS error 1749 means "the security context is invalid".

The Net-Library for Multi-Protocol (DBmsRPCn.dll) does not correctly tranmit the user name and password for authentication to the Windows NT Server computer.



WORKAROUND
To work around this problem, create an account on the Windows NT Server computer for each client using Multi-Protocol and do not specify a user name and password in the client utility.



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

197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a

For more information, contact your primary support provider.

Additional query words: multiprotocol netlib net libs netlibs net-lib lib username machine acct

Keywords: kbbug kbfix KB214639

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.