tracker issue : CF-4202200

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

[ANeff] Bug for: Access DSN creation fails

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/UserError

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

Created: 04/30/2018

Components: Database, MSAccess

Versions: 2018

Failure Type: Non Functioning

Found In Build/Fixed In Build: 2018.0.01.308605 (PreRelease) /

Priority/Frequency: Normal / Some users will encounter

Locale/System: / Windows 10 64 bit

Vote Count: 0

Issue: Access DSN creation fails

Repro:

1) In CF Admin, create a "Microsoft Access" data source named "MyAccessDSN" pointing to attached MyAccessDatabase.mdb.
2) See red error text:
-----------
- Unable to update the NT registry.
Variable DRIVERPATH is undefined.
-----------
3) See writeDump(queryExecute("SELECT * FROM myTable", [], {datasource="MyAccessDSN"})) throws "java.sql.SQLException: [Macromedia][SequeLink JDBC Driver]TCP/IP error, connection refused."
4) Per CF-4202199, change all '20006' to '20008' in neo-datasource.xml and restart CF.
5) See writeDump(queryExecute("SELECT * FROM myTable", [], {datasource="MyAccessDSN"})) throws "java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error:  Data source name not found and no default driver specified"
6) In CF Admin, delete the "MyAccessDSN" DSN
7) Install AccessDatabaseEngine_X64.exe (Microsoft Access Database Engine 2016 Redistributable) from https://www.microsoft.com/en-us/download/details.aspx?id=54920
8) Repeat #1
9) See red error text:
-----------
- Connection verification failed for data source: MyAccessDSN
java.sql.SQLException: [Macromedia][SequeLink JDBC Driver]TCP/IP error, connection refused.
The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver]TCP/IP error, connection refused.
-----------
10) Repeat #4
11) See writeDump(queryExecute("SELECT * FROM myTable", [], {datasource="MyAccessDSN"})) succeeds

Actual Result: Step #7 is necessary

Expected Result: Step #7 is unnecessary

Attachments:

Comments:

Hi Aaron, You get "Variable DRIVERPATH is undefined" exception, when you don't have the driver installed on the box. Can you download the driver(x64) from this URL: https://www.microsoft.com/en-in/download/details.aspx?id=13255 and install and try again?
Comment by HariKrishna K.
27809 | May 03, 2018 06:14:18 AM GMT
Hi Adobe, I see you closed this ticket w/o any comment. You marked it "Closed/Withdrawn/UserError". Could you please explain? Thanks!, -Aaron
Comment by Aaron N.
27761 | May 12, 2018 07:48:47 AM GMT
Aaron, the comment remained internal for some reason. We've made it external. If you check the support matrix for 2016 too, support for Access is not listed but users can download the driver from the MSN download site (refer Hari;s comment on the same) and get it to work
Comment by Vamseekrishna N.
27810 | May 15, 2018 05:31:15 AM GMT
Hi Vamsee, Thank you for making Hari's comment visible. Issue: CF's "Supplied Drivers" doc has *always* listed Access. And 32-bit CF Admin had no issue creating an Access DSN. Saying "since 32-bit Windows bundled an Access driver, we listed Access in the "Supplied Drivers" doc is ingenuous. If Adobe says CF "Supplied X" then it means _CF_ supplied X. I don't see why CF can't just ship the latest 64-bit Access driver, since that'd be a better customer experience than for 64-bit CF Admin to throw error messages. Note: _I_ am unaffected b/c I know my way around the issue. BUT, customers trying to use CF Admin, and choosing "Access" on DSN page, would naturally expect no issue since it's always been a "Supplied Driver". I hope Adobe can see where I'm coming from? I started a discussion here (hoping someone can clarify?): https://coldfusion.adobe.com/2018/05/supplied-drivers/ Thanks!, -Aaron P.S. Tracker email notifications do not work. I'm just now seeing questions from Adobe on many tickets.
Comment by Aaron N.
29022 | June 12, 2018 12:53:43 AM GMT
To clarify: yes, me (*I*) know I can resolve the issue by installing the driver from Microsoft's download site. I noted the same in this ticket's description. The issue is CF Admin's error messages conflict w/ CF's long-standing "Supplied Drivers" doc. And, for those that say: never use Access. Wrong. Never say never =P I agree Access should not be used in production. However, there is certainly a need/use for CF's supplied Access driver for connecting with desktop apps that store their data in Access files. Thanks!, -Aaron
Comment by Aaron N.
29023 | June 12, 2018 12:58:02 AM GMT