AnsweredAssumed Answered

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

Question asked by Dheeru.S on Feb 21, 2017
Latest reply on Mar 9, 2017 by Dheeru.S

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).

Outcomes