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

SYMPTOMS

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

CAUSE

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 
-----------------

RESOLUTION

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

DISCLAIMER

MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE FOR ANY PURPOSE. THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED HEREIN AT ANY TIME.

For more information on the terms of use, click on the link below:
http://support.microsoft.com/tou/