Object #<number> has parent #<number>, which does not exist.

book

Article ID: 4136

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) AXIOMATICS POLICY SERVER CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On

Issue/Introduction

The Validation Process during the running of most XPS Tools returns errors in the following format:

 

 

[CA.XPS.EDIT0050][ERROR] Object #<number> has parent #<number>, which does not exist.

 

EXAMPLE:

 

[CA.XPS:EDIT0050][ERROR] Object #4254 has parent #4252, which does not exist. 
[CA.XPS:EDIT0050][ERROR] Object #15788 has parent #15786, which does not exist. 


Cause

Each error represents an object in the Policy Store which has a Parent attribute populated with the XPSNumber, however that XPSNumber does not exist in the policy store.  This is an 'Orphaned Object'.

 

Environment

Policy Server: r12.5; r12.51; r12.52Policy Server OS: AnyPolicy Store: LDAP

Resolution

1) Perform an LDIF Export of the Policy Store using the LDAP Admin tools for your LDAP Directory Server.

2) Search the .ldif export file for the first orphaned object by XPSNumber.

example:

Search: xpsNumber=0000004254

Result:

# entry-id: 475051
dn: xpsNumber=0000004254,ou=XPS,ou=policysvr4,ou=siteminder,ou=netegrity,dc=ca,dc=com
objectClass: top
objectClass: xpsObject
xpsNumber: 0000004254
xpsCategory: 2
xpsClass: 30
xpsGUID: 0f-588f61a6-979e-4ba7-8a15-9bb89a1916bd
xpsSortKey: 2-0000004254
xpsUpdateBy: siteminder
xpsUpdateMethod: 5
xpsParent: 4252
creatorsName: cn=smadmin,dc=ca,dc=com
modifiersName: cn=smadmin,dc=ca,dc=com
createTimestamp: 20120521121229Z
modifyTimestamp: 20120521121229Z
entryUUID: 362c53ad-a33e-11e1-8032-d83ee7ab2ab9

 

3) Record the DN

4) Using the Resource Identifier (RID) populated in the xpsGUID value from the XPSNumber object, search for the objects tied to that XPSNumber.

example:

Search: 0f-588f61a6-979e-4ba7-8a15-9bb89a1916bd

NOTE: There are often two objects that get returned.  xpsXID is not always returned for all objects.

Result:

# entry-id: 475050

dn: smUserPolicyOID4=0f-588f61a6-979e-4ba7-8a15-9bb89a1916bd, smPolicyOID4=04-
 20890dec-3df0-4972-b144-1bd5c57a4594, smDomainOID4=03-7df7ae7b-e4d1-4542-b88
 1-81f98cc783b9, ou=PolicySvr4,ou=SiteMinder,ou=Netegrity,dc=ca,dc=com
objectClass: smuserpolicy4
objectClass: top
smUserPolicyOID4: 0f-588f61a6-979e-4ba7-8a15-9bb89a1916bd
smPolicyOID4: 04-20890dec-3df0-4972-b144-1bd5c57a4594
smDomainOID4: 03-7df7ae7b-e4d1-4542-b881-81f98cc783b9
smUserDirectoryOID4: 0e-4a8a9298-91c8-4a32-8c5e-5ff3edde9ab0
smFilterPath4: All
smFilterClass4: All
smPolicyResolution4: 7
smPolicyFlags4: 0
creatorsName: cn=smadmin,dc=ca,dc=com
modifiersName: cn=smadmin,dc=ca,dc=com
createTimestamp: 20120521121229Z
modifyTimestamp: 20120521121229Z
entryUUID: 362c53ac-a33e-11e1-8032-d83ee7ab2ab9

 

# entry-id: 475052

dn: xpsXID=CA.SM::[email protected],ou=XPS,ou=policysvr4,ou=siteminder,ou=netegrity,dc=ca,dc=com
objectClass: top
objectClass: xpsXIDKey
xpsXID: CA.SM::[email protected]
xpsIndexedObject: xpsNumber=0000004254,ou=XPS,ou=policysvr4,ou=siteminder,ou=netegrity,dc=ca,dc=com
creatorsName: cn=smadmin,dc=ca,dc=com
modifiersName: cn=smadmin,dc=ca,dc=com
createTimestamp: 20120521121229Z
modifyTimestamp: 20120521121229Z
entryUUID: 362c53ae-a33e-11e1-8032-d83ee7ab2ab9

 

5) Record the Distinguished Names (DNs)

6) Delete the following DNs

xpsNumber=0000004254,ou=XPS,ou=policysvr4,ou=siteminder,ou=netegrity,dc=ca,dc=com

smUserPolicyOID4=0f-588f61a6-979e-4ba7-8a15-9bb89a1916bd, smPolicyOID4=04-
 20890dec-3df0-4972-b144-1bd5c57a4594, smDomainOID4=03-7df7ae7b-e4d1-4542-b88
 1-81f98cc783b9, ou=PolicySvr4,ou=SiteMinder,ou=Netegrity,dc=ca,dc=com

xpsXID=CA.SM::[email protected],ou=XPS,ou=policysvr4,ou=siteminder,ou=netegrity,dc=ca,dc=com

 

Repeat until the errors are no longer returned when validation is run during the execution of various XPS Tools.