Successfully created replica package
New install of Replica
When the replica is started, on the primary ACE/Server activity monitor messages appear. "primary connected to replica" and followed by the error: " Rep name in DB doesn't match host". The same error may also appear in application log, if configured within ACE Administration to "Log to System Log". For example, on the primary ACE/Server activity monitor, the following messages appear when a new replica is started:
11/29/2001 10:53:41 Primary connected to replica gtrp1rsa.shandwic.com (the name of new replica)
11/29/2001 10:53:45 Rep name in DB doesn't match host eastrsa02bsmg.bsmg.com
11/29/2001 10:53:45 Shutting down replica eastrsa02bsmg.bsmg.com
This is very common with Windows 2000 servers as in most cases domain name is not part of the computer name.
a. On the primary server do the following at a command prompt:
cd ace/data
sdrepmgmt list
This will give the list of all hostnames in replica table. Note the replica name whether it is FQDN or short name.
Notice the name of the replica server. If the replica server name is not correct, delete the the replica server from the replica table and add it with the correct name.
sdrepmgmt delete
Enter the name of the replica server name.
sdrepmgmt add
Enter the correct name of the replica server name.
If you think the replica table is more accurate and there is error on replica server name on actual machine, proceed as below described:
b. On the replica server:
My computer -->Right Click -->Properties --> Network Identification ----->Full Computer name
Verify the hostname and if the name is matching with the hostname in the replica table.
If the hostname does not match, Click on Properties and change the hostname.
Hostname must be all in lower case in order to maintain consistency. Reboot the server.
c. Confirm the hostname change by running: ipconfig /all
d. Start the primary server.
e. On the primary server launch the activity monitor.
f. Start the replica.
Related Articles
Generate reports for extendable and nonextendable tokens in RSA Authentication Manager 8.2 or later 469Number of Views Create a report of online emergency access tokencodes and emergency access tokencode lifetimes for RSA Authentication Mana… 257Number of Views Migration to RSA Authentication Manager 8.1 with the option to retain system settings fails with an error about duplicate … 137Number of Views RSA Authentication Manager replica instance fails to attach to the Authentication Manager deployment 402Number of Views How to manually sync a replica in an RSA Authentication Manager 8.x deployment with one or more replicas 1.49KNumber of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide