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
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 Alert sent 'EM-006 : Unable to communicate with Network Controller' 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 How to report OC admin activity immediately and forward it to Syslog? Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?
