To confirm if there are dangling references, please navigate to "Administration | Tooling | Script Editor" and run the following script. Replace <yourServiceName> with the name of the problematic service :
===
def hosts = [];
def service = # !FSMService where name = '<yourServiceName>' #.getTopologyObjects()[0];
def topSrv = server.TopologyService;
service.hosts.each{
hosts.add(topSrv.getObject(it.uniqueId));
}
return hosts;
===
Check if a TopologyObjectNotFoundException appears - like the example below:
2011-07-18 07:54:48.058 ERROR [AnonymousTask:136213066013109720880125] scripts.system:foglight_services_catalystalarmstate.Get Filtered Alarm State Progress Tracker (Service or Service Perspective).FilteredAlarmStatesTask - com.quest.nitro.service.sl.interfaces.scripting.ScriptAbortException: script1000716: com.quest.nitro.service.topology.TopologyObjectNotFoundException: Topology Object Not Found: 38a50308-5cff-4c5c-8100-0e6957fe13ba
If the above TopologyObjectNotFoundException appears, please run the attached script "find-dangling-references.groovy" with the "clear" argument to fix the problem. Run the script from the $FMS_HOME/bin directory like this:
fglcmd -cmd script:run -f find-dangling-references.groovy clear