Error This replica exceeds the number of instances allowed by the license when trying to attach replica in RSA Authentication Manager 8.1
Originally Published: 2014-01-17
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.1
Issue
In a new deployment of RSA Authentication Manager 8.1 the replica will not attach to the primary.
The following error is seen in the Operations Console UI:
The following error is seen in the Operations Console UI:
@@@2014-01-16 15:49:30,468 ERROR [ReplicaAttach] GUILog.traceThrowable(637) | error:
com.rsa.authmgr.internal.replication.TransportClientUnexpectedStatusException: Expected the HTTP response code 200, but got: 500 Message: java.lang.RuntimeException: The gddrlvrsa01.gfinet.com replica with the d8b5ca9fc9e6010a0801c4c9c629f1ab instance ID was not able to attach. This replica exceeds the number of instances allowed by the license.
Errror : failled to attach replica instance.
To attach a replica instance the user must redeploy this replica instance by performing the following steps:
1- delete this replica
2- shutdown and delete the virtual appliance
3- follow the procedure in the setup and configuration guide for deploying a new replica instance
Cause
The error displayed in the Operations Console is deceiving, because it does not mention that the limit allowed of instances has been reached.
Open the install logs.zip file you can download from the error page, and select the rsa-console.log. In the log you will be able to verify the actual reason for the failed attachment.mmIf your error message is the text below, then the replica will not attach:
com.rsa.authmgr.internal.replication.TransportClientUnexpectedStatusException: Expected the HTTP response code 200, but got: 500 Message: java.lang.RuntimeException: The Hostname replica with the instanceID instance ID was not able to attach. This replica exceeds the number of instances allowed by the license.
To show that the instance limit has been reached,
- Launch the Security Console and navigate to Setup > Licenses > Status > View Installed Licenses.
- Click on the installed license and select View.
- Review the information in the Number of Instances row. If you are at the limit for allowed replicas, you will not be able to add another one to the deployment. For more information see documentation on RSA SecurID Access Editions.
| License Feature | Description |
| Authenticator Provisioning | Available |
| Business Continuity | Available |
| License Type | 300 |
| Number of Instances | 15 |
| Number of users with RBA/ODA enabled | 5000 |
| Offline Authentication | Available |
| RADIUS | Available |
| RBA/ODA | Available |
| Self-Service | Available |
| Tokens | Available |
| Users with Assigned Authenticators | 100000 |
Resolution
Speak to your RSA sales representative or reseller about purchasing either an Enterprise Edition or Premium Edition license.
Related Articles
Error: 'Web-tier host certificate creation failed' when trying to create a web tier package Number of Views AuthnContextValidator error when trying to authenticate using RSA Authentication Agent 2.0 for AD FS Number of Views Passcode format error when trying to set a PIN thru a Cisco ASA Number of Views Server certificate validation error when trying to authenticate using the RSA Authentication Agent 2.0 for AD FS Number of Views How to recover from "Error: The private key could not be parsed" when trying to upload the RSA SecurID Access Identity Rou… Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?
