-
1. Re: Variable DRIVERPATH is undefined Error
CF probably does not have permission to access to your registry
Locate the following reg key
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\<your data source>\
do you see a string called "Driver"?
if not, create it with the value of "C:\WINDOWS\System32\odbcjt32.dll"
if this works, credit Rob D. -
2. Re: Variable DRIVERPATH is undefined Error
That does work. but has to be done each time an access datasource is added. Is there anyway to give coldfusion permission to access the registry automatically? -
3. Re: Variable DRIVERPATH is undefined Error
I did the exact same thing, but it's not working for me. I still get the following error:
Unable to update the NT registry.
Variable DRIVERPATH is undefined.
Any ideas anyone? -
4. Re: Variable DRIVERPATH is undefined Error
Thank you Rob D. :)
*****************************************
CF probably does not have permission to access to your registry
Locate the following reg key
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\<your data source>\
do you see a string called "Driver"?
if not, create it with the value of "C:\WINDOWS\System32\odbcjt32.dll"
if this works, credit Rob D. -
5. Re: Variable DRIVERPATH is undefined Error
I had same problem with x64 vista found answer
Open C:\Windows\SysWOW64\odbcad32.exe and create a System DSN using the Microsoft Access Driver (*.mdb).
Then open the ColdFusion Admin and create a datasource using the ODBC Socket driver.
Check the Trusted connection checkbox and it should work.
-
6. Re: Variable DRIVERPATH is undefined Error
@jimmoos
Your solution is clean and works! No messing around with registry entries.
I have x64 Windows 7. I took myself backwards and was able to reinstall my ColdFusion MX 6.1 software. It was also my first time to use the "ODBC Socket driver" option. Upto this point I had always used the other drivers (native ones)
Thx buddy
-
7. Re: Variable DRIVERPATH is undefined Error
Thanks so much for the info! I have Windows 7 x64bit with
Coldfusion 6.1. I'm just developing for myself so didn't want to upgrade. This solution worked perfectly. Thanks again!
-
8. Re: Variable DRIVERPATH is undefined Error
I'm having the same problem, but when I try to create a SYSTEM DSN, I don't have a Microsoft Access option. I only have SQL Server and SQL Native Client. Any suggestions? Thanks!
-
9. Re: Variable DRIVERPATH is undefined Error
That's a clean solution, but the MS Access DSN I add in System DSN does not show up in the "ODBC DSN" select box in the Datasource creation form in the CF Admin at
Data & Services > Datasources > ODBC Socket
so when I submit the form I get this error:
A ODBC Datasource must be selected before submitting changes -
10. Re: Variable DRIVERPATH is undefined Error
I had similar issues. Fixed them by installing the 64-bit drivers from here: http://www.microsoft.com/en-us/download/details.aspx?id=13255
Then I had to add the System DSN in the 64-bit ODBC Management Console, which causes it appear in the ODBC DSN drop-down on the CF Admin Data Source form.
Then had to add the same System DSN to the 32-bit ODBC Management Console, to fix this error when CF attempts to connect to the database:
Connection verification failed for data source: PABasketballSSJ
java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application
The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application