| bjornhenrikformo@gmail.com 2006-01-05, 7:23 am |
| 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][ODBC
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.
|