Hello,
I currently have a strange situation where I have added several new folders to existing replications groups. Therefore, some folders are reporting a status of normal, where some are reporting Waiting for initial replication .
For a given folder that is reporting Normal status, if a file is created on the non-primary member, it will replicate the the primary member. However, if a file is created on the primary member, it will not replicate to the child member. Keep in mind that this is for a replicated folder reporting a status of Normal , not reporting the status of Waiting for initial replication .
There doesn't appear to be anything strange in the logs reflecting trouble. Why would the above occur? Why wouldn't the change replicate in the Normal folder as expected?
In addition to the "content set not ready" errors, I receive the following error on the child member:
20100202 19:43:30.200 4324 MEET 3109 Meet::GetParent -> BLOCKED Could not find parent. parentUid:{225499E9-D466-4CC2-94D9-F2C897D1EBF1}-v14008502 updateName:file.ext uid:{225499E9-D466-4CC2-94D9-F2C897D1EBF1}-v14008806 gvsn:{225499E9-D466-4CC2-94D9-F2C897D1EBF1}-v14008806 connId:{BBDEEF56-3EB8-4FF4-8C59-DECC1642ABF3} csName:REPLNAME csId:{440B02C8-9F51-4A45-9C73-BD2105B47710}
The folder REPLNAME is reporting Waiting for initial synchronization . What does this error: "BLOCKED Could not find parent" indicate?
Thanks for your time,
Matt Brown
<small> My unanswered threads:
• DFS / RDC size estimations?
• Online backup of Active Directory / ESE DB, command line interface to ESENT.DLL's JetBackup() function.</small>
I currently have a strange situation where I have added several new folders to existing replications groups. Therefore, some folders are reporting a status of normal, where some are reporting Waiting for initial replication .
For a given folder that is reporting Normal status, if a file is created on the non-primary member, it will replicate the the primary member. However, if a file is created on the primary member, it will not replicate to the child member. Keep in mind that this is for a replicated folder reporting a status of Normal , not reporting the status of Waiting for initial replication .
There doesn't appear to be anything strange in the logs reflecting trouble. Why would the above occur? Why wouldn't the change replicate in the Normal folder as expected?
In addition to the "content set not ready" errors, I receive the following error on the child member:
20100202 19:43:30.200 4324 MEET 3109 Meet::GetParent -> BLOCKED Could not find parent. parentUid:{225499E9-D466-4CC2-94D9-F2C897D1EBF1}-v14008502 updateName:file.ext uid:{225499E9-D466-4CC2-94D9-F2C897D1EBF1}-v14008806 gvsn:{225499E9-D466-4CC2-94D9-F2C897D1EBF1}-v14008806 connId:{BBDEEF56-3EB8-4FF4-8C59-DECC1642ABF3} csName:REPLNAME csId:{440B02C8-9F51-4A45-9C73-BD2105B47710}
The folder REPLNAME is reporting Waiting for initial synchronization . What does this error: "BLOCKED Could not find parent" indicate?
Thanks for your time,
Matt Brown
<small> My unanswered threads:
• DFS / RDC size estimations?
• Online backup of Active Directory / ESE DB, command line interface to ESENT.DLL's JetBackup() function.</small>