Sure enough, the neo-query.xml file contained the DefaultDataSource. The working file now on the server (from a backup) has no DefaultDataSource.
For anyone likely to pass this on to MM, it appears that the DefaultDataSource is periodically re-introduced into the neo-query.xml file by CF when adding legitimate datasources. A fix would be very nice... -----Original Message----- From: James Holmes Sent: Monday, 6 December 2004 11:01 To: CF-Talk Subject: Datasource service not available "The DataSource service is not available." This error still occurs to us every now and then, even with CF 6.1 with the updater. Does anyone know why MM has not bothered to fix the error? I'm going through neo-query.xml now to attempt to find the corruption (if that's where the problem lies this time) but if anyone know of other causes, I'd be happy to hear from you. Our platform is Solaris 8, Apache 2, CFMX 6.1 Updater, Oracle 9i. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - New Atlanta http://www.newatlanta.com Message: http://www.houseoffusion.com/lists.cfm/link=i:4:186266 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
