Messages that have attachments are not delivered as expected, and Event ID 12003 and 327 messages are logged in Exchange 2000 Server and in Exchange Server 2003

You may experience the following symptoms on your Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 computer:

• Messages that have attachments build up in the Simple Mail Transfer Protocol (SMTP) local delivery queue on the destination Exchange Server computer. These messages are encoded by using the Microsoft Outlook Rich Text formatting or the Transport Neutral Encapsulation Format (TNEF) content type.
• Messages that have attachments that use the MIME body part of the Application/MS-TNEF content type encoding are successfully delivered to the recipient.
• The Exchange Server computer cannot send messages that have attachments that are encoded using Rich Text TNEF. Messages that use the Rich text TNEF option and that are sent to another routing group or to the Internet are received without the attachment. The attachment icon is present, but when you try to open the attachment, you experience one of the following behaviors:
  • If you use Microsoft Outlook as a MAPI client, you receive the following error message:
    Operation Failed.
  • If you use Microsoft Outlook Web Access (OWA) or a Post Office Protocol version 3 (POP3) client, the attachment opens, but it is blank.
• The following event ID messages are logged in the Application log in the Event Viewer:

  Date: <date>
  Source: MSExchangeIS 
  Time: <time>
  Category: Content 
  Engine Type: Error 
  Event ID: 12003 
  User: N/A 
  Computer: <servername>
  Description: Error 80070003-82000387 occurred while processing message 5.169.5.0.0.13459.988140029@sender11.domain.com with subject 'test'.
  

  Date: <date> 
  Source: MSExchangeTransport
  Time: <time>
  Category: Exchange Store Driver 
  Type: Warning 
  Event ID: 327 
  User: N/A 
  Computer: <servername> 
  Description: The following call : EcSetFileHandleProp to the store failed. Error code : -2147024893. MDB : 5420fe97-20a4-4233-ab4d-ab05819a7959. FID : . MID : . File : C:\Program Files\Exchsrvr\Mailroot\vsi 1\Queue\NTFS_cbf2f24801c0cc77000000c6.EML.

• You may see an increase in nonpaged pool usage. This occurs because the file handles that are being allocated in IIS and are transferred to the Exchange Information Store. These file handles are kernel objects that are guaranteed to always be available in the memory. When the Exchange Information store is configured incorrectly, it cannot find the message file to set the file properties on by using file handles. Therefore, the handles are not used by the Exchange Information store and cannot be closed. These nonpaged pool allocations are represented by using an OvfL Tag and are listed with a source of EXIFS File Control Block Overflow List. In this case, the following error message may be seen in the System log:
  

  Event Type: Error 
  Event Source: Application Popup 
  Event Category: Srv 
  Event ID: 2019 
  Date: date 
  Time: time 
  User: N/A 
  Computer: computer name 
  Description: The server was unable to allocate from the system non-paged pool because the pool was empty. 
  

This problem may occur if you move the Exchange Server information store database files to another folder on the Exchange Server computer, and then delete the old folder in which those files were stored.

For example, if you install Exchange Server in the default installation folder (C:\Program Files\Exchsrvr), the database files are stored in the C:\Program Files\Exchsrvr\Mdbdata folder by default. If you move the database and log files to the E:\Program Files\Exchsrvr\Mdbdata folder, and then delete the C:\Program Files\Exchsrvr\Mdbdata folder, you may experience the behaviors described in the "Symptoms" section.

This problem occurs because the information about the folder in which the Exchange Server database and log files are stored is written to the Windows registry in the following location (where C:\Program Files\Exchsrvr\Mdbdata is the folder in which the database and log files are stored): The message conversion process uses the Working Directory parameter as its temporary directory during the conversion process. If the folder structure is missing, or if the registry entry points to location that is not correct, the conversion process is not successful

To resolve this problem, use one of the following methods:

Method 1: Re-create the Deleted Folder Structure

Re-create the deleted folder structure as it is referenced in the registry location that is specified in the "Cause" section.

Method 2: Edit the Registry to Point to the New Folder Structure

Edit the Windows registry to specify the new location of the Exchange Server database and log files. To do so, follow these steps.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
3. In the right pane of Registry Editor, double-click Working Directory.
4. Edit the path in the Value data box to point to the new location of the Exchange Server database and log files, and then click OK.
5. Quit Registry Editor.