For anyone who has the power to investigate this further at MM, the corruption in this case is the DefaultDataSource sneaking back into the neo-query.xml file, presumably when other DS changes are made. Deleting the block of XML that corresponds to that DS allows the server to restart successfully. We haven't been able to find out which type of change is prompting the corruption.
-----Original Message----- From: James Holmes [mailto:[EMAIL PROTECTED] Sent: Tuesday, 7 June 2005 12:41 To: CF-Talk Subject: Neo-query.xml curruption on 6.1 updater Even with 6.1 updater (on CF Enterprise standalone, Solaris 8 on SPARC, Oracle datasources only), we still get regular corruption of neo-query.xml and we need to restore from backups to get the datasource service working. Has anyone made any progress in fixing this? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:208763 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
