#677 closed defect (invalid)
Error when trying to change the system configuration
Reported by: | johnh | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | v2.7.0 |
Component: | General | Version: | v2.6.3 |
Keywords: | system configuration error | Cc: | johnh |
Description
Hi,
I am running GeoNetwork 2.7.0 on Linux debian platform with amd64. I have logged in as 'admin' and selected the 'Administration' menu option. If I select "System configuration" the input form is shown but when I try to save any changes to the form I get the error:
"Unable to save the system configuration Error : operation-aborted Message : Cannot set all values Class : OperationAbortedEx " I get the same error even if I don't make any changes and select the "save" button.
Thanks.
johnh
Attachments (1)
Change History (8)
by , 13 years ago
comment:1 by , 13 years ago
Milestone: | v2.6.5 → v2.7.0 |
---|
comment:2 by , 13 years ago
Cc: | added |
---|
comment:3 by , 13 years ago
This is a configuration error. You probably have missing settings. Check the settings table.
2011-11-28 11:14:04,167 DEBUG [geonetwork.settings] - Set path: system/metadata/defaultView, value: simple 2011-11-28 11:14:04,167 DEBUG [geonetwork.settings] - Unable to find Settings row.
If you could update to (at least) revision 8121, the debug info contains the missing settings path now : "Unable to find Settings row for: " + path and helps solving that type of issue.
comment:4 by , 13 years ago
Just to explain a bit more:
the settings table represents a hierarchical, tree structure, of the settings. So each setting has a 'parent' setting.
If any ancestor setting is missing, settings can't be saved and you get this message.
In my opinion this implementation is unnecessarily prone to error and we'd be better off replacing it with simple key-value pair settings. The hierarchy is not very useful, and to retain some kind of grouping we could simply use a field 'type' or so.
comment:6 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Move settings changes proposed here to enhancement in ticket #677 and close this ticket as invalid because in this case the database was actually out of date with respect to the settings - see comment by fxp above.
catalina.out errors