Replication enabled database cores when started multi-user

Replication enabled database does not start multi-user
Multi user start-up session stops after the 13870 message in the database lg file PROSERVE of replication enabled database crashes with protrace file

Stack trace from _mprosrv.exe reads:

The database Control Area was rebuilt for either the Source or Target database with the PROSTRCT BUILDDB utility.

Full stack trace from _mprosrv on Windows reads:

Exception code: C0000005 ACCESS_VIOLATION
Fault address:  0040AEB0 01:00009EB0 _mprosrv.exe

Registers:
EAX:00127FE4
EBX:00002000
ECX:00127FF0
EDX:00000001
ESI:00127C3B
EDI:00127E03
CS:EIP:001B:0040AEB0
SS:ESP:0023:00127A98  EBP:00127E3E
DS:0023  ES:0023  FS:003B  GS:0000
Flags:00010202

Call Stack:
Address   Frame
0040AEB0  00127E3E  dbut_firstByte+9770
61626174  61642073  0000:00000000

When the database Control Area has been rebuilt for either the source or the target database, the PROSTRCT BUILDDB utility does only minimal validation of the resulting Control Area and is not able to fully reconstruct all the control information needed by Replication. 

Amongst others PROSTRCT BUILDDB will create an empty replication blob in the new Control Area, which the replication model relies on to keep recovery information in a blob (RCB) in the Control Area (.db) file. The database code cannot recreate this information since it is Replication specific.

Rebuilding the Control Area (.db) of a replication enabled database, effectively disables replication. This utility should never be used in a replication environment before PROUTIL disablesitereplication and then only when all other avenues have been exhausted.

The replication baseline will need to be re-established. It is not the intent of this Article to fully describe the steps involved. These should be fully documented in the site Backup Restore / Disaster Recovery plans based on the individual environment requirements and version possibilities.

A. If the source database Control Area was rebuilt with BUILDDB:

• Remove the [source | target].repl.recovery files,
• Re-enable Replication on source database,
• Take a new full backup of source
• Restore this backup to target and
• Enable replication on target database.

B. If the target database Control Area was rebuilt with BUILDDB:

• Remove the target.repl.recovery files, 
• Take a new full backup of source
• Restore this backup to target
• Enable replication on target database.

C. There may be extraneous circumstances in the production environment which lead to the perceived need for the control area to be rebuilt.  Other recovery options may include:

References To Written Documentation:

OpenEdge Replication Users Guide - Reference - Utilities and OpenEdge Replication

Progress Articles: 

What effect does builddb have on a replication enabled database?   
How does changing the name of a storage area affect after-imaging?