Forta.com - Blog

Comments

Hi Ben,
My CFMX 6.1 Server on Win2k has been crashing every day now and getting worse. This is my error is windows evnet log
The description for Event ID ( 0 ) in Source ( ColdFusion MX 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. The following information is part of the event: ColdFusion MX ODBC Server@LOCALHOST,ErrorCode=3059,ErrorMessage=The specified data source is not defined.,ClientHost=127.0.0.1,Session=599.

Below is my debug log
Tue Mar 23 16:39:09 2004:SLX ODBC Socket. Build 0081
Tue Mar 23 16:39:09 2004:Connection request from 127.0.0.1:1957
Tue Mar 23 16:39:09 2004:HALO(2 CPU) - Microsoft Windows 2000(5.0-Service Pack 4 (Build 2195))
Tue Mar 23 16:39:09 2004:The specified data source is not defined.

Is this the cause of my ODBC crashes? how do I identifty and solve this problem. I have tried reinstalling the ODBC services sequelink in the registry and a lot more.

Please help if you can or at least point me in the right direction.

Cheers Ben

# Posted By Steve O'Neill | 3/23/04 8:41 PM

add onto my last blog

Mon Mar 22 19:16:55 2004:SLX ODBC Socket. Build 0081
Mon Mar 22 19:16:55 2004:HALO(2 CPU) - Microsoft Windows 2000(5.0-Service Pack 4 (Build 2195))
Mon Mar 22 19:16:55 2004:The active request for session 5014 is interrupted due to an unexpected exception
Mon Mar 22 19:16:55 2004:sched.swschd.1753.Internal error, an unexpected exception was detected.

# Posted By Steve O'Neill | 3/23/04 8:46 PM

Thanks for the tip.

The tech-doc is wrong. It has you turn OFF all settings when you are done, when the default is to leave FATALERROR and ERRORS =on.

Strangely our crashing/hung ODBC server/agent services are not logging anything with the default setting. I will be trying the all=ON option this week to see if the large debug logs yield anything.

# Posted By brian | 8/10/04 4:56 PM

Hi,

I am getting a very generic error after installing ColdFusion Enterprise edition 30-day trial. Windows 2000 Adv Server

The ColdFusion MX ODBC server won't start.

I followed the instructions according the link you provide and I get an error when I type in swcla -l

[SequeLink error 2306] TCP/IP error connection refused
[SequeLink error 6853] Failed to access configuration at HOSTNAME:19997

I goolged this and searched the KB on Macromedia with no luck...any ideas?

# Posted By Joe Genshlea | 9/4/04 1:07 AM

Hello Steve;
regarding the CFMX6.1 ODBC problem on Win2k.
We have a similar problem with CFMX6.1 on Windows 2003 Server with IIS 6.0.
We found the following characteristics, when a CF Server Crash happens: The CF MX ODBC Server Service could not be restarted and the process swstrtr.exe could not be killed from the memory. The only way: Restart the complete server.
Did you find a solution for your problem in the meantime?

regards frank

# Posted By frank winkelmann | 10/25/04 9:00 AM

Steve, et. al.

Sorry to google into an old thread...but...

I am having the same Event ID (0) error, but am also getting fatal server errors...

...
sched.swschd.943.Internal error, fatal server error detected.
...

and i get about thirty of these errors upon restart of the service...

any ideas?...

# Posted By dave powell | 2/23/05 12:30 PM

I have the same problem (Win 2003 server) where swsoc becomes unresponsive. Instead of restarting the whole server though, I've been using the following in a batch file:

taskkill /F /IM swsoc.exe /T
net stop "ColdFusion MX 7 ODBC Server"
net start "ColdFusion MX 7 ODBC Server"

which allows users to maintain sessions and restarts the ODBC server.

# Posted By Mark Beaches | 10/5/05 1:57 PM

I know this is a very late response (it's 2006 now), but I was able to solve the ODBC Agent not starting by deleting the 'tracing' folder and recreating it:
<cfroot>\db\slserver54\tracing

Hope this helps...

# Posted By Rob | 3/31/06 8:23 PM

Running ColdFusion MX 6.1, trying to connect to a Progress database using the Merant Progress 9.1D ODBC driver:
When adding a CF datasource using generic ODBC, I encountered an error in the slserver52 logs stating "The specified data source is not defined."

Every time I tried to verify the datasource, a new copy of swcla would spawn and hang indefinitely.

I tried running swcla from the command line and entered the commands stored in the <dsn>.inp file created in <cfroot>\db\slserver52\admin folder. I got an error stating "Error 6522: Failed to load MGSS mechanism."

Upgrading the SequeLink software from v5.2 to 5.4 fixed it:
http://www.macromedia.com/cfusion/knowledgebase/in...

# Posted By Derek | 4/6/06 2:33 PM

Mark Beaches - Can't tell you how much I appreciate the tip! Thank You!!!

# Posted By Jeff | 8/16/06 3:49 PM

Derek, thanks for your post, it really helped me out. Upgrading SequeLink cleared up my ODBC Server timeout issues I was having when trying to add an ODBC Socket datasource.

# Posted By Ryan Stille | 4/13/07 12:23 PM

[Add Comment]

TechNote: Enabling debugging for DataDirect SequeLink Server ODBC Services