This article has been archived. It is offered "as is" and will no longer be updated.
The Exchange 2000 information store may report an event ID 327 warning message that indicates that the virtual memory may be fragmented. When the server is in this state, the Simple Mail Transfer Protocol (SMTP) protocol cannot send and receive e-mail messages.
The Application event log may contain the following warning messages:
Event Type: Warning Event Source: MSExchangeTransport Event Category: Exchange Store Driver Event ID: 327 Date: 1/17/2002 Time: 09:20:57 User: N/A Computer: MS1 Description: The following call : EcCopyTo to the store failed. Error code : -2147024882. MDB : 867d0828-32b8-409c-a733-6c4fd2c9ba4c. FID : . MID : . File : C:\Program Files\Exchsrvr\Mailroot\vsi 1\Queue\NTFS_36d5199001c19ec500019407.EML.
Event Type: Warning Event Source: MSExchangeTransport Event Category: Exchange Store Driver Event ID: 327 Date: 1/15/2002 Time: 12:24:42 User: N/A Computer: MS1 Description: The following call : EcGetMime to the store failed. Error code : -2147467259. MDB : 867d0828-32b8-409c-a733-6c4fd2c9ba4c. FID : 1-35. MID : 1-1B981AA. File :
The following event ID 9582 error message may be logged in the Application event log because of prior errors, which cause virtual memory fragmentation:
Event Source: MSExchangeIS Event Category: Performance Event ID: 9582 Type: Error Description: The virtual memory necessary to run your Exchange server is fragmented in such a way that normal operation may begin to fail. It is highly recommended that you restart all Exchange services to correct this issue.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:
To work around this problem, either restart the SMTP service or restart the server.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.