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
WebService cancelChangeActivity causes activity to stay in Activity State of Open in RSA Identity Governance & Lifecycle 7… Number of Views Unable to create managed connection errors in the System Activity Monitor for RSA Authentication Manager 8.x Number of Views VMWare UAG Authentication Fails with error "Initialize Request Proxied" in the Authentication Activity Monitor Number of Views Authentication using acetest fails TRANSACTION_ROLLBACK on real time authentication activity monitor for RSA Authenticatio… Number of Views Duplicate entitlements are created when an Application has 'Complete Manual Activity Before Collection' enabled in RSA Ide… Number of Views
Trending Articles
RSA Release Notes for RSA Authentication Manager 8.8 RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Upgrade Process Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
