After some period of inactivity RCM-API based application fails at the function call XudaLDAPFetch() with return code 35 (XrcWRITEFAILURE)
Originally Published: 2012-11-29
Last Modified: 2023-10-06
Article Number
Applies To
Firewall between the host where RCM-API application is running and another host where the target RSA Certificate Manager is installed
Issue
If the RCM-API application is restarted, it starts working fine without any issues (until a period of inactivity lapses, such as 30 minutes)
Cause
Resolution
Update the application using RCM-API 6.8 build 522 (or later) and set XresKEEPLDAPOPEN to 1.
Workaround
Notes
Related Articles
User delete operations take an excessive period of time to perform on excessively large static groups in RSA Access Manage… 23Number of Views Amazon Web Services IAM - Session Tags Configuration - RSA Ready Implementation Guide 1Number of Views CyberArk Password Vault Web Access - SAML My Page SSO Configuration - RSA Ready Implementation Guide 68Number of Views How to set a session timeout when accessing the Admin Console to automatically log out the user after a certain period of … 69Number of Views Default Application Business Source attributes are returning null values when called through variables in Request Forms in… 81Number of Views
Trending Articles
Authentication Manager Syslog Data Not Reaching Remote Syslog Server RSA Authentication Manager 8.9 Patches and Hotfixes Readme How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to Forward RSA Authentication Manager 8.4 or Later Logs to Multiple Syslog Servers Using rsyslog RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?