Fixed the problem by doing the following: Opened SQL Server Configuration Manager and went to Protocols for MSSQLSERVER -> TCP/IP. In the 'IP Addresses' tab, I noticed that IP2 which has address of 127.0.0.1 was active but not enabled. Changed to enabled and restarted SQL services.My VB script now successfully opens the connection to 127.0.0.1.
It could fail if the database is not configured to listen to TCP/IP traffic. The error "Named Pipes Provider, error: 0 - No process is on the other end of the pipe. " points in that direction.
You can test that with: telnet 127.0.0.1 1433 To configure where the server listens, use `SQL Server Network Utility" for SQL Server 2000, or "SQL Server Surface Area Configuration" for SQL Server 2005 and up.
Ok I've done the telnet test and it failed, could not connect on port 1433. The servers are using SQL Server 2005, I've opened SQL Server Surface Area Configuration but can you please advise where I go to configure where the server listens? – VBscripter Dec 7 '09 at 6:25 @VBScripter: click on Surface Area Configuration for Services and Connections, then MSSQLSERVER -> Database Engine -> Remote Connections, and make sure one of the options with TCP/IP is selected – Andomar Dec 7 '09 at 6:55 'local and remote connections' and 'Using both TCP/IP and named pipes' are selected, yet I still can't connect to 127.0.0.1 through management studio or telnet to 127.0.0.1 on port 1433.
– VBscripter Dec 7 '09 at 6:59 @VBScripter: Check the logs for a line that looks like "SQL server listening on : " (should be near startup) and verify that it's listening on port 1433? – Andomar Dec 7 '09 at 11:14 I think I may have found the problem. I opened SQL Server Configuration Manager and went to Protocols for MSSQLSERVER -> TCP/IP.In the 'IP Addresses' tab, I noticed that IP2 which has address of 127.0.0.1 was active but not enabled.
It appears to be both active and enabled on the servers that are working. However, this change requires restart of SQL services, so I'll have to wait until after hours to test. – VBscripter Dec 7 '097 at 0:12.
It's not a database error, but a client tools or config error The failing servers will probably: have a different level of either SQL Server install /includes service pack) are configured for Windows Authentication only have an older MDAC (linked to SQL Service pack, OS Service pack etc) Edit: SQL Server SSL Encryption, server side, is described here. And in KB 316898 too "Server side" requires only a server certificate and all connections are encrypted "client side" requires client certs and is optional, and only for that client Certain client libraries (notably MS JDBC) do not support this. If I've guessed right, you'll have either client or server SSL encryption set based on the server (your script is acting as a client) a blog entry too.
All servers have Windows 2003 R2 x64 SP2. All servers are using SQL Server 9.0.3042 64 bit. This includes the succeeding and failing servers.
I have double checked the failing servers just to make sure. I'm not sure how to check MDAC version. I've just noticed that on the failing servers, when opening SQL Server Management Studio, I can't connect to 127.0.0.1, I have to connect to the server name.
However on every other server I can connect to 127.0.0.1. – VBscripter Dec 7 '09 at 5:50 This is the error when trying to connect to 127.0.0.1 on the failing servers through Management Studio: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.(provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233) – VBscripter Dec 7 '09 at 5:53 @VBScripter: can you ping 127.0.0.1?
Are these server configured for encrpytion? – gbn Dec 7 '09 at 7:09 yes I can ping 127.0.0.1, and the windows firewall is disabled. Can you please be more specific about your encryption question?
– VBscripter Dec 7 '09 at 7:13.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.