I’m still having fun with 64-bit Windows and ODBC. This time, I’m working with SAP BusinessObjects Business Intelligence 4.0 SP2 Patch 10 (BI4) instead of my previous exploits with SAP BusinessObjects Enterprise XI 3.1 (see related article, More Fun with 64-bit Windows and ODBC). My challenge was to easily copy ODBC DSN’s from a customer’s existing XI 3.1 environment to their new BI4 environment without hours of tedious typing in the Windows control panel.
The procedure is simple enough, as ODBC DSN’s are stored in the Microsoft Windows registry. Simply use the registry editor on the source machine to export the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC
tree. Move the generated registry file to the destination machine and load using the registry editor. But when moving between 32-bit Windows and 64-bit Windows, there’s a small catch.
In 64-bit Windows, HKEY_LOCAL_MACHINE\SOFTWARE\ODBC
is where the 64-bit DSN’s are stored. 32-bit DSN’s are stored in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC
. This means that the 32-bit DSN’s that you import from the 32-bit XI 3.1 server automatically become 64-bit DSN’s on the BI4 server by virtue of their registry location.
SAP BusinessObjects BI4 is primarily 64-bit, so most services like the Web Intelligence Processing Server will be looking for 64-bit DSN’s. However, classic Crystal Reports 2011/2013/2016 are 32-bit (even on the BI4 server), so it will look for DSN’s in the second Wow6432Node. I ended up creating these 32-bit DSN’s manually using the ODBC panel on our BI4 staging server (see related article, SAP BusinessObjects BI4 is (Mostly) 64-bit).
However, once I have both 32-bit and 64-bit DSN’s created on the staging server, I can move them easily to other 64-bit Windows machines. I just have to remember to export both the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC
and HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC
keys.
TIP: Remember that each set of DSN’s has its own control panel. To avoid going insane during testing, take a moment to create separate desktop shortcuts to the 32-bit and 64-bit ODBC DSN panels on your 64-bit Windows server (see related article, More Fun with 64-bit Windows and ODBC).
Related Articles
- Fun with 64-Bit Windows and ODBC
- More Fun with 64-Bit Windows and ODBC
- The Fun Never Ends with 64-Bit Windows and ODBC
- SAP BusinessObjects BI4 is (Mostly) 64-bit
For more information, check out this related thread on the BusinessObjects Board (BOB).
Dallas,
Very useful information, I would not have thought of exporting from the registry.
I guess if you’re feeling adventurous you could change the path of the entries in the reg file before importing?
Also Crystal Reports 2011 has a shortcut to the 32bit ODBC panel for convenience.
Matt
I’m going through this now. I’m going to try what Matt suggested, doing an export from the 32-bit system, and then using that as well as making a copy and modifying the path. We have a test server so I can try it out first.
Thanks for the blog post, I’m so glad I’m not the only person going through this insanity!