asked on

Problems with ODBC connector running on Windows 2003 R2 64 bit

We have a Jade application that extracts statistics form a Jade database and inserts/updates them into a SQL 2005 database. The Jade application was running on a separate server from the database server. The application uses an ODBC connection to the database server. The database server has since been replaced and updated from Windows 2003 32 bit to Windows 2003R2 64 bit. The Jade application is still running 32 bit version. In order to take advantage of the shared memory that Jade uses all of the applications such as this SQL extract are being moved to the new server. The application that extracts the data is exactly the same as then one running on the old 32 bit server, uses the same ODBC connection settings etc. In the Jade log the same information is being produced. For example the following snippet for the log shows that updates have occurred.

26/08/2010 15:56:46.752 : BGP_ControllerApp/Process/187.628:
EDB - Committed transaction. 0 creates, 72 updates, 0 deletes. 72 changes in 0 seconds.

However no data is being received on the SQL server. The DBA run profiler on the SQL server but saw no data coming from the database server but when the application was switched back to the old server data was present in profiler.

It seems to me that the issue is with the ODBC connector.

How would I go about troubleshooting the connection to see if in fact this is the cause of the problem.

Jerryuk007

In 64 bits OS, you have TWO ODBC Drivers...

Try to run your ODBC DataSource Admin from C:\Windows\SysWOW64\odbcad32.exe

The default one is being run from the C:\Windows\System32 directory

Hope this helps.

Jerry

sclltd

ASKER

If I run it from that location and then look at the help tab it is still using the dll's from system32. Does this mean I need a server restart to clear the files from memory? And how do I prevent the system 32 files from loading automatically?

Screenshot.jpg

ASKER CERTIFIED SOLUTION

Jerryuk007

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

sclltd

ASKER

Had setup the new DSN using C:\Windows\SysWOW64\odbcad32.exe but this did not initially resolve the issue; there was still no information in the ODBC trace log. Suspected that this may now be an issue with the previous DSN still being in memory. Arranged for an outage on the server and restarted the server, tested and now see traffic in the ODBC trace log, data is now being transferred to SQL.