OLE DB Connection without DSN
When writing a connection with a DSN using OLE DB provider a client is unable to locate SQL Server 2005 with a DBnetlib.dll error.
Upvotes: 1<=-=Dec 29 2005 8:08AM=-=>
To clarify the above statement: a connection without a DSN does not work, creating a DSN will work, and then once the DSN is deleted new connections continue to work even after client re-boots.<=-=Jan 4 2006 6:44AM=-=>
Here is an added error message that I’m wondering how to repair. On an Active Directory authenticated network I make a remote connection to xasid9546\ia_team using the SA account in Management Studio and receive this error: Cannot connect to xasid9546\ia_team additional info: a connection was successfully established with the server, but then an error occurred during the login process. (provider: Named Pipes Provider, error: 0 – No process is on the other end of the pipe.) (MS SQL Server, Error: 233)
However, I am able to connect to xasid9546\ia_team using Windows Authentication.<=-=Jan 4 2006 11:30AM=-=>
There is a fix to one error “0 – No process is on the other end of the pipe.” placing the SQL Server in Mixed Mode.
On another note, I have tested another provider, MSDASQL, and received the same [DBNETLIB] error message.<=-=Jan 4 2006 12:52PM=-=>
I have tested the ADODB connection errors on two workstations, with two providers on each, receiving the same error message with respect to the provider.
Using a MSDASQL provider the connection error is:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
Using a SQLOLEDB provider the connection error is:
[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied.
Can I ask you several questions?
1) What are the protocols enabled on the server? If TCP enabled, what�s the TCP port the server listening on?
2) Is your SQL browser running on the server box? To use TCP for this named instance, you must have SQL browser running to get the TCP port.
3) Do you have firewall on the server? If yes, please put both sql server and sql browser into exception list?
4) What�s the value for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib\ProtocolOrder?
You can also try to connect to the server using specific protocols (e.g. np, tcp). Take sometime to check your errorlog file as well, which will usually give you hints about your problem.
The following may explain your doubt about DSN:
When you create DSN, you connect to the server successfully. We will put a value here:
which will be used when you connect to the same data source later.
You should be able to see a value for �xasid9546\ia_team� here.
(or even here HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo, depends on whether you change the client configure)
Thanks,<=-=Jan 6 2006 5:53AM=-=>
I posted the work-around for this bug, so the problem is resolved with this Knowledge Base article that I found a couple of days ago: http://support.microsoft.com/?kbid=888228
In light of this information would you like your questions answered? Thank you,<=-=Jan 6 2006 10:28AM=-=>
OK. This is known issue.
Actually, the issue was an unknown issue to MS SQL Server 2005 on 06 JAN 06. The KB article noted above references a solution for a similar bug in MS SQL Server 2000 that was determined independently in early DEC 05.
Please consider testing my solution to see if it will work for MS SQL Server 2005 editions, if deemed necessary. Otherwise, thank you for your time.<=-=Jan 26 2006 11:08PM=-=>
Yes. I worked on that customer issue.
It has similar cause, i.e., SSRP UDP response packet get dropped. (by firewall or ipsec)