


Is not running or has not been installed. JDBC Driver]internal error: The specified DSN contains anĪrchitecture mismatch between the Driver and ApplicationĬoldfusion 11 new install - The ColdFusion ODBC Server service Mismatch between the Driver and Application Socket]internal error: The specified DSN contains an architecture Variable DRIVERPATH is undefined.>Ĭonnection verification failed for data source: neg Unfortunately after submitting the selected variables, a red error I was able to chose ms access as driver and to browse to the database file. Having restarted the coldfusion services I was able to start the Thank you for providing me with the hotfix. And hopefully CF12 can properly register ODBC DSNs w/ Windows as the correct bitness. Hopefully this port issue can be fixed in a future-proof way. Issue #5 and #6) (unresolved tickets 34925608) ODBC DSN creation (#5) and deletion (#6) fail in non-cfusion instances. Variable DRIVERPATH is undefined." error indicates CF didn't successfully register the DSN as 32-bit - tho the 64-bit registration succeeds) Issue #4) (unresolved ticket 3492620) 64-bit CF11 still requires same-named 32-bit "System DSN" to be manually registered w/ Windows using C:\Windows\SysWOW64\odbcad32.exe. During Splendor Beta, I added a comment on 3492574 noting this - but there was no reply. Workaround #3) Noted in description for this ticket (install CF10 w/ ODBC support, then create the CF11 ODBC DSN, then stop CF10's ODBC service). (same issue regardless if CF10 was installed or not prior to installing CF11) Issue #3) Creating CF11 ODBC DSN fails if CF10's ODBC Server isn't running. Workaround #2) Open that file and replace all 20002 with 20004. Issue #2) CF11's Settings Migration, Datasources page and CAR Deploy feature all write 20002 to C:\ColdFusion11\cfusion\lib\neo-datasource.xml for ODBC DSNs. Workaround #1) Open that file and replace all 20002 with 20004 (CF11's ODBC Server port). Issue #1) CF11's C:\ColdFusion11\cfusion\lib\neo-drivers.xml has 20002 (CF10's ODBC Server port) for both MSAccess and ODBCSocket. Just also noting the comment here as it contains some workarounds.

I added the following comment on 3759846.
