bpurcell.org - Enabling Seguelink debugging in CFMX
Calendar
SunMonTueWedThuFriSat
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
31            

Subject Archives
Amazon EC2 (15)
ColdFusionMX (155)
Corvette (3)
Flash Lite (4)
Flash Media Server (5)
Flash Player (3)
Flex (39)
General Web Dev (14)
HDTV (3)
Jboss (1)
Jquery (2)
JRun (59)
Max 2003 (3)
Other (33)
PC Hardware (16)
Software (17)
SpatialKey (7)
Wireless (8)
Working Out (1)

RSS Feed
Feed Listing

Site Contents
Home
My Blog
ColdFusion
JRun
Flex
Wireless & Networking
Hardware & Gadgets
HDTV
Software Picks
Pictures
Contact Me
Search


My Articles & Papers
Flex Performance
Server/Client
mm.com Under the Hood
Multiple Instances of CFMX
Multiple Instance Config
NLB with ColdFusion
Clustering CFMX for J2EE
Multi-Tier Hardware LB w CFMX
Cisco CSS & Coldfusion MX
JRun 4 Jini based Clustering
WiFi Growth

2ID Tacweb

Other Hobbys
Body-For-Life Challenge

Personal Projects
Family Pool
Deck Gate

username:
password:
 

 
Viewing Individual Entry / Main
May 23, 2003

To enable Seguelink debugging:

1. Stop the ColdFusion MX ODBC Agent and ColdFusion MX ODBC Server service

2. Delete any log files in the C:\CFusionMX\db\slserver52\logging directory.

3. Start theColdFusion MX ODBC Agent and ColdFusion MX ODBC Server service.

4. Open up a command prompt and cd to CFusionMX\db\slserver52\admin.

5. Type the command swcla -l ( This changes the prompt to swcla> )

6. Enter the following:

sdll "ColdFusion MX ODBC Server" debugging=on fatalerror=on ssppackets=on ssprequests=on warnings=on errors=on informationals=on

7. Enter sdll "ColdFusion MX ODBC Server" ( This should output a table like the following verifying the loglevel state )
-----------------------------------------------------------------
Debug log level for ColdFusion MX ODBC Server
-----------------------------------------------------------------
Level State
-----------------------

fatalerror on
errors on
warnings on
informationals on
debugging on
ssppackets on
ssprequests on
swcla>

8. Run the query or test ( This creates a "ColdFusion MX ODBC Server_xxx.log" in the C:\CFusionMX\db\slserver52\logging directory )

Note: The above log files created with debugging grow quickly so debugging should be disabled after the test.

9. Stop the ColdFusion MX ODBC Agent and ColdFusion MX ODBC Server service

10. Start the ColdFusion MX ODBC Agent and ColdFusion MX ODBC Server service

11. Open up a command prompt and cd to CFusionMX\db\slserver52\admin.

12. Type the command swcla -l ( This changes the prompt to swcla> )

13. Enter the following:

sdll "ColdFusion MX ODBC Server" debugging=off fatalerror=off ssppackets=off ssprequests=off warnings=off errors=off informationals=off

Comments

Brandon,

Your blog and the official tech-doc (http://www.macromedia.com/support/coldfusion/ts/documents/debug_sequelink.htm) are wrong??

They both have you turn OFF all settings when you are done, when the default is to leave FATALERROR and ERRORS =on.

I checked against 2 fresh CFMX6.1/JRUN4(updater3) installs today and they both had fatal/errors=on as the default.

Sadly, even with default I am not getting any useful info in the logs. Turning on full debug now.

-

Do you have any idea what I do with the .DMP file in the slserver52\logging directory to help fix problems?

-

What about the .INP file in the \admin\ directory? They seem informative, but not useful to me

alc dsd 'ColdFusion MX ODBC Server' 'policy2004' dsc 'ColdFusion MX ODBC Server' 'policy2004' dsar 'ColdFusion MX ODBC Server' 'policy2004' DataSourceSOCODBCConnStr dsn='policy2004' dsaa 'ColdFusion MX ODBC Server' 'policy2004' DataSourceFetchTimeStampAsString Yes dsar 'ColdFusion MX ODBC Server' 'policy2004' DataSourceLogonMethod DBMSLogon(UID,PWD) dsi 'ColdFusion MX ODBC Server' 'policy2004' cc


 
Page Render Time:203