CF9 ODBC (microsoft access) DSN's not working

[Capt Obvious]

I am having issues with the Microsoft Access DSN’s on a cf9 server (windows 2000)

Here is the original problem I had after upgrading from CF8 to CF9, which as you can see I solved

http://russ.michaels.me.uk/index.cfm/2010/3/5/Microsoft-Access-DSNs-no-longer-working-after-upgradin...

However since upgrading to cf9.0.1 it has stopped working again and I cannot figure out why this time, and none of my fellow CFGURU's have been able to shed any light either, thus why I am posting here as a last resort.

The ODBC services are running

The ports in swandm.ini are still correct

Nothing in D:\ColdFusion9\db\slserver54\logging

However every site is giving the error

[Macromedia][SequeLink JDBC Driver]TCP/IP error, connection refused.

And when editing a dsn in the cfadmin I get

The ColdFusion ODBC Server service is not running or has not been installed. You may also use the "MS Access with Unicode" driver to connect to MS Access datasources

Anyone got any ideas?

[tclaremont]

Have you switched to the unicode driver? I had to do that when I moved from 7 to 8. I have no idea why that was the case, but it worked so I

did not argue.

Better yet, move to a better database!

[Capt Obvious]

no, as this would mean manually updating hundreds of DSN's and users no

longer having the ability to create DSN's themselves, so this is not really

a viable solution.

Russ

[tclaremont]

I think you can programmatically change the database drivers, so theoretically you could automate the process. Can you change a single datasource and at least prove that the theory works?

I am curious why you say that users would not be able to create DSNs themselves if you went this route. What is the issue?

[Capt Obvious]

because the control panel does not support the msaccess with unicode driver.

Russ

[Capt Obvious]

I have made some progress, I have now just noticed something new.
It is only new DSN's (created via my  adminapi) that are not working.
Existing MSACCESS DSN's are actually still working, they will verify ok from the cfadmin , I just cannot edit them  as I get the error stating the service is not running,

So I checked out the neo-datasource.xml to see what is the the difference between an old DSN and a new DSN, and I noticed this.

<var name="url">
   <string>jdbc:sequelink:msaccess://localhost:20000;serverDatasource=111</string>
</var>

if I look at the old still working DSN's I see

<var name="url">
   <string>jdbc:sequelink:msaccess://localhost:19998;serverDatasource=PCK;MaxPooledStatements=1000</string> 
</var>

So it appears that the CFADMIN is using the wrong port to connect to the ODBC service and to create DSN’s, since the update, so if I can find where this port setting is coming from then I think I will be able to fix it.
It is nowhere in the db/ folder, the port setting in the ini files are correctly using 19998, not been able to fidn any other settings so far relating to this.