That was a bug in the initial release of CFMX, but the fix should have been included in Updater 1. If you've apply either Updater 1 or 2, it should straighten it out.
Debbie -----Original Message----- From: Lawrence B. Afrin, M.D. [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 10:36 PM To: CF-Talk Subject: CFMX problem: undeleteable datasource? Howdy -- We've been preparing to upgrade our CF5-Linux production platform to CFMX-Linux, and on our test server where we've been testing the upgrade process, we've run into a curious snag: Our test CF5-Linux platform included an ODBC datasource -- call it "goober" -- which was using the Merant Text Driver. Following the application of the CFMX Pro upgrade, we found that the new JDBC-equivalent "goober" is listing in the CF Administrator as having a JDBC driver type of "ODBC socket". Rather curious, since "ODBC socket" isn't one of the JDBC drivers that comes with CFMX-Linux Pro (you only get SQL Server and MySQL). (Also, not surprisingly, an attempt to verify a connection to "goober" is failing, but we don't care about that at this point.) Furthermore, attempts to delete the "goober" datasource simply result in the following error: ----------------------------- An exception occurred when invoking an external process. The cause of this exception was that: java.io.IOException: \opt/coldfusionmx/db\slserver52\admin\swcla.exe: not found. The Error Occurred in /home/httpd/html/CFIDE/administrator/datasources/_sl52del.cfm: line 10 Called from /home/httpd/html/CFIDE/administrator/datasources/odbcsocket.cfm: line 16 Called from /home/httpd/html/CFIDE/administrator/datasources/odbcsocket.cfm: line 760 Called from /home/httpd/html/CFIDE/administrator/datasources/_sl52del.cfm: line 10 Called from /home/httpd/html/CFIDE/administrator/datasources/odbcsocket.cfm: line 16 Called from /home/httpd/html/CFIDE/administrator/datasources/odbcsocket.cfm: line 760 ----------------------------- We also tried to delete the "goober" datasource by deleting its XML declaration in .../servers/default/SERVER-INF/jrun-resources.xml, but regardless of whether we restarted the CFMX server or even rebooted the whole machine, this change didn't seem to affect the continued listing of "goober" in the Administrator, Datasources page. We tried to figure out (by searching the system and searching JRun and JDBC documentation) where else within the Linux filesystem the JDBC datasources are defined or listed (i.e., where does the CF Administrator, Datasources page get its listing of datasources from?), but it's a mystery to us. Anybody have any ideas about how we can get rid of "goober"? It'd be kinda silly to have to pay MM the $500 incident support fee to get a fix for their own upgrade-process bug. TIA... -- Larry Afrin Medical University of South Carolina [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
