The replicated folder {0} is published in a namespace. Creating a new member for this replicated folder does not add the member to the namespace. Therefore, users cannot access the member using the namespace. To add the new member without adding it to the namespace, use the /force parameter.
The replica source %1:%2 requires Kerberos authentication but does not have a properly registered service principal name ...
The replica/child install failed to get the objectVersion attribute on the schema container on the source DC. Either the ...
The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the ...
The replicated folder at local path %2!s! has been disabled. The replicated folder will not participate in replication until ...
The replicated folder {0} is published in a namespace. Creating a new member for this replicated folder does not add the ...
The replicated folder {0} is published in a namespace. Creating a new membership for this replicated folder does not add ...
The replicated folder {0} is published in a namespace. Deleting the replicated folder does not remove it from the namespace. ...
The replicated folder {0} is published in a namespace. Enabling a membership for this replicated folder does not add the ...
The replicated folders listed above are not participating in replication because their memberships were manually disabled ...