Microsoft KB Archive/915325

= A PROPPATCH request to update the security descriptor of the public folder appears to succeed, but the update is unsuccessful in Exchange Server 2003 =

Article ID: 915325

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange Server 2003 Enterprise Edition

-





SYMPTOMS
Microsoft Exchange Server 2003 has a 32,768-byte (32KB) discretionary access control list (DACL) entry limit for each public folder.

If you exceed this limit when you try to modify the public folder permissions by using a MAPI program such as Exchange System Manager, you receive the following error message as expected:

Error 80040305

However, if you exceed this limit when you try to modify the public folder permissions programmatically through WebDAV by using the PROPPATCH method, you experience the following symptoms:
 * The PROPPATCH request to update the security descriptor of the public folder appears to succeed. When you view the HTTP response to the PROPPATCH request, you notice that HTTP returns a &quot;200 OK&quot; response.
 * The public folder permissions are not successfully updated.

You expect to receive an error response to a PROPPATCH request to update the security descriptor of a public folder if that update exceeds the 32KB DACL limit.



CAUSE
This problem occurs because Exchange does not correctly handle an error situation that occurs when Exchange sets the ptagNTSD data. In this situation, Exchange incorrectly overwrites the error code that Exchange receives.



Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
No prerequisites are required to apply this hotfix.

Restart requirement
You do not have to restart the computer after you apply this hotfix. However, the Microsoft Exchange Information Store service and all its dependent services are automatically stopped and then restarted when you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

817903 New naming schema for Exchange Server software update packages

Additional query words: XADM

Keywords: kbhotfixserver kbqfe kbfix kbbug kbpubtypekc KB915325

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.