Skip to main content
Participant
April 20, 2006
Question

ODBC server & agent won't start - J2EE install

  • April 20, 2006
  • 1 reply
  • 333 views
Hi all,

I have installed the developer edition of CFMX7. I have tomcat running on my windows2000 server, so I downloaded the windows installer and chose the J2EE-war option. It runs just fine.

I also installed the ODBC server, because I want to connect to MS Access databases with my developer edition. For that, I tried this: http://www.bpurcell.org/blog/index.cfm?mode=entry&entry=860. First problem was that after tomcat automatically deployed the war file, the folder 'SequeLink Setup' did not exist in the web-inf\db folder. So I renamed the war to zip, and checked - the file is present in the war. So I manually extracted the zip to a new directory. I ran the cfm script with the reference to this new directory, and the ODBC services were installed - hurray!

But now the services do not want to start. I first got the error that the file was not found. It referenced to a slserver52 folder, which had only two directories called 'logging' and 'tracing', but no bin files whatsoever. There is however a slserver54 folder, which contains all kind of stuff. So I started regedit and changed all the references to 52 in 54, and rebooted the server. Still no luck: now I get a 1067 error on the server and an unknown error on the agent.

Any ideas??
    This topic has been closed for replies.

    1 reply

    Participating Frequently
    April 20, 2006
    Manual configuration of ODBC may help.
    Here is a Technote if you'd like to try.
    Participant
    April 21, 2006
    That is just what I did, but that didn't help. The installer creates services that point to the slserver52 folder, but that should be slserver54. When I change the directory in the registry, the services won't start. The ODBC Agent sais:
    "Could not start the ColdFusion MX ODBC Agent service on Local Computer. The service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists, please contact your system administrator."
    The ODBC Service returns the exact same error.