The request could not be handled error is thrown while editing a Change Request in RSA Identity Governance and Lifecycle
Originally Published: 2016-05-17
Article Number
Applies To
RSA Version/Condition: 6.9.1, 7.0.0
Issue
The following error will appear in the aveksaServer.log or in the logs found at Admin > System > Logs:
05/13/2016 14:51:05.575 ERROR (http-0.0.0.0-8443-7) [com.aveksa.UI] com.aveksa.gui.core.MainManager.handleRequest(MainManager.java:195) -
java.lang.NullPointerException
at com.aveksa.gui.util.forms.CustomValueTextField.printAsSelectField(CustomValueTextField.java:61)
at com.aveksa.gui.util.forms.CustomValueTextField.printComponent(CustomValueTextField.java:44)
at com.aveksa.gui.util.forms.FormField.print(FormField.java:272)
at com.aveksa.gui.util.forms.FormField.print(FormField.java:266)
at com.aveksa.gui.pages.admin.extensibleObject.edit.ExtensibleObjectPickerHelper.makeEditableExtensibleFld(ExtensibleObjectPickerHelper.java:447)
at com.aveksa.gui.pages.admin.extensibleObject.edit.ExtensibleObjectPickerHelper.makeExtensibleAttributeFlds(ExtensibleObjectPickerHelper.java:372)
at com.aveksa.gui.pages.admin.extensibleObject.edit.ExtensibleObjectPickerHelper.makeExtensibleAttributeFlds(ExtensibleObjectPickerHelper.java:332)
at com.aveksa.gui.pages.changeRequest.edit.ModifyCRDialogView.printContent(ModifyCRDialogView.java:41)
at com.aveksa.gui.pages.base.view.DialogPageView.makeContent(DialogPageView.java:134)........
Cause
Resolution
- Go to Admin > Attributes > Custom Values.
- Edit the Value list of String type.
- Click on the Value tab and add the values.
If you do not want to restrict the values users can provide for the string attributes, make sure you do not associate custom values to the attributes. For change request attributes, this can be done by editing the Change Request attributes [Admin > Attributes > Change Request > click Edit and disassociate the Custom Value from the desired attribute.
Related Articles
'Request could not be handled' error exporting metadata from RSA Identity Governance & Lifecycle 80Number of Views Getting a Request could not be handled error when trying to change the certificate store on RSA Via Lifecycle & Governance… 10Number of Views When editing/creating a SOAP Web Service AFX Connector and configuring any capability, a 'Request could not be handled' me… 53Number of Views Request Could not be Handled while generating server.keystore & client.keystore in RSA Governance & Lifecycle 231Number of Views 'Request could not be handled' and 'No enum constant com.aveksa.server.core.DataCollector.Status.InActive' errors exportin… 161Number of Views
Trending Articles
An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process
Don't see what you're looking for?