We are trying to evaluate our Team Developer applications on Windows Server 2008 (SP 1). But they all have a big issue: ODBC connections don't work, to databases be they local on that WS 2008 computer, or on some other computer in the network. It does work, though, to connect through ODBC the other way around -- to the DB on WS 2008 from other computers in the network (running Win XP). Also, we use MS SQL Server 2005 SP 2. And if we use OLE-DB connections instead of ODBC, it works.
Any idea about, maybe, some tricky settings for the ODBC that could make it work?
I believe the settings for SQL Server 2005 are correct (allowing TCP/IP), and the firewall is down.
ODBC on Windows Server 2008
Re: ODBC on Windows Server 2008
What errors are you getting when you try to connect? Anything specific?
What does an ODBC trace show?
I am going to move this to a different forum where you might get a bit better response.
What does an ODBC trace show?
I am going to move this to a different forum where you might get a bit better response.
Re: ODBC on Windows Server 2008
Thanks.
I'm getting just error 9268 (cannot connect) as if the DB doesn't exist.
Here's the SQL trace:
I'm getting just error 9268 (cannot connect) as if the DB doesn't exist.
Here's the SQL trace:
Code: Select all
test_connection e84-1520 ENTER SQLAllocEnv
HENV * 102454A4
test_connection e84-1520 EXIT SQLAllocEnv with return code 0 (SQL_SUCCESS)
HENV * 0x102454A4 ( 0x01ddcdc0)
test_connection e84-1520 ENTER SQLDataSourcesW
HENV 01DDCDC0
UWORD 2 <SQL_FETCH_FIRST>
WCHAR * 0x01DB5078
SWORD 33
SWORD * 0x0012E310
WCHAR * 0x01DC41E8
SWORD 513
SWORD * 0x0012E312
test_connection e84-1520 EXIT SQLDataSourcesW with return code 0 (SQL_SUCCESS)
HENV 01DDCDC0
UWORD 2 <SQL_FETCH_FIRST>
WCHAR * 0x01DB5078 [ 18] "MS Access"
SWORD 33
SWORD * 0x0012E310 (18)
WCHAR * 0x01DC41E8 [ 31] "Microsoft Acces"
SWORD 513
SWORD * 0x0012E312 (31)
test_connection e84-1520 ENTER SQLDataSourcesW
HENV 01DDCDC0
UWORD 1 <SQL_FETCH_NEXT>
WCHAR * 0x01DB5078
SWORD 33
SWORD * 0x0012E310
WCHAR * 0x01DC41E8
SWORD 513
SWORD * 0x0012E312
test_connection e84-1520 EXIT SQLDataSourcesW with return code 0 (SQL_SUCCESS)
HENV 01DDCDC0
UWORD 1 <SQL_FETCH_NEXT>
WCHAR * 0x01DB5078 [ 11] "Excel"
SWORD 33
SWORD * 0x0012E310 (11)
WCHAR * 0x01DC41E8 [ 30] "Microsoft Excel"
SWORD 513
SWORD * 0x0012E312 (30)
test_connection e84-1520 ENTER SQLDataSourcesW
HENV 01DDCDC0
UWORD 1 <SQL_FETCH_NEXT>
WCHAR * 0x01DB5078
SWORD 33
SWORD * 0x0012E310
WCHAR * 0x01DC41E8
SWORD 513
SWORD * 0x0012E312
test_connection e84-1520 EXIT SQLDataSourcesW with return code 0 (SQL_SUCCESS)
HENV 01DDCDC0
UWORD 1 <SQL_FETCH_NEXT>
WCHAR * 0x01DB5078 [ 11] "dBASE"
SWORD 33
SWORD * 0x0012E310 (11)
WCHAR * 0x01DC41E8 [ 30] "Microsoft dBase"
SWORD 513
SWORD * 0x0012E312 (30)
test_connection e84-1520 ENTER SQLDataSourcesW
HENV 01DDCDC0
UWORD 1 <SQL_FETCH_NEXT>
WCHAR * 0x01DB5078
SWORD 33
SWORD * 0x0012E310
WCHAR * 0x01DC41E8
SWORD 513
SWORD * 0x0012E312
test_connection e84-1520 EXIT SQLDataSourcesW with return code 0 (SQL_SUCCESS)
HENV 01DDCDC0
UWORD 1 <SQL_FETCH_NEXT>
WCHAR * 0x01DB5078 [ 8] "AMDB"
SWORD 33
SWORD * 0x0012E310 (8)
WCHAR * 0x01DC41E8 [ 10] "SQL S"
SWORD 513
SWORD * 0x0012E312 (10)
Re: ODBC on Windows Server 2008
Check your ODBC setup using Datasource Manager. Make sure there is a correct sql.ini file that is being specified in the 'configuration file' box (i.e. one that points to the correct server where the SQLBase engine is running with the database).
Re: ODBC on Windows Server 2008
I solved the problem! It was more like PEBCAC because of an error in sql.ini. Thanks for the help.
Who is online
Users browsing this forum: [Ccbot] and 1 guest