Please contact technical support if you have had debug logging inside the GPOADmin Options available before the issue occurred. If you ran into the problem without debug logging enabled, enable debug logging now via the GPOADmin Options. Should you experience the issue again, please send the debug logs to technical support.
Workaround
1. Make note of the GPOADmin ID for the affected object and navigate to the storage location of the Version Control Root (such as in Active Directory).
NOTE: The GUID/ID of the affected object can be found by viewing the properties of the object in GPOADmin console (Right-click Object > Properties).
The GPOADmin GUIDs can be found inside the VCRoot container inside AD/ADLDS. All data is stored inside the Configuration partition under CN=Services, CN=Quest (expand to the VCRoot folder).
2. Locate the GPO using the GPOADmin ID and open its properties.
A quick way to find this is to right-click the "Configuration" node > New > Query.
Form the query such that it searches for CN={GPOADmin ID including brackets}.
Right-click the only result, and go to Properties.
3. View/Edit the attribute monikerDisplayName and change the Status value to Status= .
4. Refresh the GPOADmin console.
In scenarios where this does not resolve the issue, take the following actions on the MonikerDisplayName attribute:
Change the Status value to "Status=Available".
Change the Substatus value to "Substatus=None"
Change the ApprovalState value to "ApprovalState=".
Change the ApprovedByList value to "ApprovedByList=".
Change the ApprovalRequester value to "ApprovalRequester=".
You should now be able to work with the GPO again.
