i think we have seen this issue before and it's due to bad data in the enumeration property values. did you open a ticket on this w/ support yet ?
Bill, seemingly it is the 'blcontent' process which corrupts some property data - according to support.
I have applied SP1 which sadly did not fix the issue, so support are currently writing me an SQL script which should correct the offending entries. Fingers crossed.
The issue w/ blcontent was fixed in 8.2 SP1, but there was no remediation in that release, so if you had already ran blcontent, upgrading would not fix anything.
having same issue on 8.5, my custom Server property (Enum value) has over 130 values, some with double quotes in the value. After adding additional values, it reaches a point where I cant open it for editing anymore.
Theres a certain max # of values you can give to each Enum Value Property before it becomes unavailable for editing. Not sure if this is a data limit or if my console doesnt have enough memory to open the window for editing.