tracker issue : CF-3492620

select a category, or use search below
(searches all categories and all time range)
Title:

[ANeff] Bug for: 64-bit CF10 creates wrong registry entries for ODBC data sources

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 01/30/2013

Components: Database

Versions: 10.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: Final /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Win All

Vote Count: 0

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_not_fixed on October 12, 2016 using build 2016.0.01.298513
(Filing this b/c I don't think I ever actually filed a bug about it)

First, an important note: DataDirect SequeLink runs as a 32-bit process in 64-bit Windows.

Issue: When creating an ODBC data source in 64-bit Windows, CF10 creates 32-bit Windows registry entries. This is why ODBC data sources fail to work in CF10 by default.

Steps to Reproduce:

1) Create an ODBC data source in 64-bit CF10's CF Admin

Actual Result: "Unable to update the NT registry. Variable DRIVERPATH is undefined." is displayed in CF Admin and data source does not work

Expected Result: CF Admin should always create the proper 32-bit registry entries for ODBC data sources, so that the data sources can work.

Temporary Workaround: http://blogs.coldfusion.com/post.cfm/coldfusion-10-64bit-and-msaccess

Adding an ODBC data source in 64-bit CF10 creates these incorrect registry entries:

- key: HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\{Data Source Name here}
- value: HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources\{Data Source Name here}

However, it should create these correct registry entries:

- key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\{Data Source Name here}
- value: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources\{Data Source Name here}

To verify, just delete the 64-bit registry entries (after following the steps in that blog article to add the 32-bit registry entries) and see that the ODBC data source still works.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3492620

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:

Attachments:

Comments:

Related URL: http://blogs.coldfusion.com/post.cfm/coldfusion-10-64bit-and-msaccess
Comment by External U.
16439 | January 30, 2013 12:23:32 AM GMT
I see I had a typo.. Just replace this: "Issue: When creating an ODBC data source in 64-bit Windows, CF10 creates 32-bit Windows registry entries." with this: "Issue: When creating an ODBC data source in 64-bit Windows, CF10 creates 64-bit Windows registry entries."
Comment by External U.
16440 | February 03, 2013 04:25:23 AM GMT
Adobe, I've verified this is fixed in build 11.0.0.294632. Please note: CF Admin still displays the red text "Unable to update the NT registry. Variable DRIVERPATH is undefined." while ODBC DSN creation is successful. So, that red text can be ignored and should be removed. Thanks!, -Aaron
Comment by External U.
16441 | August 12, 2015 12:34:44 AM GMT
Adobe, Please disregard my last comment. This issue is not fixed. The issue remains exactly as described in the description. Thanks!, -Aaron
Comment by External U.
16442 | August 12, 2015 12:51:19 AM GMT
Adding 64-bit ODBC driver for 64-bit ColdFusion installations.
Comment by Krishna R.
16443 | September 23, 2015 01:26:28 PM GMT
Hi Krishna, Thanks very much! -Aaron
Comment by External U.
16444 | September 23, 2015 01:46:16 PM GMT
This issue is fixed and this fix will be available as part of next major release of ColdFusion.
Comment by Nimit S.
16445 | September 23, 2015 11:12:45 PM GMT
Hi Adobe, This is not fixed. It needs re-opened. CF2016 -does- run ODBC Server/Agent as 64-bit (good). CF2016 -still- does not write the correct registry entries (bad). Steps to reproduce: 1) In CF Admin, create an Access DSN "MyAccessDSN" 2) See red error text and see DSN verification fails (and queries fail) 3) In Windows Registry see the incomplete list of values under HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\MyAccessDSN\Engines\Jet (and extraneous "Jet 2.x" key) 4) In CF Admin, delete MyAccessDSN 5) In C:\Windows\System32\odbcad32.exe, on the "System DSN" tab, create the MyAccessDSN 6) In Windows Registry see the the complete list of values under HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\MyAccessDSN\Engines\Jet 7) In CF Admin, create the MyAccessDSN (and ignore the red error text) 8) See DSN verification succeeds and queries work Note: Before performing the above steps, ensure the AccessDatabaseEngine_X64.exe driver is installed from https://www.microsoft.com/en-us/download/details.aspx?id=13255. If that installer throws an error saying a 32-bit Office app is already installed, then run that installer from the command line w/ the "/passive" flag (ex: "c:\path\to\AccessDatabaseEngine_X64.exe /passive"). Thanks!, -Aaron
Comment by External U.
16446 | October 12, 2016 05:54:26 PM GMT
>10/12/2016 17:54:26 GMT >This is not fixed. It needs re-opened. >CF2016 -still- does not write the correct registry entries (bad). Hello? -Aaron
Comment by Aaron N.
16447 | August 07, 2017 05:04:59 AM GMT
When an ODBC DSN can be created via CF Admin w/o error, and queries run successfully, then this is fixed. That is, ultimately, the goal here. To be able to run a query.. against an ODBC DSN. If you compare the registry entries CF Admin creates vs the registry entries that the Windows ODBC (64-bit) tool creates, you'll see CF Admin still doesn't write the correct entries. Thanks!, -Aaron
Comment by Aaron N.
16448 | August 07, 2017 05:12:02 AM GMT
*bump* Adobe?? Again, this is _not_ fixed. Please see above repro steps/comments. Please re-open. Thanks!, -Aaron
Comment by Aaron N.
16449 | August 22, 2017 07:52:25 PM GMT
Umm.. it's been a YEAR since I mentioned this isn't fixed. Adobe!?!?
Comment by Aaron N.
16450 | October 01, 2017 08:17:43 AM GMT
Aaron, This issue was fixed in CF 2016. Can you please confirm which CF version did you try it on? I will try it again and re-open this issue. -Nimit
Comment by Nimit S.
16451 | October 01, 2017 02:10:46 PM GMT
Hi Nimit, Regarding: "This issue was fixed in CF 2016." I see Krishna's comment above: "Adding 64-bit ODBC driver for 64-bit ColdFusion installations." Yet, CF-4202200 shows we still must install the 64-bit driver manually? Verified in build 2018.0.01.308605 (PreRelease). Maybe we can do Connect sometime? Thanks!, -Aaron
Comment by Aaron N.
27808 | May 15, 2018 01:20:38 AM GMT