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
Alert sent 'EM-006 : Unable to communicate with Network Controller' Number of Views ESA Alerts Summary Page Does Not Show Stats 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 Business Role Does not Show Missing Direct Entitlements Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to implement SAML SSO Authentication with Microsoft Azure Active Directory and RSA Identity Governance & Lifecycle How to download full kits, service packs, and patches from RSA Link for RSA Identity Governance & Lifecycle Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update RSA announces the availability of the RSA SecurID Hardware Appliance 350 based on the Dell PowerEdge R640 Server
Don't see what you're looking for?
