Connections, using ODBC (version 3.520) and from a couple web apps, to one of
my SQL Server 2000 systems (with SP3) had been fine until a couple days ago.
Suddenly some of my systems (but not all) are unable to connect to that one
server. The message when ODBC attempts to login into the SQL Server is:
Connection failed:
SQLState: '01000', SQL Server Error: 11001, [TCP/IP Sockets]ConnectionOpen
(Connect())
SQLState: '08001', SQL Server Error: 6, [TCP/IP Sockets]Specified SQL Server
not found
My web apps (including a web service) display a similar (though abbreviated)
message when the user is trying to connect to the SQL server to
login/authenticate.
From that same system that can't get to the first SQL Server, I can use ODBC
to connect to a different SQL Server with no trouble. I've tried Named Pipes
with no success. Enterprise Manager connects fine from other systems. I am
certain that MDAC 2.8 has been installed on all systems but, regardless, I
hadn't done any Windows updates on any systems for at least a week and no
MDAC/ODBC updates for a couple months.
What can I check or fix?
Thanks.
Jon
jlimmer@.gmbeverage.com
On the surface it sounds like a name resoultion problem. What happens if
you ping the SQL Server name from the web server. Does it return? Als try
ping -a <ip address of the SQL Server machine>. Does it return the correct
server name?
Can you connect from a DSN using the ip address of the SQL Server as the
server name?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Very interesting, Rand.
I can ping the SQL server both using the server name and using the -a switch
(which does resolve the server name).
I also can sucessfully use the IP address in the SQL Server instance name in
the DSN to connect.
So, what does that indicate is the problem, if DNS is working?
Jon
Showing posts with label sockets. Show all posts
Showing posts with label sockets. Show all posts
Tuesday, March 20, 2012
[TCP/IP Sockets] Specified SQL Server not found
Connections, using ODBC (version 3.520) and from a couple web apps, to one o
f
my SQL Server 2000 systems (with SP3) had been fine until a couple days ago.
Suddenly some of my systems (but not all) are unable to connect to that one
server. The message when ODBC attempts to login into the SQL Server is:
Connection failed:
SQLState: '01000', SQL Server Error: 11001, [TCP/IP Sockets]ConnectionOp
en
(Connect())
SQLState: '08001', SQL Server Error: 6, [TCP/IP Sockets]Specified SQL Se
rver
not found
My web apps (including a web service) display a similar (though abbreviated)
message when the user is trying to connect to the SQL server to
login/authenticate.
From that same system that can't get to the first SQL Server, I can use ODBC
to connect to a different SQL Server with no trouble. I've tried Named Pipe
s
with no success. Enterprise Manager connects fine from other systems. I am
certain that MDAC 2.8 has been installed on all systems but, regardless, I
hadn't done any Windows updates on any systems for at least a week and no
MDAC/ODBC updates for a couple months.
What can I check or fix?
Thanks.
Jon
jlimmer@.gmbeverage.comOn the surface it sounds like a name resoultion problem. What happens if
you ping the SQL Server name from the web server. Does it return? Als try
ping -a <ip address of the SQL Server machine>. Does it return the correct
server name?
Can you connect from a DSN using the ip address of the SQL Server as the
server name?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Very interesting, Rand.
I can ping the SQL server both using the server name and using the -a switch
(which does resolve the server name).
I also can sucessfully use the IP address in the SQL Server instance name in
the DSN to connect.
So, what does that indicate is the problem, if DNS is working?
Jon
f
my SQL Server 2000 systems (with SP3) had been fine until a couple days ago.
Suddenly some of my systems (but not all) are unable to connect to that one
server. The message when ODBC attempts to login into the SQL Server is:
Connection failed:
SQLState: '01000', SQL Server Error: 11001, [TCP/IP Sockets]ConnectionOp
en
(Connect())
SQLState: '08001', SQL Server Error: 6, [TCP/IP Sockets]Specified SQL Se
rver
not found
My web apps (including a web service) display a similar (though abbreviated)
message when the user is trying to connect to the SQL server to
login/authenticate.
From that same system that can't get to the first SQL Server, I can use ODBC
to connect to a different SQL Server with no trouble. I've tried Named Pipe
s
with no success. Enterprise Manager connects fine from other systems. I am
certain that MDAC 2.8 has been installed on all systems but, regardless, I
hadn't done any Windows updates on any systems for at least a week and no
MDAC/ODBC updates for a couple months.
What can I check or fix?
Thanks.
Jon
jlimmer@.gmbeverage.comOn the surface it sounds like a name resoultion problem. What happens if
you ping the SQL Server name from the web server. Does it return? Als try
ping -a <ip address of the SQL Server machine>. Does it return the correct
server name?
Can you connect from a DSN using the ip address of the SQL Server as the
server name?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Very interesting, Rand.
I can ping the SQL server both using the server name and using the -a switch
(which does resolve the server name).
I also can sucessfully use the IP address in the SQL Server instance name in
the DSN to connect.
So, what does that indicate is the problem, if DNS is working?
Jon
Thursday, March 8, 2012
[ODBC SQL Server Driver][TCP/IP Sockets] ConnectionRead (recv())
Hi,
I have developed socket on VB using wsock32.dll, which connects to the data from AS400. This data is then stored in SQL server. MTS is uset to handle the dll objects.
During the process of insertion system returns an error
[ODBC SQL Server Driver][TCP/IP Sockets] ConnectionRead (recv())
[ODBC SQL Server Driver][TCP/IP Sockets] General Network Error
After this error, system does not connect to SQL server and to AS400, until the MS DTC service on MTS is stopped and restarted.
Please help on this.
Note:
I have introduced a trace in each ster to analyze at what point error is happening. I found out that system is not giving problem while opening a connection to SQL server, it only gives an error while inserting the records in SQL server. I think, there might be problem with the locking machanism.
I will appericiate your helps, mean while I try to solve the problem related to locking.
regardsIs there some reason that you didn't want to use DTS packages for this? DTS does quite well connecting to our AS/400 (though it took a bit of configuration).
Regards,
Hugh Scott
Originally posted by attinder
Hi,
I have developed socket on VB using wsock32.dll, which connects to the data from AS400. This data is then stored in SQL server. MTS is uset to handle the dll objects.
During the process of insertion system returns an error
[ODBC SQL Server Driver][TCP/IP Sockets] ConnectionRead (recv())
[ODBC SQL Server Driver][TCP/IP Sockets] General Network Error
After this error, system does not connect to SQL server and to AS400, until the MS DTC service on MTS is stopped and restarted.
Please help on this.
Note:
I have introduced a trace in each ster to analyze at what point error is happening. I found out that system is not giving problem while opening a connection to SQL server, it only gives an error while inserting the records in SQL server. I think, there might be problem with the locking machanism.
I will appericiate your helps, mean while I try to solve the problem related to locking.
regards|||We might have used DTS but we are using the same socket with different applications. They may or may not use SQL server|||Hi Hugh,
You indicated that connecting to AS 400 requires quite a bit of configuration. Can you please elaborate on this point? I need it urgently.
Thanks
Originally posted by hmscott
Is there some reason that you didn't want to use DTS packages for this? DTS does quite well connecting to our AS/400 (though it took a bit of configuration).
Regards,
Hugh Scott|||Okay, here is what I remember:
1. We used the IBM Client Access Express drivers. We are using V5R1M0 with SP SI02795. The SP is critical, since there is a bug in the original release which won't let you connect to a database w/ more than 9 characters in the name (thanks IBM!).
2. The main hassle is that the driver always prompts you for a user name/password unless you config it appropriately. The prompt is not visible when the DTS package runs as a job (since it appears on the virtual desktop of the SQL Agent service account).
If that doesn't make sense to you, stop. Read up on SQL Service accounts and make sure that SQL Agent is set up to run under a service account.
3. Okay, proceeding ahead:
a. The SQL Agent account must be set up with 10 characters or less (SQLAdmin is okay, SQLAgentAccount is not).
b. Set up an account on the AS/400 with the same name as the SQL Agent account.
c. Set the password for both accounts to be identical (and again, no more than 10 characters)
4. Use the ODBC Administration GUI to set up a new connection. Specify that the connection should use the Windows user name/account information. It is helpful to do this set up while logged in as the SQL Agent Service account. It's not critical, but it is helpful.
Some additional notes:
1. We are using MS W2K SP4 (Advanced)
2. We are using MS SQL 2K (SP3a + MS03-031)
3. To verifiy that you have everything working correctly, log in to the server as the SQL Service account. Open a DTS package. Create a connection object for the AS/400. Create a destination connection object. Add a data pump task. When you specify the details of the data pump task, you should never be prompted for the password.
Alternatively: A friend of mine has had good success with the Hit Software OLE DB drivers for AS/400. I have never used them/don't know anything about them. But they may be worth trying. www.hitsw.com.
HTH,
hmscott
I have developed socket on VB using wsock32.dll, which connects to the data from AS400. This data is then stored in SQL server. MTS is uset to handle the dll objects.
During the process of insertion system returns an error
[ODBC SQL Server Driver][TCP/IP Sockets] ConnectionRead (recv())
[ODBC SQL Server Driver][TCP/IP Sockets] General Network Error
After this error, system does not connect to SQL server and to AS400, until the MS DTC service on MTS is stopped and restarted.
Please help on this.
Note:
I have introduced a trace in each ster to analyze at what point error is happening. I found out that system is not giving problem while opening a connection to SQL server, it only gives an error while inserting the records in SQL server. I think, there might be problem with the locking machanism.
I will appericiate your helps, mean while I try to solve the problem related to locking.
regardsIs there some reason that you didn't want to use DTS packages for this? DTS does quite well connecting to our AS/400 (though it took a bit of configuration).
Regards,
Hugh Scott
Originally posted by attinder
Hi,
I have developed socket on VB using wsock32.dll, which connects to the data from AS400. This data is then stored in SQL server. MTS is uset to handle the dll objects.
During the process of insertion system returns an error
[ODBC SQL Server Driver][TCP/IP Sockets] ConnectionRead (recv())
[ODBC SQL Server Driver][TCP/IP Sockets] General Network Error
After this error, system does not connect to SQL server and to AS400, until the MS DTC service on MTS is stopped and restarted.
Please help on this.
Note:
I have introduced a trace in each ster to analyze at what point error is happening. I found out that system is not giving problem while opening a connection to SQL server, it only gives an error while inserting the records in SQL server. I think, there might be problem with the locking machanism.
I will appericiate your helps, mean while I try to solve the problem related to locking.
regards|||We might have used DTS but we are using the same socket with different applications. They may or may not use SQL server|||Hi Hugh,
You indicated that connecting to AS 400 requires quite a bit of configuration. Can you please elaborate on this point? I need it urgently.
Thanks
Originally posted by hmscott
Is there some reason that you didn't want to use DTS packages for this? DTS does quite well connecting to our AS/400 (though it took a bit of configuration).
Regards,
Hugh Scott|||Okay, here is what I remember:
1. We used the IBM Client Access Express drivers. We are using V5R1M0 with SP SI02795. The SP is critical, since there is a bug in the original release which won't let you connect to a database w/ more than 9 characters in the name (thanks IBM!).
2. The main hassle is that the driver always prompts you for a user name/password unless you config it appropriately. The prompt is not visible when the DTS package runs as a job (since it appears on the virtual desktop of the SQL Agent service account).
If that doesn't make sense to you, stop. Read up on SQL Service accounts and make sure that SQL Agent is set up to run under a service account.
3. Okay, proceeding ahead:
a. The SQL Agent account must be set up with 10 characters or less (SQLAdmin is okay, SQLAgentAccount is not).
b. Set up an account on the AS/400 with the same name as the SQL Agent account.
c. Set the password for both accounts to be identical (and again, no more than 10 characters)
4. Use the ODBC Administration GUI to set up a new connection. Specify that the connection should use the Windows user name/account information. It is helpful to do this set up while logged in as the SQL Agent Service account. It's not critical, but it is helpful.
Some additional notes:
1. We are using MS W2K SP4 (Advanced)
2. We are using MS SQL 2K (SP3a + MS03-031)
3. To verifiy that you have everything working correctly, log in to the server as the SQL Service account. Open a DTS package. Create a connection object for the AS/400. Create a destination connection object. Add a data pump task. When you specify the details of the data pump task, you should never be prompted for the password.
Alternatively: A friend of mine has had good success with the Hit Software OLE DB drivers for AS/400. I have never used them/don't know anything about them. But they may be worth trying. www.hitsw.com.
HTH,
hmscott
Subscribe to:
Posts (Atom)