Primary does not communicate with replica. Activity monitor does not show messages.
Originally Published: 2001-08-30
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
VMWare UAG Authentication Fails with error "Initialize Request Proxied" in the Authentication Activity Monitor Number of Views Real-Time Monitoring Using Activity Monitors Number of Views WebService cancelChangeActivity causes activity to stay in Activity State of Open in RSA Identity Governance & Lifecycle 7… Number of Views RSA Identity Governance and Lifecycle Workflow Activity Node of type Decision Node based on internal variables always eval… Number of Views View Messages in the Activity Monitor Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?
