ODBC Service wont run

[arniebld]

Hi guys,

Working on setting up a new server and I need to create a datasource to an
access database. When I try to add the datasource, it tell me "The ColdFusion
MX 7 ODBC Server service is not running or has not been installed."

This is true, the service is not running. When I try to run it, it starts and
the stops and gives me the following message: "The ColdFusion MX 7 ODBC Server
service on Local Computer started and then stopped. Some services stop
automatically if they have no work to do, for example, the Performance Logs and
Alerts service."

Any reason this would happen?

Thanks, Arnie

[arniebld]

I saw in some knowledgeBase article that ODBC service needs ports 19997 & 19998
to run, so I had the host open those ports. No luck. Then I found that MX 7
needs ports 19995 & 19996 (so they dont conflict) and I've had the host open
those ports as well, but it still wont run!

What would cause that?

Arnie

[Mike Greider]

Anything in the logs? Any failures in the installation summary report?

[arniebld]

From the installation summary:

Summary
-------------

Installation: Successful.

85 SUCCESSES
0 WARNINGS
0 NONFATAL ERRORS
0 FATAL ERRORS

and I dont see anything usefull in the logs other than a bunch of messages
about starting various services (in server.log.) The only thing mentioned in
the log is "CORBA Configuration not enabled." Is this related?

[Mike Greider]

Don't think the corba issue is related. Anything in the windows event viewer?

[arniebld]

From the Windows Event Viewer:

(this error occured what I think is the first time coldfusion was run)

ColdFusion MX 7 ODBC Server
The description for Event ID ( 0 ) in Source ( ColdFusion MX 7 ODBC Server )
cannot be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote computer.
You may be able to use the /AUXSOURCE= flag to retrieve this description; see
Help and Support for details. The following information is part of the event:
ColdFusion MX 7 ODBC Server error: 0, StartServiceCtrlDispatcher Error!.

Similar error for the ColdFusion MX 7 ODBC agent.

[Mike Greider]

No messages since that time? Not really sure why this is happening for you.
Perhaps an uninstall/reinstall? I know that is usually the worst case, but I'd
had to resort to that several times in the past.

[arniebld]

Hi Mike, thanks for your help.

I've received that message about the ODBC service many times, that exact
message.

Re-installing the server I dont believe will help. This is the second server
I've had with this problem (other one I got around using ODBC at all) and on
the other server I did re-install coldfusion. Only helped for about a week. I
cant re-install every week.

[Mike Greider]

Let me ask the dumb question. Once you installed, you ran the configuration wizard right?

[arniebld]

I certainly thought I did. Can I run it again?

[Mike Greider]

That, I don't know. You can probably tell by looking through the cfide / administrator directory. I looked briefly, but nothing stood out at me. Could be a registry entry or xml flag or something too.

[arniebld]

I found something in the logs, not sure what it means.

<cf_root>\db\slserver54\logging\ColdFusion MX 7 ODBC Server4156.log

Thu May 19 10:02:35 2005:SLX ODBC Socket. Build 0097
Thu May 19 10:02:35 2005:C21621_56931(4 CPU) - Microsoft Windows 2000(5.2-
(Build 3790))
Thu May 19 10:02:35 2005:Failed to open event trace file because the file
version is not recognised.

there are a bunch of such log files with the same error

[arniebld]

After reading those logs, I decide to look at the trace file. The entire file was blank. I deleted those files, and then restarted the services - and it worked! The files were recreated correctly.

[Mike Greider]

Very weird. Glad you found the problem.

[olllllo]

I experienced the same error out of the blue this morning after our colo rebooted our server. Deleting the trace file and recreating it worked for me as well.

[Unregistered]

I experienced the same error out of the blue this morning after our colo rebooted our server. Deleting the trace file and recreating it worked for me as well.

I've been trying to figure this out for days. Deleting the corrupt trace files did the trick. Thank you!!!