Mailbox quota is exceeded when you expand a recurring calendar item in Exchange 2000 Server (317362)



The information in this article applies to:

  • Microsoft Exchange 2000 Server

This article was previously published under Q317362

SYMPTOMS

When you view a recurring appointment by using Microsoft Outlook Web Access (OWA) or when you open that recurring appointment by using a Collaboration Data Objects (CDO) program, your mailbox size increases to the point where you might exceed your mailbox quota.

CAUSE

This problem occurs if the following conditions are true:
  • The recurring appointment contains a message attachment.
  • You view the appointment by using Monthly view or Weekly view in OWA, or you open that appointment by using a CDO program that expands the instances of that appointment.
This problem occurs because when an appointment item is expanded by CDO, the size of each instance of that expanded appointment item is counted toward the mailbox storage limit. CDO expansion of an appointment item occurs when you view that item from the OWA calendar or when you access that item by using CDO.

Therefore, if a recurring appointment item contains an attachment, the size of each instance of that attachment together with the size of each instance of that appointment item is counted against the mailbox storage limit that is assigned in Microsoft Exchange 2000 Server.

For example, you have a recurring appointment that contains a 50 kilobyte (KB) attachment. In this scenario, this attachment counts as 50 KB toward your mailbox storage limit. However, if you view that appointment by using the Monthly view in OWA, the recurring appointment is automatically expanded with each instance of that 50 KB attachment counting toward your mailbox storage limit. Depending on the recurrence of the appointment, this attachment could count as hundreds of KB toward your mailbox storage limit even though the actual size of the message in the Microsoft Exchange Information Store has not changed.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was corrected in Microsoft Exchange Server 2003.

Modification Type:MajorLast Reviewed:8/17/2004
Keywords:kbDiskMemory kbenv kbFirewall kbtshoot kbprb kbbug KB317362 kbAudDeveloper kbAudITPRO