Microsoft Windows Server R2 Standard 64 bit 6. Stack Overflow works best with JavaScript enabled. I looked in the SysWOW key to find the parameters that were set up using the bit version of the ODBC administration tool and recreated this in the standard location. See the supported platforms for SP3 – Middleware. After you finish these steps, system administrators and possibly data architects depending upon permissions in your environment should install the Metadata Location. If you cannot establish a connection after checking for errors, contact your Netezza system administrator. Apparently, Microsoft never renamed their “system32” folder, so system32 really has all of the 64 bit drivers.

Uploader: Zologrel
Date Added: 21 February 2011
File Size: 15.28 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 95505
Price: Free* [*Free Regsitration Required]

Open IIS manager, select Application Pools, select the application pool you are using, click on Advanced Settings in the right-hand menu. This allows you to skip supplying the user and password during ODBC connection.

Configuring the ODBC data source and driver (Windows)

After significant and fruitless searching to find how to get the OdbcConnection class to look for the DSN in the right placeI stumbled upon a web site that suggested modifying the registry to solve a different problem. You can also configure a user data source.

Unfortunately the person doing the testing didn’t test the functionality of a couple of apps that I have that rely on accessing the data to do both live- and post-processing on the data to produce some reports. NET couldn’t look it up. Gues that Universe designer doesn’t realy like the 64Bit driver yet. I know its too late for the reply!


Select a search Explain These Choices I 332 managed to resolve by installing both 32 bit and 64 bit ODBC drivers.

Sign up using Email and Password. Baddack 8 I looked in the SysWOW key to find the parameters that were set up using the bit version netezzx the ODBC administration tool and recreated this in the standard location. Installation Location The Aginity Amp application is installed into your user home directory, for example, c: Not endorsed by or affiliated with SAP.

Install Aginity Amp Execute the installation package you have downloaded at the previous step. The next issue was the software that we ran was compiled to use ‘Any CPU’. The package also installs the command-line interface for Code Generator. Sign up using Facebook.

The installation will proceed and provide status on the last page. All times are GMT – 5 Hours. This topic provides instructions on installation of the Aginity Amp application.

Configuring the ODBC driver and creating the data sources on Windows

Thu Oct 14, 5: Or provides a right click context menu to do so. I didn’t add an entry for the driver, however, as that was not installed by the standard installer for the app either. When the License Key prompt appears, paste the key you have been neteza into the Specify the Aginity Aginity Amp license below box either paste manually, click Paste from clipboardor select Load from File if you have the key saved in a file.


netezz Click Finish to finish the installation. A message box is displayed, indicating that the connection attempt was either successful or failed: Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your obdc use of the website is subject to these policies.

Wed Oct 27, 4: Kasindula Forum Member Joined: I gues I didn’t understand you correctly. So, seems to be, that the 32 bit driver fakes to be a 64 bit one The driver isn’t seen by the 32 bit ODBC administration panel c: Our issue was similar to OP’s, we upgraded 32 bit XP machines biy 64 bit windows 7 and our application software that uses a 32 bit ODBC driver stopped being able to write to our database.