Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. E2K3/XADM - PFDAVAdmin unable to propagate client permissions on mailbox folders or public folders

E2K3/XADM - PFDAVAdmin unable to propagate client permissions on mailbox folders or public folders

View products that this article applies to.

Symptoms

Source: Microsoft Support

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION IN RESPONSE TO EMERGING OR UNIQUE TOPICS, AND MAY BE UPDATED AS NEW INFORMATION BECOMES AVAILABLE.

↑ Back to the top

Cause

Customer is attempting to propagate client permissions on a mailbox folder to its subfolders by using PFDAVAdmin. However, when we attempt to propagate, we get the following error:
http://<servername>/exadmin/admin/DOMAIN.COM/mbx/user/ Failed to process subfolders with exception: The remote server returned an error: (404) Not Found. Finished.

If we try to propagate folder ACEs for public folders, we would see the following:
<http://<servername>/exadmin/admin/DOMAIN.COM/public%20folders/TestFolder/> Failed to process subfolders with exception: The remote server returned an error: (404) Not Found. Finished.

Environment:

Exchange Server 2003 Service Pack 1
PFDAVAdmin web release version 6.5.7720.1

↑ Back to the top

Resolution

URLScan was installed and running on the server where the mailbox was located.

If you view the URLScan log file (default location is <System root>\system32\inetsrv\urlscan), you'll see an entry similar to this
[01-11-2006 - 15:39:26] ---------------- Initializing UrlScan.log 
----------------
[01-11-2006 - 15:39:26] -- Filter initialization time: [11-25-2005 - 12:54:23] --
[01-11-2006 - 15:39:26] Client at 10.30.8.52: Sent verb 'BPROPFIND', which is not 
specifically allowed. Request will be rejected.
[01-11-2006 - 15:39:32] Client at 10.30.8.52: Sent verb 'BPROPFIND', which is not 
specifically allowed. Request will be rejected.
[01-11-2006 - 15:52:50] Client at 10.30.8.52: Sent verb 'BPROPFIND', which is not 
specifically allowed. Request will be rejected.
[01-11-2006 - 15:52:57] Client at 10.30.8.52: Sent verb 'BPROPFIND', which is not 
specifically allowed. Request will be rejected.
[01-11-2006 - 16:32:05] Client at 10.30.8.52: Sent verb 'BPROPFIND', which is not 
specifically allowed. Request will be rejected.
[01-11-2006 - 17:02:04] ---------------- UrlScan.dll Terminating 
-----------------

↑ Back to the top

Disclaimer

We needed to add the BPROPFIND verb to the "AllowVerbs" section of the urlscan.ini file to allow PFDAVAdmin to work successfully after we restarted IISAdmin.

Installing the latest version of PFDAVAdmin resolved the issue when the above resolution failed in a recent case.
http://www.microsoft.com/downloads/details.aspx?FamilyID=635be792-d8ad-49e3-ada4-e2422c0ab424&displaylang=en
PFDAVAdmin version: 06.05.7775

↑ Back to the top

Keywords: KB924196, kbrapidpub, kbtshoot, kbprb

↑ Back to the top

Article Info
Article ID : 924196
Revision : 3
Created on : 10/25/2007
Published on : 10/25/2007
Exists online : False
Views : 225