Solved

Problems with ODBC connector running on Windows 2003 R2 64 bit

Posted on 2010-08-25
4
523 Views
Last Modified: 2012-05-10
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.
0
Comment
Question by:sclltd
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 6

Expert Comment

by:Jerryuk007
ID: 33529977
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
0
 

Author Comment

by:sclltd
ID: 33538757
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
0
 
LVL 6

Accepted Solution

by:
Jerryuk007 earned 500 total points
ID: 33575509
Nope. That's correct.
Though if you add a new ODBC DSN using C:\Windows\SysWOW64\odbcad32.exe you would then have the option to have a lot more different DSN (like Access, etc...) compare to the on in system32 which might have only a couple of ODBC Drivers listed.

So, did you add you System DSN using the C:\Windows\SysWOW64\odbcad32.exe or the one in System32?
Also be aware that a Web Service by default will do its best to use the 64 bits ODBC even if the DLL behind has been compiled in 32 bits.

It seems that the ODBC you need to use is the 32 bits one in C:\Windows\SysWOW64\odbcad32.exe

Are you also using some kind of Web Application running on 64 bits server? If yes, make sure you enabled 32 bits compatibility (in the AppPool IIRC).

Hope this helps.

Jerry
0
 

Author Comment

by:sclltd
ID: 33582241
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.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

JSON is being used more and more, besides XML, and you surely wanted to parse the data out into SQL instead of doing it in some Javascript. The below function in SQL Server can do the job for you, returning a quick table with the parsed data.
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
Via a live example, show how to setup several different housekeeping processes for a SQL Server.
Viewers will learn how the fundamental information of how to create a table.

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question