Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ODBC Issue on Win 2008 R2 64 bit

1,861 views
Skip to first unread message

Slamet

unread,
Dec 3, 2009, 6:07:14 AM12/3/09
to
I had 32 bit application installed on Win 2008 R2 64 bit,

my applications use ODBC to access sql server 2005 32 bits on another
server.

I had configure odbc (Sql Server Type) under :

%SystemRoot%\SysWOW64\odbcad32.exe

ODBC is successfull, but why i cannot connet to my database from my
applications ?

I think is about win 2008 R2 issue not ODBC anymore,
to campare a problem i try scenario like this :

I try to install an application at win 2008 64 bit (not win 2008 R2 64
bit), and i use 2 methode :

1. ODBC SQL Server version 6.00.6001.18000
2. ODBC SQL Server Native Client 10.0 version 2009.100.1352.12

and all successfull, i can connet to database.

So i'm sure, it's something wrong with Win 2008 R2 64 bit, any update
or patch for this issue ?

I think this issue related to link below :

http://msdn.microsoft.com/en-us/library/aa384253(VS.85).aspx#redirected__shared__and_reflected_keys_under_wow64

any idea ?

Pak-Ming Cheung - MSFT

unread,
Jan 29, 2010, 11:08:01 AM1/29/10
to
There are hundreds of reasons that it can fail. Therefore, could you tell us
what the exact error message?
Did you try SQL Server Native Client 10.0 on Windows Server 2008 R2?

The link you have given is not very relevant. Since you know using
"c:\windows\syswow64\odbcad32" to setup your DSN, the 32-bit / 64-bit problem
shouldn't happen in your case.

Instead, please make sure you have configured your DSN successfully. In the
last page of the GUI during setting up the DSN, you can press the button
"Test Connection" to verify your setting.

Also, if there is any error related to "cannot find the server", you may
need to double check the firewall setting on both the server side and the
client side.

Thanks,
Ming.
WDAC Team, Microsoft.
P.S. We recommend customers to use the forum to ask questions in the future,
where you can obtain a faster response (Forum is at:
http://social.msdn.microsoft.com/forums/en-US/sqldataaccess/threads/)


"Slamet" wrote:

> .
>

Carlton@discussions.microsoft.com Randy Carlton

unread,
Feb 2, 2010, 8:50:03 AM2/2/10
to
I'm having the same or similar issue to the individual prior. The connection
tests properly to a remote instance of SQL Server 2008 64-bit when setting up
the 32-bit ODBC on Windows 2008 SP2 64-bit. I can also connect successfully
to the database when using the 32-bit OSQL from the SQL Server 2008 32-bit
client via the command line and using the data source name (switch -D).
However, the 32-bit application is returning the following error in its logs
for tests with 32-bit ODBC connections tested with the default SQL Server
driver and the SQL Server Native Client 10.0:
While trying f_maint password: Trying to connect through OSQL.EXE: [SQL
Server Native Client 10.0]Named Pipes Provider: Could not open a
connection to SQL Server [67].
[SQL Server Native Client 10.0]Login timeout expired
[SQL Server Native Client 10.0]A network-related or instance-specific error
has occurred while establishing a connection to SQL Server. Server is not
found or not accessible. Check if instance name is correct and if SQL Server
is configured to allow remote connections. For more information see SQL Server
Books Online.

For user f_maint: Trying to connect through ODBC: IM002:1:0:[Microsoft][ODBC
Driver Manager] Data source name not found and no default driver specified


Any and all help would be greatly appreciated.

Thanks,
Randy Carlton

Randy Carlton

unread,
Feb 2, 2010, 11:28:01 AM2/2/10
to
The issue is resolved. This was an application specific issue and not a
general ODBC issue.

The properties file had multiple data source entries and only one of them
was set properly. Once they all were set properly, the application was able
to connect successfully.

0 new messages