Using our Attunity 32 bit drivers on a Windows 64 bit machine is a supported process within Attunity. There are a few issues that need to be addressed before the drivers can be used or configured.

On installation our drivers in 32 bit mode are self registering drivers that use the executable regsvr32.exe. On completion the OLEDB and ODBC drivers are readily available. The installation on a 64 bit Windows machine runs the executable from the default system32 directory. This fails attempting to register in the 64 bit registration. Our drivers do not self install using this executable.

In order to register a 32 bit driver on a 64 bit machine, Microsoft has offered a set of 32 bit executables in the WOW(Windows on Windows) directory of the system. In order to register our drivers you must follow the steps detailed below.

1.) Compete the Attunity installation for Windows using our executable kit.

2.) Open a DOS window and change directory to the Windows-->WOW directory.

3.) Open up Windows Explorer and go to the tool bar option "View--> Address". Drill down to the Attunity --> bin directory (c:\Program Files\Attunity\Server\bin by default). Copy the address into a Notepad document two times. At the end of each entry add in the Attunity DLL's to register.


C:\Program Files\Attunity\Server\Bin\Odnav32.dll

C:\Program Files\Attunity\Server\Bin\Nav32.dll

Copy the first complete line and go to the DOS window. From here execute the 32 bit regsvr32.exe with the path to the each dll as input. Do this for both DLL's. This will register the Attunity DLL's in the WOW portion of the registry.

There are a few things to note here.

1.) To define an Attunity 32 bit ODBC definition you must use the WOW\odbc32.exe to bring up the GUI interface that allows for the 32 bit DSN's. The same GUI is used in the Control Panel-->Administrative Tools --> Data Sources(ODBC) GUI but this default is for 64 bit definitions.

2.) You must define a SYSTEM DSN so that the 32 bit registration can be accessed via applications.

3.) You can use the OLEDB driver in code but certain Microsoft tools will NOT recognize the 32 bit registration of this driver.

4.) When accessing Attunity within Microsoft tools such as SQL Server 2005 or SSIS you must use the "Kagera" solution as it sometimes called where a Microsoft OLEDB provider points to an ODBC definition. There are two available depending on the MS MDAC you have or whether the .NET environment is installed on the box. The MDAC Version is called "MS OLEDB Providers for ODBC" and the .NET version is called ".NET for ODBC". Once these 64 bit interfaces are available either can be used to point to an existing 32 ODBC SYSTEM DSN defined using the Attunity ODBC driver.