Primary does not communicate with replica. Activity monitor does not show messages.
Originally Published: 2001-08-30
Last Modified: 2023-10-06
Article Number
Applies To
Issue
Created a replica package on the primary
Files copied manually from ace/data/replica_package/ from primary to replica
Started the Primary. Started the replica. No messages appear on the activity monitor.
Cause
Resolution
a. On UNIX Server:
Run ./sdsetup -config and change the the "This Server" to the Replica's name.
This will correct the field "This server"
b. On NT Server:
Edit the ACE/Server Configuration Management. Change the field "This server" and type the name of the replica.
2. Bring up the activity monitor on primary.
3. Start the replica.
For additional information see also: How to tell the Primary and a Replica are synchronizing in RSA ACE/Server and RSA Authentication Manager
Related Articles
Alert sent 'EM-006 : Unable to communicate with Network Controller' Number of Views Workflow editor pop-up "An error occurred communicating with the server" in RSA Identity Governance and Lifecycle Number of Views SID: sd_login error unable to communicate with Authentication server Number of Views A Firewall is blocking Remote AFX Agents and Remote Collection Agents from communicating with the Application Server in RS… Number of Views RCM xudad.exe is failing to start Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide User Application Portal Unable to Resolve User by Login ID and/or Alias or Authenticator Not Assigned to User When Attempting to Authenticate via … Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU Manage Users for Cloud Access Service
Don't see what you're looking for?
