XADM: Message Flow to the Local Delivery Queue Is Very Slow (314744)

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

E-mail messages are backing up on the Simple Mail Transfer Protocol (SMTP) queue that is bound for local delivery. Additionally, the server experiences high disk queue lengths on the Exchange 2000 Server computer installation drive. Typically, this installation drive is drive:\Program Files\Exchsrvr\.

CAUSE

This behavior can occur because the information store uses the working folder parameter setting that is defined in the registry for e-mail message conversion (there are several reasons and types of conversion scenarios). If this folder is on a slower drive, the conversion process can become very slow and as a result, e-mail messaging flow appears to stop.

RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this behavior, change the path of this parameter to point to a faster drive, to do so:

Start Registry Editor (Regedt32.exe).
Locate, and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
On the Edit menu, click Add Value, and then add the following registry value:
Value name: Working Folder
Data type: REG_SZ: Folder Path
Quit Registry Editor.

NOTE: Make sure that you create the new path entered on the new drive. The new path is not created automatically.

MORE INFORMATION

A dump file indicates several threads waiting on a disk write. The following text is one example of a Multipurpose Internet Mail Extensions (MIME) conversion:

00 1916f78c 77e95d35 ntdll!_ZwWriteFile+0xb
01 1916f7f8 0044ec20 KERNEL32!WriteFile+0xc5
02 1916f840 00450b66 store!EcIFSWrite+0x84
03 1916f85c 00450b39 store!CIfsStream::HrWriteFile+0x21
04 1916f87c 00450af2 store!CIfsStream::HrFlushWriteCache+0x36
05 1916f888 00702bb1 store!CIfsStream::Commit+0x10
06 1916f8a0 610df63e store!CCRLFTermIfsStream::Commit+0x44
07 1916f8e4 610df451 exmime!CMessageTree::_HrWriteMessage+0x1aa
08 1916f90c 0045a5e4 exmime!CMessageTree::Save+0x83
09 1916f92c 0044a357 store!CMimeMessageOut::RefreshMime+0x62
0a 1916f954 00426ad4 store!CMdbConverter::HrConvert+0x1b5
0b 1916f974 00463b66 store!CMdbConverter::HrEnsureMime+0x26
0c 1916f990 00463ab2 store!CMdbConverter::HrGetMimeFile+0x35
0d 1916f9b0 00463779 store!CIMailConvert::HrGetFileHandleProp+0xaa
0e 1916fb6c 158e0411 store!EcGetMimeOp+0x2b9
0f 1916fbb4 158e365b EXSMTP!CMdbLogon::HrGetMessageContent+0x7d
10 1916fce0 158e3754 EXSMTP!COmsgWrapper::HrGetContentHandle+0x2de
11 1916fd14 158e7069 EXSMTP!COmsgWrapper::HrReOpen+0x36
12 1916fef4 158d253c EXSMTP!rosfnReOpen+0x17a
13 1916ff10 158d2c29 EXSMTP!Dispatch+0x132