December 8, 2009 at 2:02 am
We have a sql2000 server db. In our VB6 application we connect to this DB using this connectionstring :
Database=dbName;Server=serverName;Driver={SQL Server};UID=userName;PWD=password;Network=DBMSSOCN
This worked for years on all our clients (win2000). Since a few months they install vista on every client and since then we have a few clients who get an error when starting our application.
This is the error they receive :
Connection failed:
SQLState: 01000
SQL Server Error: 11001
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect())
Connection failed:
SQLState: 08001
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not found.
Not every client gets this error, most of them work without errors. So far only 3 pc's out of 100 get this error.
What can be the cause of this error ?
December 8, 2009 at 12:58 pm
Is the Windows Firewall turned on? I wonder if it is blocking port 1433 from connecting.
Joie Andrew
"Since 1982"
December 10, 2009 at 4:01 am
I'll have it checked. Does the firewall have to be set on every server or is this one firewall for the network ?
It's a very strange thing. Our different offices have each a server where the application is running on. Every client runs the application on the server of its location.
With the win2000 clients there are no problems.
With the vista clients we the problem, but only on 1 server, all the other servers are ok.
Running the application from a win2000 client on the server with the problem doesn't give any problem.
December 10, 2009 at 12:43 pm
I am not positive, since we have Windows Firewall disabled on our clients at work and depend on a hardware firewall for traffic in and out of our organization. I just mentioned it because I was not sure if Windows Firewall blocked port 1433 by default. I would imagine that would need to be opened on any computer wishing to talk to the database. So if the server is at least 2003, it would need to have the firewall opened for port 1433. Every client would probably also have to have that port enabled as well if they needed to connect to the server.
This is of course if it is using port 1433 (the default port for SQL server). If not, you will need to identify the port SQL is using and ensure that is open.
Joie Andrew
"Since 1982"
December 11, 2009 at 12:28 am
Windows firewall is disabled on all our clients.
Apparantly, after we get the error the application does work normally.
December 11, 2009 at 1:06 am
You can also check the client network utility on one of your clients and ensure that it is setup to conenct properly. I believe there is an area where you can check ODBC connection settings. If it still does not work, you can add an alias for the server to its IP address and try it again.
Joie Andrew
"Since 1982"
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply