(More in a moment on CF2016, where that alone does not seem to suffice.) The steps above about creating a DSN in the Windows 32-bit ODBC control panel (and one in the CF Admin of the same name) should suffice. I will add that resorting to a 3rd party jar (like that hxtt one) should not be necessary, for those wanting to create and use an Access DSN (though that should be discouraged generally) on 64-bit CF10 or 11. Is it possible you did since then do that restart, and all did work and you just forgot to tell us? Or did you maybe give up and never try to verify the DSN again after a restart? Please do let us know. Usually, the "no suitable driver" is because of that (CF does not have the jar loaded). What you don't indicate is whether you had restarted CF, as halbob indicated was the final step. You said you had gotten the jar, put it in the lib, created an "other" DSN, and got the error about "No suitable driver". Pierre, I know your last reply here was from a few months ago, but since I know some people who are paying attention to this thread, I wanted to follow-up with you. Is the driver setting : other or access driver ? The root cause was that: : No suitable driver available for test_16, please check the driver setting in resources file, error: .AccessDriverĬould you tell me where could be the problem in my datasource declaration ? : No suitable driver available for test_16, please check the driver setting in resources file, error: .AccessDriver In CFAdmin, when submitting the datasurce, I get the yellow error message :Ĭonnection verification failed for data source: test_16 No suitable driver available for test_16, please check the driver setting in resources file, When accessing the datasource with a CFM query JDBC URL : jdbc:access:/C:/ColdFusion2016/cfusion/wwwroot/test/site_user.mdb I declared the CF datasource as follow :
I dropped the Access_JDBC30.jar file in : c:/coldfusion16/cfusion/lib I removed all ODBC declaration (32 and 64 bits) Step 6: Go to ColdFusion Admin page and map that DSN using MS Access drivers and verify. Use 64 bit odbc path: C:\Windows\System32\odbcad32.exe
Step 5: Once the installation is completed, you will have to define the DSN using 64 bit drivers. Step 4: Download and install 64 bit MS Access Database Engine from the link: Step 3: Ensure that you have removed all the DSN entries from odbc administrator(both 32 bit and 64 bit under system DSN).Ħ4 bit odbc path: C:\Windows\System32\odbcad32.exeģ2 bit odbc path: C:\Windows\SysWOW64\odbcad32.exe Step2: Ensure that you don’t have any MS Access related data source defined in ColdFusion admin page(under Data Source). Step 1: Uninstall any existing “Microsoft Access database engine 2010” from add\remove program. Please try the below instructions and let me know if it works: Thank you for contacting Adobe ColdFusion support. I received the following instructions from support and this has fixed my problem.
0 kommentar(er)
