KB164761 - Push Replications Using ACLs Fail to Replicate Some Files

Article ID: 164761

Article Last Modified on 11/5/2003

Microsoft Commercial Internet System 1.0 Service Pack 2

This article was previously published under Q164761

SYMPTOMS

When a push replication with the /ACLS flag encounters a file that Content Replication System (CRS) does not have access to, the replication pauses for what appears to be a timeout period, and then completes without errors. However, any files in the directory that had not already been replicated at this point are not sent. Without the /ACLS flag, the same timeout period occurs, but the replication continues, skipping the files that CRS cannot access.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Commercial Internet System version 1.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Commercial Internet System version 1.0. For information on obtaining the Service Pack, query on the following article in the Microsoft Knowledge Base:

183062 MCIS 1.0 Service Packs 1 and 2 Information

MORE INFORMATION

When CRS encounters a file that it does not have access to, CRS will abort the entire replication. On abort, an event will be recorded in the Windows NT Event log stating:

The replication %1 was aborted"

where "%1" is the name of the project.

Keywords: kbbug kbfix KB164761