Skip to main content
nickeldoor_ash
nickeldoor_ash
Participant
August 12, 2007
Question

Add New Data Source - Problem

  • August 12, 2007
  • 2 replies
  • 435 views
Hi there, I just completed a basic tutorial on Access db and was trying to load this db onto CF MX 7. When I tried to: Add New Data Source (with MS Access driver selected), it gave an error: "Unable to update the NT registry. Variable
DRIVERPATH is undefined."

The db file is from: C:\CFusionMX7\wwwroot\database\teacloud.mdb

However, when i reload the data source page, the new submission that i was going to post appeared in the data source page. But when I Verify All Connections, it gave the following error message:

Connection verification failed for data source: Teacloud
java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: Data source name not found and no default driver specified
The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: Data source name not found and no default driver specified Text

I am running on Vista Ultimate with DW 8, and CF MX7.0.2. No IIS was installed.

Can someone please advise on how to go about this error?

Thank you very much.
Ash
This topic has been closed for replies.

2 replies

R
rganong
Participant
August 26, 2007
Use the MS Access Unicode driver and it should work ok on Vista.
A
Anonymous
August 13, 2007
First, CFMX7 is not supported on Vista. Although this may have nothing to do with your problem.
If you did not install CFMX7 as admin to the box when you installed CFMX may not have registry permissions to create the datasource. The underlying ODBC datasource is created in the registry just like any other datasource. Are you running CFMX7 from the commandline using cfusionmx7\bin\cfstart? If so, that may be the issue and you need to do this with an admin user.

Workarounds will probably include - create a system datasource to your database using the windows control panel. Then create a datasource in the cfmx7 admin that uses that datasource. The choices would be to use a DSN of type ODBC socket that connects this new windows DSN you just created. A second method is to use the Jadozoom driver which is what is used for Access Unicode DSNs. You can view this technote for instructions.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices