on Jun 14, 2016Article Content
| Article Number | 000012435 | ||||||||||||||||||||||||
| Applies To | RSA Authentication Manager 8.0 RSA Authentication Manager 8.1 | ||||||||||||||||||||||||
| Issue | Unable to attach replica to primary 8.1 - new deployment @@@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 teh virtual appaliance 3- follow the procedure in the setup and configuration guide for deploying a new replica instance | ||||||||||||||||||||||||
| Cause | License instances limit reached | ||||||||||||||||||||||||
| Resolution | 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 atttachement. If your error message is: error: The user will not be able to attach this replica. To show that the limit has been reached go to: Security console - Setup - Licenses - Status - View Installed Linceses - Click on installed license and select view :
| ||||||||||||||||||||||||
| Legacy Article ID | a63762 |