AgentInstance Objects Have Invalid Attribute Values
search cancel

AgentInstance Objects Have Invalid Attribute Values

book

Article ID: 259447

calendar_today

Updated On:

Products

SITEMINDER

Issue/Introduction

You may run an XPS tool such as XPSSweeper, XPSExport, XPSImport, XPSExplorer and see errors similar to the following

[Validate.cpp:1055][IXPSObjectV1::CheckForDanglingObjects][WARN][sm-xpsxps-03491] CA.SM::AgentInstance@PS-0000000000000000000000004f73a8c0-webprod5-aSlNwAuqeHtjiIq2qvt7mNN7MMXhtgoi8MjSwSPgfr8=: AgentInstance[] has an attribute named 'ACOLink' that points to an object of type 'AgentConfig' that does not exist. (The unique ID of the AgentConfig object being pointed to is #1150481580)

[Validate.cpp:1055][IXPSObjectV1::CheckForDanglingObjects][WARN][sm-xpsxps-03491] CA.SM::AgentInstance@PS-000000000000000000000000e173a8c0-extwebprod2-nQbLSssWbzLLEXC+EW45KWqwHsez07WeM7Psy7f5HWU=: AgentInstance[] has an attribute named 'TrustedHostLink' that points to an object of type 'TrustedHost' that does not exist. (The unique ID of the TrustedHost object being pointed to is #1123624380)

Environment

SiteMinder Policy Server

Release : 12.8.x

Cause

When Agent Discovery is enabled on the policy server and a web agent connects to the policy server for the first time, an AgentInstance object is created.  Then, at a later time an object such as an Agent Configuration Object (ACO) or a TrustedHost object is deleted from the policy store.  The errors (above) are indicating that the AgentInstance object has the 'TrustedHost' attribute pointing to the XID of an Trusted Host object that no longer exists in the policy store.  In the other example (above) the AgentInstance object is pointing to an ACO which no longer exists.

Resolution

The Agent Instance objects in the error need to be deleted from the Policy Store.  This can either be done through the AdminUI or through XPSExplorer.  At the minimum, the Agent Instance objects which are returning errors during XPS Validation need to be removed.  You can simply remove ALL Agent Instance objects.  The next time an agent connects to the policy server, a new Agent Instance object is created.

If there is no valid Agent Instance object in the policy store when the agent connects, the policy server will simply create a new one.  Deleting agent instances have no direct bearing on active agents.  Deleting the agent instance does not delete the agent, agent object, or any functionality or transactional flow.  Deleting Agent Instance objects is completely safe in a running environment.

Additional Information

6/23/29 David M fixed some spelling errors