CF 8 ODBC server service required after CF 9 migration

Report · May 25, 2010

Today I installed CF 9 (standard edition) and migrated my CF 8 settings to the new install. Everything appeared to go fine, no errors or hangs.

Now, when the CF 9 services are running and the CF 8 services are stopped, all data sources that use an ODBC Socket driver stop working. The error when test the connection using the Verify tool in the CF Admin data sources page is:

Connection verification failed for data source: voyager
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.

However, if I start the CF 8 ODBC server service and the CF 9 ODBC server service, the ODBC data sources work just fine.

Q1: Why would this be?

Q2: Is it safe for me to run both the CF 8 and CF 9 ODBC server service simultaneously?

Thanks,
Lori

Report · May 25, 2010

It is because of these types of wierd cross over errors, that I now completely uninstall the previous version of ColdFusion and install a clean, new version when I do a major upgrade.

I can only suspect that somehow or the other, the ODBC services got cross wired.

Report · Jul 12, 2010

Search your system for a file called "derby.properties". I suspect you'll find 2 copies. One for CF8 and one for CF9. Open them both and compare the line "derby.drda.portNumber=".

Is the port number the same? My guess is no.

Stop all instances of the ODBC server/agent and your CF instance(s). Find the file called "neo-drivers.xml" in your CF9 install and make a copy of it.

Now, open it and search for the number you see in your CF8 install's derby.properties file (in this case, mine is port 1527). Modify that value to what ever the port number is in your derby.properties file for your CF9 install.

Start up CF9 and the CF9 related odbc services and test your connections.

I think you should be good to go (I've got no easy way to test this since I'm on 64 bit editions and ODBC support is gone in 64 bit). If you break anything, simply reinstate your copy of neo-drivers.xml after stopping CF and ODBC services.