000018997 - Primary does not communicate with replica. Activity monitor does not show messages.

Document created by RSA Customer Support Employee on Jun 15, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000018997
Applies ToRSA ACE/Server 5.0 (no longer supported as of 8-15-2004)
IssuePrimary does not communicate with replica. Activity monitor does not show messages.
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.
CauseThe sdconf.rec file on the Replica is configured as if it were the Primary server.  This can be confirmed by running sdinfo (UNIX) or examine the "Configuration Management" (NT) on replica. In the field "This server" it shows the name of primary, which is incorrect.
Resolution1.On the replica, by editing configuration management change the field "This Server"

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
Legacy Article IDa4938

Attachments

    Outcomes