jmaitino, I have news, some may be good, some maybe not.
First, that would be odd, indeed, if (even with that error) a change on one CF Admin page would change SOME but not ALL settings on that page.
As for the error, note the reference to ".xalan.processor.Transformer". As you may know, the CF admin configuration settings are stored in XML files, with a name in teh form of neo-*.xml, in the cfusion/lib folder (or instancename/lib, if you use multiple instances) . In the case of that settings page, I expect most are in the neo-runtime.xml. So you may want to open that, and better try to check out if it's well-formatted.
Sadly, while CF does keep a backup of any changes to the files, it keeps only ONE generation, so you will see a neo-runtime.bak. And that can be updated for any of various reasons, so that you may find your backup file is of no use. Still, make a copy of the two neo-runtime.bak and .xml files you have, to protect them for the next steps. You could then stop CF, rename the current .xml file, and then rename the bak to that, then restart CF and see if the problem is resolved (can you now save changes on that page). Do beware in reverting to the bak this way, you could lose settings you had made that were in the "real" (broken) one and not the "bak"). If that does NOT help, you may want to revert back to the original .xml you had.
But maybe you can find a backup made by your OS or some software, and then you could try that (again, you need to stop CF, put in the restored neo-runtime.xml file, and then start CF and test things).
The bummer about all this is that there can be occasions when the XML files become corrupt--it sometimes happens when people kill CF (rather than stop it gracefully, or when that does not work), or when CF crashes, or the box is rebooted and CF is not able to shitdown gracefully. Again, it's a bummer both that there is just the one generation backup (I have filed a feature request asking them to keep more), and that there's no provision for better-detecting corupted files or easily reverting to the backup.
Finally, if you are absolutely stuck, as a last resort you could also rename the neo-runtime.xml (while CF is down) and start CF. It will create a new version, set to the defaults. At least then you could proceed to make your intended updates--but again you will have lost all the changes you made before, that were stored in that file.
I will note that there is (since CF10) an audit.log, found in the CF logs folder, which tracks many (not all) changes made in the CF admin. It doesn't track all the details for every change it does track, but it could help you to at least be reminded of some things that WERE changed.
Again, the best thing would be if you had a backup you could revert to.
Let us know if any of this gets you going.
/Charlie (troubleshooter, carehart.org)
1 Correct answer
12
Replies
AdChoices