AdminUI: Partnership failed to activate

Document ID : KB000032041
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem:

Using the AdminUI, each time that we were trying to activate a Partnership we were getting the following error: Error activating Partnership.  

  • Checking the policy server logs and traces we can see:


[28246/-239907984][Tue Sep 22 2015 15:25:33][PartnershipSvcBase.cpp:3112][findActivePropertySection][ERROR][sm-xobfed-01070] Failed to create filter
[28246/-239907984][Tue Sep 22 2015 15:25:33][PartnershipSvcBase.cpp:3144][findActivePropertySection][ERROR][sm-xobfed-00390] Activation check failed
[28246/-239907984][Tue Sep 22 2015 15:25:33][SPPartSvc.cpp:1899][canBeActivated][ERROR][sm-xobfed-01470] canBeActivated failed

  • Associated traces:


[09/22/2015][15:25:33.460][15:25:33][28246][4055059312][Reference.cpp:439][ReferenceImpl][][][][][][][][][][][][][][][][][][][][][Enter ReferenceImpl]
[09/22/2015][15:25:33.461][15:25:33][28246][4055059312][Reference.cpp:1278][ReferenceImpl][][][][][][][][][][][][][][][][][][][][][Unable to resolve dictionary reference"CA.SM::SAMLv2SP.KEY_SPID".]
[09/22/2015][15:25:33.461][15:25:33][28246][4055059312][][ReferenceImpl][][][][][][][][][][][][][][][][][][][][][Exit ReferenceImpl]
[09/22/2015][15:25:33.461][15:25:33][28246][4055059312][PartnershipSvcBase.cpp:3112][findActivePropertySection][][][][][][][][][][][][][][][][][][][][][LogMessage:ERROR: Failed to create filter]
[09/22/2015][15:25:33.461][15:25:33][28246][4055059312][PartnershipSvcBase.cpp:3144][findActivePropertySection][][][][][][][][][][][][][][][][][][][][][LogMessage:ERROR: Activation check failed]
[09/22/2015][15:25:33.461][15:25:33][28246][4055059312][SPPartSvc.cpp:1899][canBeActivated][][][][][][][][][][][][][][][][][][][][][LogMessage:ERROR: canBeActivated failed.]
[09/22/2015][15:25:33.461][15:25:33][28246][4055059312][SPPartSvc.cpp:2365][setActivated][][][][][][][][][][][][][][][][][][][][][LogMessage:ERROR: setActivated failed.]

The policy server was missing some objects.

Solution:

Checking the objects, we were missing some by using XPSExplorer based on a standard policy store installation.

Running the following fixed the problem:

1) XPSDDInstall SmMaster.xdd
2) Restart SM Policy Server

  • Please note that all operation on policy store would need a backup before to be able to rollback to a previous stage in case of any error.

Additional Information:

In the event that the above solution does not work, occasionally a few additional steps are necessary:

1) Run XPSSweeper to synchronize all Policy Store objects with Policy Server

2) XPSDDInstall SmMaster.xdd (in some Partnership Federation instances, the objects facing the issue need to be manually deleted and recreated)

3) Run XPSImport smpolicy.xml to ensure all required objects are loaded

4) Restart SM Policy Server

5) Activate Partnership