Items whose attributes prevented replication will not replicate after being changed to replicable
Article ID: 162239
IT Management Suite
The attributes of Organizational Group items were, at one time, set to 516 (non-replicable) in order to prevent them from replicating (as recommended for specific reasons in TECH200746). But after changing the attributes back to 512 (replicable) the items failed to replicate during the next differential replication cycle. Nor would they replicate during a complete replication cycle.
Because the attributes were, at one time, set to non-replicable, the Organizational Group items were entered into the “ReplicationItem” table with the “IsReplicable” bit set to 0. This is to be able to quickly determine which items, during the initial phases of replication, should be evaluated, and which ones can be discarded. The end result is the items will not get replicated because they were once declared by their attributes not to be replicable.
Flipping the IsReplicable column to 1 is not enough. The items need to be removed from ItemReplication before the next replication cycle.
Flipping the IsReplicable column to 1 is not enough. The items need to be removed from ItemReplication before the next replication cycle. The following query example, when run against the parent’s database, will remove all references to Organizational Group items (scoped collections) that were at one time identified as non-replicable, but whose attributes now allow it. Example #1 – All Organizational Groups