Microsoft KB Archive/159726

From BetaArchive Wiki
Knowledge Base


Files with No Access ACL Do Not Reach Destination Directory

Article ID: 159726

Article Last Modified on 11/7/2003



APPLIES TO

  • Microsoft Commercial Internet System 1.0 Service Pack 2



This article was previously published under Q159726


SYMPTOMS

If you are replicating with Transaction Method on, and you have Membership Services installed, you may notice that some of your files that have No Access permissions do not reach the destination directory. When you install the Membership Broker (the broker portion of MBS), the following registry entry is added:

   HKEY_LOCAL_MACHINE\Software\SecRepl\DefaultAccount
                

The value is set to the user account "Administrator." Normally, if the Content Replication System (CRS) is unable to find a valid SID to assign to the No Access permission at the target computer, it will strip all ACL values and set Full Control permissions to the Default Account. Unless the CRS service account is Administrator (not recommended) CRS will lose permissions to this file and will be unable to rename the file from the CRSTemp directory into the destination directory.

RESOLUTION

Set the Default Account to the Administrators group, or a group that both the CRS Service account and a local administrator belong to. To change the Default Account:

  1. Start Registry Editor (Regedt32.exe or Regedit.exe, depending on your version of Windows NT).
  2. Select the following registry entry and press ENTER:

          HKEY_LOCAL_MACHINE\Software\SecRepl\DefaultAccount
                            
  3. Edit the data value of the entry to the desired group and click OK.

NOTE: This behavior is also for pre-Site Server versions of CRS. As of Site Server release and SP2 for MCIS, the DefaultAccount registry key will be null and void. Default behavior will be to assign the Well Known SID entry of Administrators group.

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:

ARTICLE-ID: 183062
TITLE : MCIS 1.0 Service Packs 1 and 2 Information


Keywords: kbbug kbfix KB159726