Skip to main content
C
Capt Obvious
Inspiring
August 31, 2010
Question

CF9 ODBC (microsoft access) DSN's not working

  • August 31, 2010
  • 1 reply
  • 3035 views

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-upgrading-to-ColdFusion-9

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?

    This topic has been closed for replies.

    1 reply

    tclaremont
    tclaremont
    Inspiring
    August 31, 2010

    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!

    C
    Capt ObviousAuthor
    Inspiring
    August 31, 2010

    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
    tclaremont
    Inspiring
    August 31, 2010

    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?

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