Some of my clients cannot access an application, and it seems there is
a communication issue(?). The application server is a bit slow, the
database server (MS SQL Server 2000, SQL SP4) is brand new and fast.
Users that have the problem are behind a firewall that allows
everything from the client network to the server network. I have
configured the ODBC DSN, tested it, and the test succeeds. When
starting the application however, they get an error, [Microsoft][ODB
C
SQL Server Driver]Timeout expired. I have traced the startup, and the
log file is pasted below:
Vbus 100-938 ENTER SQLAllocEnv
HENV * 013FC478
Vbus 100-938 EXIT SQLAllocEnv with return code 0
(SQL_SUCCESS)
HENV * 0x013FC478 ( 0x02031540)
Vbus 100-938 ENTER SQLAllocConnect
HENV 02031540
HDBC * 01AC4ED0
Vbus 100-938 EXIT SQLAllocConnect with return code 0
(SQL_SUCCESS)
HENV 02031540
HDBC * 0x01AC4ED0 ( 0x020315e8)
Vbus 100-938 ENTER SQLDriverConnectW
HDBC 020315E8
HWND 001902C6
WCHAR * 0x74329A38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x74329A38
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
Vbus 100-938 EXIT SQLDriverConnectW with return code -1
(SQL_ERROR)
HDBC 020315E8
HWND 001902C6
WCHAR * 0x74329A38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x74329A38
SWORD 2
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
DIAG [S1T00] [Microsoft][ODBC SQL Server Driver]Timeout expired
(0)
Vbus 100-938 ENTER SQLErrorW
HENV 02031540
HDBC 020315E8
HSTMT 00000000
WCHAR * 0x00208B48 (NYI)
SDWORD * 0x01AC4EDC
WCHAR * 0x00208748
SWORD 512
SWORD * 0x0020F08C
Vbus 100-938 EXIT SQLErrorW with return code 0
(SQL_SUCCESS)
HENV 02031540
HDBC 020315E8
HSTMT 00000000
WCHAR * 0x00208B48 (NYI)
SDWORD * 0x01AC4EDC (0)
WCHAR * 0x00208748 [ 50] "[Microsoft][ODBC SQL
Server Driver]Timeout expired"
SWORD 512
SWORD * 0x0020F08C (50)
It seems that the SQLDriverConnectW is what generates the error, but I
am not a database administrator, nor developer, and knows nothing about
what it is or means.
The ODBC-driver (odbc32.dll) version on the machines that get this
error, is identical to those that don't.
Can anyone interpret this trace for me? What goes on, what is the
ODBC-driver (or anything else) complaining about? Would be highly
appreciated!
Bjorn Henrik Formo.Any luck on this issue. I am running into the same error. The ODBC test
connects fine but from my application I cannot.
-Markus
markusr
---
markusr's Profile: http://www.dbtalk.net/m568
View this thread: http://www.dbtalk.net/t169537
Showing posts with label isa. Show all posts
Showing posts with label isa. Show all posts
Friday, March 9, 2012
Monday, February 20, 2012
ODBC failing to connect
Ok here is the problem. I am trying to set up logging on SQL 2005. Now I
am trying to setup the OBDC on the ISA server and it is failing each time.
It cannot reach the server. Every other computer in the domain can access
the SQL server via OBDC. So what am I missing to do that on the ISA server.
I am running ISA 2006 Enterprise, and have set the system policy to use SQL
for logging. Plus I have a access rule that allows SQL through ISA. Anyone
know what I missed?
TCP/IP is set up as dynamic, and I can ping the SQL Server.
The following is the failure I get from ODBC:
Connection failed:
SQLState: '01000'
SQL Server Error: 10065
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection Failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist
or access denied.
Thanks,
Michael R. Mastro II
It can be a lot of different things. Enable login auditing
or run profiler to see if it's actually connecting on the
SQL Server end. It just makes troubleshooting easier.
If it's a named instance, make sure you are specifying the
instance name.
You'd also want to check your ports and protocols - one way
to check is look in the SQL Server error log from when it
started up to determine what ports and protocols SQL Server
is listening on.
From the ISA server, try to telnet to the port SQL Server is
listening on. Make sure the client end (ISA) is using the
same port.
Make sure SQL Server is listening on the correct protocols
as well. Make sure you have TCP/IP enabled.
And then run through the following article:
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306
-Sue
On Tue, 23 Jan 2007 10:03:10 -0500, "Michael Mastro"
<MikeRM2XXX@.worldnet.att.net> wrote:
>Ok here is the problem. I am trying to set up logging on SQL 2005. Now I
>am trying to setup the OBDC on the ISA server and it is failing each time.
>It cannot reach the server. Every other computer in the domain can access
>the SQL server via OBDC. So what am I missing to do that on the ISA server.
>I am running ISA 2006 Enterprise, and have set the system policy to use SQL
>for logging. Plus I have a access rule that allows SQL through ISA. Anyone
>know what I missed?
>TCP/IP is set up as dynamic, and I can ping the SQL Server.
>The following is the failure I get from ODBC:
>Connection failed:
>SQLState: '01000'
>SQL Server Error: 10065
>[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
>(Connect()).
>Connection Failed:
>SQLState: '08001'
>SQL Server Error: 17
>[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist
>or access denied.
>
>Thanks,
>Michael R. Mastro II
>
|||I tried the following with still no luck.
First off I went into the SQL Server logs and found out that it is listening
in on TCP port 2440, it also mentioned 2441.
I then went to the ISA server and created protocol that allows inbound and
outbound connections on 1433, 2440, and 2441. I created an access rule that
allows any of the protected networks and the local host to access the new
protocol I created with the SQL server.
I went back to the SQL server machine, and started up the profiler to run a
trace.
Back to the ISA machine, and opened up telnet and tried to connect to SQL
server machine via 1433, then 2440, then 2441. Each time connect failed. I
also tried a static IP on the ODBC set for 2440. And each time as the same
before.
I looked over the SQL Profiler trace and it does not even show any
connection attempts from the ISA machine.
Pinging and PathPinging show good connections. Plus a looking over the
ports on the SQL server machine show that it is listening on those ports.
Still scratching my head.
Michael R. Mastro II
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:iejdr215njd7fp0taafif3lcsdb508i420@.4ax.com...
> It can be a lot of different things. Enable login auditing
> or run profiler to see if it's actually connecting on the
> SQL Server end. It just makes troubleshooting easier.
> If it's a named instance, make sure you are specifying the
> instance name.
> You'd also want to check your ports and protocols - one way
> to check is look in the SQL Server error log from when it
> started up to determine what ports and protocols SQL Server
> is listening on.
> From the ISA server, try to telnet to the port SQL Server is
> listening on. Make sure the client end (ISA) is using the
> same port.
> Make sure SQL Server is listening on the correct protocols
> as well. Make sure you have TCP/IP enabled.
> And then run through the following article:
> Potential causes of the "SQL Server does not exist or access
> denied" error message
> http://support.microsoft.com/?id=328306
>
> -Sue
> On Tue, 23 Jan 2007 10:03:10 -0500, "Michael Mastro"
> <MikeRM2XXX@.worldnet.att.net> wrote:
>
|||Well at least it's narrowed down. Check the logs on your ISA
server. It looks like it's still being blocked there.
-Sue
On Thu, 25 Jan 2007 10:35:04 -0500, "Michael Mastro"
<MikeRM2XXX@.worldnet.att.net> wrote:
>I tried the following with still no luck.
>First off I went into the SQL Server logs and found out that it is listening
>in on TCP port 2440, it also mentioned 2441.
>I then went to the ISA server and created protocol that allows inbound and
>outbound connections on 1433, 2440, and 2441. I created an access rule that
>allows any of the protected networks and the local host to access the new
>protocol I created with the SQL server.
>I went back to the SQL server machine, and started up the profiler to run a
>trace.
>Back to the ISA machine, and opened up telnet and tried to connect to SQL
>server machine via 1433, then 2440, then 2441. Each time connect failed. I
>also tried a static IP on the ODBC set for 2440. And each time as the same
>before.
>I looked over the SQL Profiler trace and it does not even show any
>connection attempts from the ISA machine.
>Pinging and PathPinging show good connections. Plus a looking over the
>ports on the SQL server machine show that it is listening on those ports.
>Still scratching my head.
>Michael R. Mastro II
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:iejdr215njd7fp0taafif3lcsdb508i420@.4ax.com.. .
>
|||Well looking at the Firewall logs I can see the it is opening the port then
2 seconds later terminating with a 0x80074E21. Still unable to figure a way
around this one.
Michael R. Mastro II
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:0e3jr2dffad96n056htlmnpkrubqdvr49s@.4ax.com...
> Well at least it's narrowed down. Check the logs on your ISA
> server. It looks like it's still being blocked there.
> -Sue
> On Thu, 25 Jan 2007 10:35:04 -0500, "Michael Mastro"
> <MikeRM2XXX@.worldnet.att.net> wrote:
>
am trying to setup the OBDC on the ISA server and it is failing each time.
It cannot reach the server. Every other computer in the domain can access
the SQL server via OBDC. So what am I missing to do that on the ISA server.
I am running ISA 2006 Enterprise, and have set the system policy to use SQL
for logging. Plus I have a access rule that allows SQL through ISA. Anyone
know what I missed?
TCP/IP is set up as dynamic, and I can ping the SQL Server.
The following is the failure I get from ODBC:
Connection failed:
SQLState: '01000'
SQL Server Error: 10065
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection Failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist
or access denied.
Thanks,
Michael R. Mastro II
It can be a lot of different things. Enable login auditing
or run profiler to see if it's actually connecting on the
SQL Server end. It just makes troubleshooting easier.
If it's a named instance, make sure you are specifying the
instance name.
You'd also want to check your ports and protocols - one way
to check is look in the SQL Server error log from when it
started up to determine what ports and protocols SQL Server
is listening on.
From the ISA server, try to telnet to the port SQL Server is
listening on. Make sure the client end (ISA) is using the
same port.
Make sure SQL Server is listening on the correct protocols
as well. Make sure you have TCP/IP enabled.
And then run through the following article:
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306
-Sue
On Tue, 23 Jan 2007 10:03:10 -0500, "Michael Mastro"
<MikeRM2XXX@.worldnet.att.net> wrote:
>Ok here is the problem. I am trying to set up logging on SQL 2005. Now I
>am trying to setup the OBDC on the ISA server and it is failing each time.
>It cannot reach the server. Every other computer in the domain can access
>the SQL server via OBDC. So what am I missing to do that on the ISA server.
>I am running ISA 2006 Enterprise, and have set the system policy to use SQL
>for logging. Plus I have a access rule that allows SQL through ISA. Anyone
>know what I missed?
>TCP/IP is set up as dynamic, and I can ping the SQL Server.
>The following is the failure I get from ODBC:
>Connection failed:
>SQLState: '01000'
>SQL Server Error: 10065
>[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
>(Connect()).
>Connection Failed:
>SQLState: '08001'
>SQL Server Error: 17
>[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist
>or access denied.
>
>Thanks,
>Michael R. Mastro II
>
|||I tried the following with still no luck.
First off I went into the SQL Server logs and found out that it is listening
in on TCP port 2440, it also mentioned 2441.
I then went to the ISA server and created protocol that allows inbound and
outbound connections on 1433, 2440, and 2441. I created an access rule that
allows any of the protected networks and the local host to access the new
protocol I created with the SQL server.
I went back to the SQL server machine, and started up the profiler to run a
trace.
Back to the ISA machine, and opened up telnet and tried to connect to SQL
server machine via 1433, then 2440, then 2441. Each time connect failed. I
also tried a static IP on the ODBC set for 2440. And each time as the same
before.
I looked over the SQL Profiler trace and it does not even show any
connection attempts from the ISA machine.
Pinging and PathPinging show good connections. Plus a looking over the
ports on the SQL server machine show that it is listening on those ports.
Still scratching my head.
Michael R. Mastro II
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:iejdr215njd7fp0taafif3lcsdb508i420@.4ax.com...
> It can be a lot of different things. Enable login auditing
> or run profiler to see if it's actually connecting on the
> SQL Server end. It just makes troubleshooting easier.
> If it's a named instance, make sure you are specifying the
> instance name.
> You'd also want to check your ports and protocols - one way
> to check is look in the SQL Server error log from when it
> started up to determine what ports and protocols SQL Server
> is listening on.
> From the ISA server, try to telnet to the port SQL Server is
> listening on. Make sure the client end (ISA) is using the
> same port.
> Make sure SQL Server is listening on the correct protocols
> as well. Make sure you have TCP/IP enabled.
> And then run through the following article:
> Potential causes of the "SQL Server does not exist or access
> denied" error message
> http://support.microsoft.com/?id=328306
>
> -Sue
> On Tue, 23 Jan 2007 10:03:10 -0500, "Michael Mastro"
> <MikeRM2XXX@.worldnet.att.net> wrote:
>
|||Well at least it's narrowed down. Check the logs on your ISA
server. It looks like it's still being blocked there.
-Sue
On Thu, 25 Jan 2007 10:35:04 -0500, "Michael Mastro"
<MikeRM2XXX@.worldnet.att.net> wrote:
>I tried the following with still no luck.
>First off I went into the SQL Server logs and found out that it is listening
>in on TCP port 2440, it also mentioned 2441.
>I then went to the ISA server and created protocol that allows inbound and
>outbound connections on 1433, 2440, and 2441. I created an access rule that
>allows any of the protected networks and the local host to access the new
>protocol I created with the SQL server.
>I went back to the SQL server machine, and started up the profiler to run a
>trace.
>Back to the ISA machine, and opened up telnet and tried to connect to SQL
>server machine via 1433, then 2440, then 2441. Each time connect failed. I
>also tried a static IP on the ODBC set for 2440. And each time as the same
>before.
>I looked over the SQL Profiler trace and it does not even show any
>connection attempts from the ISA machine.
>Pinging and PathPinging show good connections. Plus a looking over the
>ports on the SQL server machine show that it is listening on those ports.
>Still scratching my head.
>Michael R. Mastro II
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:iejdr215njd7fp0taafif3lcsdb508i420@.4ax.com.. .
>
|||Well looking at the Firewall logs I can see the it is opening the port then
2 seconds later terminating with a 0x80074E21. Still unable to figure a way
around this one.
Michael R. Mastro II
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:0e3jr2dffad96n056htlmnpkrubqdvr49s@.4ax.com...
> Well at least it's narrowed down. Check the logs on your ISA
> server. It looks like it's still being blocked there.
> -Sue
> On Thu, 25 Jan 2007 10:35:04 -0500, "Michael Mastro"
> <MikeRM2XXX@.worldnet.att.net> wrote:
>
Subscribe to:
Posts (Atom)