Archive Server Fails to Synchronize Cloned Object Classes and Properties
Note:
This should be a rare event. Ideally the Archive server is setup and
connected when the primary DocuShare server is installed, thus staying in sync
when the custom classes are cloned.
Issue
When an Archive Server is setup after the primary
DocuShare server has been customized with cloned object classes, especially
object classes cloned from a clone, the Archive server will not be in sync with
the primary DocuShare server. Reason
/ Possible Cause Because the Archive server is not connected when the
cloned objects are created, especially the objects cloned from a cloned class,
the Archive server will fail to create a custom class cloned from another
custom object class. Work
Around Login as Admin to the Archive server and use the Custom
Object page under the Object Properties menu to manually replicate each custom
class on the Archive server that exists on the primary server. Special care must be taken to insure that
class name are spelled exactly as they are on the primary server. Note that clones of clones must be created in
the same sequence they were created on the primary server. The properties for these custom objects do
not need to be replicated as they will be synchronized the next time the server
restarts and synchronizes with the primary server.
Solution
Published: September 8th,
2014 Solution ID: 1542
|