"Error trying to export a Policy Xpress Policy" when attempting to import an environment xml
search cancel

"Error trying to export a Policy Xpress Policy" when attempting to import an environment xml

book

Article ID: 262338

calendar_today

Updated On:

Products

CA Identity Manager

Issue/Introduction

Import issue showing PX: During an import of a environmental XML in the Management Console it fails with an odd message about not being about to export a Policy Xpress Policy:


  Deploying role definitions...
    Importing Screens...
    Importing Tasks...
    Importing Roles...
    Importing Policies...
    Importing Managed Objects...
Error: Error trying to export a Policy Xpress Policy


*********
1 error(s), 31 warning(s)

 

 

Environment

Release : 14.4

Cause

This issue was traced down to having a policy express policy with special characters:

<PxParameter extraInfo="" index="2" uiType="TYPED">&#31;&#31;</PxParameter>

Resolution


First, use the Identity Manager /standalone/log/server.log to locate more details about the import failure:

2024-01-18 14:53:38,311 ERROR [stderr] (Thread-476) [Fatal Error] :66:57: Character reference "&#31" is an invalid XML character.
2024-01-18 14:53:38,311 ERROR [ims.idmmanage] (Thread-476) com.ca.identitymanager.policyxpress.exceptions.PxImportException:
Error trying to export a Policy Xpress Policy

You can then use this to locate the problematic Policy Xpress Policies by searching the environment xml for, in this case &#31.


Once the problematic PXpolicies are identified, you have a couple of options. 

1. If the original system is available review through the problematic PXPolicies and correct / remove odd special characters, then create a new exported xml file without the special characters.


2. If the original system is not available first try just removing special characters from, or the entire element:

<PxParameter extraInfo="" index="2" uiType="TYPED">&#31;&#31;</PxParameter>


If this allows the import to complete, log into the User interface and add that parameter back without the special character (s) 

3. If simply removing the problem element does not work, remove the entire Policy, from the 
<ManagedObject type="POLICY XPRESS EXPORT" friendlyName=
through the end tag:
</ManagedObject> 

You can then rebuild that Policy Xpress policy in the User Interface as normal, taking care to avoid unusual special characters.