BUG: SS3 SDK CReplicationClient Returns Access Denied (321161)



The information in this article applies to:

  • Microsoft Site Server 3.0 Commerce Edition

This article was previously published under Q321161

SYMPTOMS

Content Replication System (CRS) CReplicationClient object method calls, which manipulate files such as DeleteFile, may fail to complete and then display the following error message:
Access Denied

CAUSE

File operations require that the user context that creates the CReplicationClient object must be a system administrator on the source system. When a file operation method is called on the object, authentication occurs. The authentication requires system administrator rights.

RESOLUTION

To work around this problem:
  • Use an account with system administrator rights if file level operations that use the CRS application programming interface (API) CReplicationClient object are required.
  • Use the CReplicationProject object to perform all file replications. This object works successfully when it runs under the context of a nonsystem administrator because it uses the global CRS authentication account to perform the operations.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

If you try to create a CReplicationClient object from the context of a user account in the Site Server publishing Administrator group (but not in the local Administrator group), the attempt fails. The failure occurs when you call the methods on the object. This occurs even when the project and the file permissions are configured properly, and the default CRS authentication account has administrative rights.

CReplicationProject methods succeed when you use the same user account.

Steps to Reproduce the Behavior

  1. Use the following API call to create an instance of a CRS client.
           Call ReplClient.DeleteFile(aryFileList(i))<BR/>
    					
  2. Try to delete a file.

Modification Type:MajorLast Reviewed:6/30/2006
Keywords:kbbug kbnofix KB321161