The forum will experience an outage sometime between February 10 at 7:00pm EST and February 12 at 11:59 EST for installation of security updates. The actual time and duration of the outage are unknown but attempts will be made to minimize the downtime. We apologize for any inconvenience.

I currently install a new Database Server on a 64bit W2K8R2 System. ASA is currently version 10.0.1 but will be upgraded in the next months.

I have installed 64bit and 32 Drivers for a remote database server. (MYSQL)

I was not able to connect to the remote server when I created a System DSN for the 64bit Driver. The 32bit driver System DSN generated with the SysWOW64odbcad32.exe was accessible.

[Sybase][ODBC Driver][SQL Anywhere]Verbindung mit dem Server 'TRMTime' konnte nicht aufgenommen werden: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
SQL Statement: CALL dbo.sp_remote_tables( 'TRMTime', NULL, NULL, NULL, 1 )

I couldn't find this detail in the Documentation. Any Ideas ? I would be interested if there are changes in later releases of ASA.

asked 05 Jul '11, 08:14

Thomas%20Duemesnil's gravatar image

Thomas Dueme...
accept rate: 16%

edited 05 Jul '11, 08:17

Were you running a 32 or 64bit server when you ran your tests?

(05 Jul '11, 08:36) Mark Culp

Are you using the 64 bit database server?

(No, I don't have an answer...)

(05 Jul '11, 08:42) Volker Barth
Replies hidden

It was the 32bit one. Now it is logical. Thanks

(05 Jul '11, 08:51) Thomas Dueme...

When you use external environments, the server launches a separate executable which communicates with the server using normal database connections. As a result the bitness of the server need not match the bitness of the external environment executable. The same is not true for remote data access. In the case of the remote data access feature, the server actually loads the ODBC driver in process and then communicates with the ODBC driver using standard ODBC procedure calls. Since the ODBC driver is loaded in process, the bitness of the ODBC driver MUST match the bitness of the server.

permanent link

answered 05 Jul '11, 12:19

Karim%20Khamis's gravatar image

Karim Khamis
accept rate: 40%

You should start the 64 Bit engine if you want to use the 64bit ODBC Connections ;-)

permanent link

answered 05 Jul '11, 08:55

Thomas%20Duemesnil's gravatar image

Thomas Dueme...
accept rate: 16%

Still your question is a useful one, particularly as dbsrv11 and above can use external environments with the opposite bitness, i.e. a 64-bit server can run a 32-bit ODBC environment.

However, I don't know whether this applies to remote data access, too. But Karim and Mark will know:)

(05 Jul '11, 09:02) Volker Barth
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 05 Jul '11, 08:14

question was seen: 1,617 times

last updated: 05 Jul '11, 12:19