000018814 - Primary ACE/Server not connecting with new replica

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

Article Content

Article Number000018814
Applies ToRSA ACE/Server 5.0 (no longer supported as of 8-15-2004)
IssuePrimary ACE/Server not connecting with new replica
Some services on replica aren't starting
Error: "Replica record not on file (138)"
Error: "No replica list record available (91)"
Error: "_edit.p was not found (293)"
ERROR: "Unable to run the PROGRESS Procedure Editor _edit.p. (3261)"
CauseThe Replica host information in Configuration Management was in upper-case when the host name resolves to a lower-case name
ResolutionTo correct this issue, modify the Replica Configuration Management screen so "This server:" entry is the correct server name listed on the Replication Management screen of the primary. This server entry must resolve correctly. Modify DNS or the host file if necessary.
Legacy Article IDa3643

Attachments

    Outcomes