Layer7 Access Management

Expand all | Collapse all

XPSSweeper errors after IDM objects import from SM V12.0 to V12.52

  • 1.  XPSSweeper errors after IDM objects import from SM V12.0 to V12.52

    Posted 02-21-2017 12:14 PM

    Hello Support,

    I had imported IDM objects from V12.0 to V12.52 SMPS as part of migration effort and see lot of errors in XPSSWeeper on V12.52 after the import. Below are the errors that i notice in the XPSSWeeper.

     

    Appreciate your advice and help on this...

     

    (ERROR) : [CA-SM-Assert] CA.SM::IMSEnvironment@35-000569e8-5fed-14e9-9941-06e40ab440a7(IDM126sp2_Test): Assert failed: pLink
    (ERROR) : [sm-xpsxps-05750] Invalid Object: CA.SM::IMSEnvironment@35-000569e8-5fed-14e9-9941-06e40ab440a7(IDM126xxxx).
    (ERROR) : [sm-xobsm-01110] CA.SM::IMSManagedObject@33-0000ff0a-03ee-11f0-a82a-06e40ab4d024(Global User): [CA.SM::IMSManagedObject.AdditionalPropertiesLink]: Invalid attribute: [CA.SM::IMSAdditionalPropertiesSet@20-00059977-03ee-11f0-a82a-06e40ab4d024].
    (ERROR) : [CA-SM-Assert] CA.SM::IMSManagedObject@33-0000ff0a-03ee-11f0-a82a-06e40ab4d024(Global User): Assert failed: pLink
    (ERROR) : [sm-xpsxps-05750] Invalid Object: CA.SM::IMSManagedObject@33-0000ff0a-03ee-11f0-a82a-06e40ab4d024(Global User).
    (ERROR) : [sm-xobsm-01110] CA.SM::IMSManagedObject@33-000673b6-ec58-1548-96b2-06e40ab440a7(Organization): [CA.SM::IMSManagedObject.AdditionalPropertiesLink]: Invalid attribute: [CA.SM::IMSAdditionalPropertiesSet@20-000b9e08-ec58-1548-96b2-06e40ab440a7].
    (ERROR) : [CA-SM-Assert] CA.SM::IMSManagedObject@33-000673b6-ec58-1548-96b2-06e40ab440a7(Organization): Assert failed: pLink
    (ERROR) : [sm-xpsxps-05750] Invalid Object: CA.SM::IMSManagedObject@33-000673b6-ec58-1548-96b2-06e40ab440a7(Organization).



  • 2.  Re: XPSSweeper errors after IDM objects import from SM V12.0 to V12.52

    Posted 02-21-2017 07:38 PM

    It looks like you have a new Policy Store for R12.52. By default the IDMObjects.xdd is not imported when setting up a policy store. Did we run "XPSDDInstall xps/dd/IdmSmObjects.xdd" on R12.52 Policy Server / Policy Store before importing the IDM objects from V12.0 to V12.52.

     

    Hubert



  • 3.  Re: XPSSweeper errors after IDM objects import from SM V12.0 to V12.52

    Posted 02-21-2017 09:42 PM

    Hi Dennis,

    Yes, the default IDM objects have been imported prior to importing the actual objects which were exported from 12.0.



  • 4.  Re: XPSSweeper errors after IDM objects import from SM V12.0 to V12.52

    Posted 02-21-2017 10:31 PM

    It seems like we have 3 objects which are in a corrupted state.

     

    OBJECT-2 & 3 show "Invalid attribute". It seems like the Data Definition does not support that attribute "CA.SM::IMSAdditionalPropertiesSet" OR the value is improper. My recommendation is to cross verify the Data Definition (using IdmSmObjects.xdd) with XPSExplorer. May be we'd get some hint there.

     

    OBJECT-1 I'd check using XPSExplorer to see if all mandatory attributes are populated. If it is possible to delete and recreate, that'd be another option to pursue.

     

     

    OBJECT-1

    (ERROR) : [CA-SM-Assert] CA.SM::IMSEnvironment@35-000569e8-5fed-14e9-9941-06e40ab440a7(IDM126sp2_Test): Assert failed: pLink
    (ERROR) : [sm-xpsxps-05750] Invalid Object: CA.SM::IMSEnvironment@35-000569e8-5fed-14e9-9941-06e40ab440a7(IDM126xxxx).

     

    OBJECT-2
    (ERROR) : [sm-xobsm-01110] CA.SM::IMSManagedObject@33-0000ff0a-03ee-11f0-a82a-06e40ab4d024(Global User): [CA.SM::IMSManagedObject.AdditionalPropertiesLink]: Invalid attribute: [CA.SM::IMSAdditionalPropertiesSet@20-00059977-03ee-11f0-a82a-06e40ab4d024].
    (ERROR) : [CA-SM-Assert] CA.SM::IMSManagedObject@33-0000ff0a-03ee-11f0-a82a-06e40ab4d024(Global User): Assert failed: pLink
    (ERROR) : [sm-xpsxps-05750] Invalid Object: CA.SM::IMSManagedObject@33-0000ff0a-03ee-11f0-a82a-06e40ab4d024(Global User).

     

    OBJECT-3
    (ERROR) : [sm-xobsm-01110] CA.SM::IMSManagedObject@33-000673b6-ec58-1548-96b2-06e40ab440a7(Organization): [CA.SM::IMSManagedObject.AdditionalPropertiesLink]: Invalid attribute: [CA.SM::IMSAdditionalPropertiesSet@20-000b9e08-ec58-1548-96b2-06e40ab440a7].
    (ERROR) : [CA-SM-Assert] CA.SM::IMSManagedObject@33-000673b6-ec58-1548-96b2-06e40ab440a7(Organization): Assert failed: pLink
    (ERROR) : [sm-xpsxps-05750] Invalid Object: CA.SM::IMSManagedObject@33-000673b6-ec58-1548-96b2-06e40ab440a7(Organization).



  • 5.  Re: XPSSweeper errors after IDM objects import from SM V12.0 to V12.52

    Posted 03-09-2017 04:48 PM

    Hi Dennis,

     

    The IdmSmObjects.xdd file was successfully imported. Below is my XPSExplorer output complaining about the IMSAdditionalPropertiesSet.

     

    AdditionalPropertiesLink (ERROR) : [sm-xobsm-01110] CA.SM::IMSEnvironment@35-000521c2-f196-12d6-b93f-06e40ab4d024(FDCExtNA_DR): [CA.SM::IMSEnvironment.AdditionalPropertiesLink]: Invalid attribute: [CA.SM::IMSAdditionalPropertiesSet@20-000dc3b6-f1a6-12d6-b93f-06e40ab4d024].
    = <?^?>