Troubleshooting Groups
The following subsections offer possible solutions to problems encountered by users working with groups. Although these subsections attempt to be comprehensive, there is no way to anticipate all possible problems or solutions a user might encounter when working with groups.
I created a hierarchy in the Group Manager, but I don't see facilities.
Here are likely possibilities:
- The Group Manager utility does not display actual facilities, even when you've performed a build for its hierarchies. It only displays the abstract structure of your hierarchy. However, the Group Service Explorer displays the actual ("as-built") hierarchies, including all relevant facilities. Open the Group Service Explorer to view relevant facilities.
- If you are in the Group Service Explorer but still don't see facilities, facility attributes might be misconfigured. Open a missing facility in the Facility Service (FAC) and double-check its Attribute, Description, and Value columns to ensure that the correct information is there. If your attributes are incorrect, you might need to add correct values and/or add correct attributes. Be sure to rebuild your hierarchies in the Group Manager utility to implement changes.
- If you double-checked and/or edited facility attributes in the FAC and they are correct but desired facilities still do not appear in your as-built hierarchy in the Group Service Explorer, carefully review and correct rule definitions to ensure that the desired facilities are included in your hierarchies.
My built hierarchy doesn't collect data from all of the facilities I expect.
Most likely, you have not set up your facility attributes correctly or have not set up your levels correctly, particularly rule-based levels. Carefully review and/or edit facility attributes to make sure they are correct and carefully revise level definitions(s) (rules and/or components) at the level of the missing data.
I changed facilities, devices, or other GRP components, but they aren’t reflected in my group hierarchy.
If you add, edit, or delete facilities and/or devices and you want the result reflected in your group hierarchies, use the Group Manager utility to rebuild the affected hierarchies. Doing so includes the changes in the GRP and ensures that these changes appear on CygNet Studio or CygNet Vision screens, in reports, and so forth.
I deleted facilities and/or devices, but they are still in the GRP.
If you delete facilities and/or devices from your system and they had GRP entries (that is, they were once part of a GRP build), manually delete these entries from the GRP.
I deleted a node from the Group Manager but it is still in other GRP components.
If you delete a node from the Group Manager, you probably only need to refresh the affected component to see the result.
I deleted an administrative node from the GRP and now my hierarchy won’t build because of the missing node even though all of its child nodes still exist.
Important: Best practice recommends not modifying nodes directly in the GRP. It is best to make GRP changes using the Group Manager utility.
If you do delete a required (usually administrative) node, you have at least two options:
- Manually recreate the node in the GRP and reassociate it with its parent and child(ren). The Group Manager utility will not recreate an administrative node once you have deleted it from the GRP even if you rebuild.
- Delete the node’s children and recreate the mistakenly deleted node and its children in the Group Manager, then rebuild all.
I'm not sure that my rollups are working.
Once you have created and configured required summary GRP nodes, calculation target points, and rollup HyperPoints, check the results of your work to ensure that the rollups are operating correctly. Perform at least one of the two steps listed below. There might be additional ways to check your work besides those provided here.
- Using CygNet Explorer, open the appropriate UIS and locate a subset of UDC/facility combinations affected by a rollup.
- Make a manual calculation of all child leaf nodes (facilities) of a summary group node to see if the calculation equals that of the summary group node displayed in the UIS. This might include consideration of child summary group nodes.
Example
If Summary Node A is configured to calculate a total of the CFGCO UDCs of two child leaf nodes (facilities), add the values for those two UDCs and compare it to the Summary Node A value for the same UDC. If the manually calculated value and the UIS-calculated are the same, Summary Node A is totalizing the two leaf nodes correctly.
To Check Results in an HSS
- Using CygNet Explorer, open the appropriate HSS and locate a subset of UDC/facility combinations affected by a rollup.
- Check the combinations' Value columns. If the value in the columns is "SUCCESS", your rollup HyperPoint (summary group node) is probably operating correctly. If another value is displayed, see Error Messages.
Note: "SUCCESS" does not guarantee that the actual values reported to the affected UIS are what you require. It is safest to also check values in the UIS.


