Microsoft KB Archive/329067

= Information about performance issues that occur when you use POP3, IMAP, or WebDAV clients, such as Entourage, after you move mailboxes in Exchange Server 2003 or in Exchange 2000 Server =

Article ID: 329067

Article Last Modified on 10/25/2007

-

APPLIES TO


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

-



This article was previously published under Q329067



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



Performance issues in POP3, IMAP4, and WebDAV clients
When the following client computers connect to Microsoft Exchange 2000 Server and Microsoft Exchange Server 2003, they fully use the streaming store (.stm) file to read and write data:
 * Internet protocol (IP) client computers that are using Internet Message Access Protocol 4 (IMAP4) or Post Office Protocol 3 (POP3).
 * WebDAV-based clients, such as Microsoft Entourage 2004

If you use the Move Mailbox functionality in Active Directory Users and Computers to move data, the data is moved into the .edb file. Therefore, clients that use POP3, IMAP4, and WebDAV protocols to access their mailboxes may experience performance issues after you move their mailboxes between databases or servers.

For clients that use POP3 or IMAP, after the user logs on, message sizes must be calculated and MAPI-to-MIME conversion occurs in memory and on the disk of the server. In large environments this calculation can take much time.

For clients that use WebDAV clients, such as Entourage 2004, severe performance issues on the server side may be caused when content is converted for large messages in the Inbox and in other folders. In extreme cases, very large temporary files may be created on the server that is running Exchange Server when this issue occurs in POP3, IMAP4, or WebDAV scenarios.

Performance issues in WebDAV clients
In addition to the issues that were described in the previous section, WebDAV client users, such as Entourage or Outlook Web Access users, may experience other issues. In Entourage, messages may remain in the Outbox or the Drafts folder. Additionally, the following event may be logged in the Application log: Event ID : 1000

Event Type : Error

Event Source : Application Error

Computer : Server_Name

Description : Faulting application w3wp.exe, version Version_Number, faulting module exprox.dll, version Version_Number, fault address 0x0002ce94

Outlook Web Access users will sometimes receive the following error in the Web browser:

500 Internal Server error

Additionally, when an Outlook Web Access user or an Entourage user accesses the Exchange server, Internet Information Services (IIS) may stop responding on the Exchange server. Then, you may receive the following error message:

IIS worker process encountered a problem and needed to close

These issues occur when Outlook Web Access users or Entourage users download large attachments to the client computers that exceed the current message size limit. For example, attachments in older messages that exceed the current message size limit will cause these issues. Although users cannot send or receive large messages that exceed the current message size limit, the users can still access older messages that were delivered before the current message size limit was configured.



MORE INFORMATION
If you are moving hundreds or thousands of mailboxes, you can use one or more of the following methods to prevent performance issues:
 * Make sure that the TMP/TEMP environment variables point to a very fast RAID 0+1 spindle set (up to 12 disks for large mailbox servers). For stand-alone mailbox servers, we recommend that you adjust the system environment TMP/TEMP variables. For server clusters, we recommend that you configure the variables for the service account under which the server cluster is running.
 * Add the Compatibility registry value. This valueinforms the store to use approximate instead of exact calculations for message sizes. The following sections describe this procedure in more detail.
 * Add the MaxResponseSizeInBytes registry value in Exchange Server 2003.

Add the Compatibility registry value for POP3 users
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

The Compatibility registry value can be used to instruct the Exchange store to use approximate message sizes instead of calculating exact message sizes for POP3.

Add the Compatibility registry value for POP3 users
 Start Registry Editor. Locate and then click the following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ POP3svc\Parameters

 On the Edit menu, click Add Value, and then add the following registry value:

Value name: Compatibility

Data type: REG_DWORD

Radix: Hexadecimal

Value data: 0xfffffffe

 Exit Registry Editor.

Enable fast message retrieval for IMAP4 users

 * 1) Open the properties of the IMAP4 virtual server.
 * 2) On the General tab, click to select the Enable fast message retrieval check box, and then click OK.

For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:

317722 Client latencies occur when Exchange 2000 converts mail from MAPI to MIME format

Add the MaximumResponseSizeInBytes registry value in Exchange Server 2003 for WebDAV clients such as Entourage
The MaximumResponseSizeInBytes registry value helps allocate more memory to the IIS worker process when Entourage users are working with large messages.

When content conversion occurs in Exchange Server for large messages, IIS may run out of memory space when it tries to sustain the communication pipe between Exchange Server and the Entourage client. When you set a larger value for this registry key, you help IIS sustain the communication pipe and the content conversion process for large messages.

Content conversion happens only when such messages are accessed by users in Entourage. Therefore, the effect on performance is distributed over time.

Add the MaximumResponseSizeInBytes registry key to at least those Exchange Server 2003 front-end and back-end servers that Entourage users use to connect to their Exchange Server mailboxes. To do this, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.  Start Registry Editor.</li> Locate and then click the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeWEB\DAV

Note By default, the  key is not in the registry. You will have to create it yourself.</li> On the Edit menu, click Add Value, and then add the following registry value:

Value name: MaximumResponseSizeInBytes

Data type: REG_DWORD

Radix: Decimal

Value data:

Note To calculate a value for the Value data field, determine the size of the largest message that you want the users to be able to send and receive. For example, if you decide to limit message size to 50 megabytes (MB) and under, you would use the following calculation:

1024 * 1024 * 50 = 52428800 (Decimal) = 3200000 (Hexadecimal)

Enter the results of this calculation in the Value data field. In this example, you would enter 52428800 (Decimal) or 3200000 (Hexadecimal). Remember that the configurable range for this registry key is 1 MB to 1 gigabyte (GB). Better results occur if customers set it to a value of 500 MB or a higher value such as 800 MB. We recommend that you set the value back to the default value or to a lower value after the content conversion issue subsides in your organization. The default value of this registry key is 128 MB. We also recommend that you set correct messages limits and mailbox size limits on your Exchange server to prevent performance issues.</li> Exit Registry Editor.</li></ol>

To put this registry key into effect under Internet Information Services (IIS), restart the Exchange Application Pool. Then, if an Entourage user tries to work with a message that is larger than the value in the Value data field, the user may experience performance issues. An oversize message may also cause performance issues on the server side. This may affect other users. '''

Important''' This registry key works only for Exchange Server 2003. It does not work for Exchange 2000 Server.

Additional query words: conversion slow XADM

Keywords: kbhowto kbinfo KB329067

-

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

© Microsoft Corporation. All rights reserved.