000019211 - Error: 'Rep name in DB doesn't match host' appears in application log

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

Article Content

Article Number000019211
Applies ToRSA ACE/Server 5.0.1 (no longer supported as of 8-15-2004)
IssueError: "Rep name in DB doesn't match host" appears in application log
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
CauseThe name of the replica specified in replica table on primary server does not match with the hostname of replica
Resolution

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.

Legacy Article IDa6934

Attachments

    Outcomes