R_KM_KEY_get_security_obj_meta_data returned 10017
Originally Published: 2009-07-30
Article Number
Applies To
Issue
get_key call previously failed with error 10040
Resolution
After solving the error 10040, the 10017 error went away.
As an FYI, 10040 is a CA Certificate error. Make sure that the web server CA certificate is trusted by the RKM Client, and that the client cert's issuer CA is trusted by the web server.
Related Articles
"Error opening installation log file" during uninstallation of RSA Authentication agent for windows 27Number of Views How to delete the RSA Authentication Manager 8.x virtual host Certificate Signing Requests (CSR) which show Pending/Inactive 1.42KNumber of Views How to determine the RSA Authentication Manager 8.x hardware platform 542Number of Views RSA Token Client returns error 40032 - R_TC_ERR_REGISTRATION_FAIL 17Number of Views How to retrieve an RSA Authentication Manager 8.x license file from the file system 179Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?