Troubleshooting the "452 4.3.1 Out of memory" error message in Exchange Server 2003 and in Exchange 2000 Server
This article was previously published under Q329167
This article has been archived. It is offered "as is" and will no longer be updated.
You may experience one or more of the following issues on a server that is running Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 in your organization:
- Messages may become backed up in the messaging queues. You may not be able to resolve this issue by restarting the Exchange 2000 Server-related services or the Exchange Server 2003-related services. Instead, you have to restart the server to restore message flow.
- When you telnet to port 25 of the problem server, and issue the MAIL FROM: or DATA command, you receive the following error message: 452 4.3.1 Out of memory
- The Exchange server logs the following event in the Application event log:Event ID: 429
Event Source: SMTPSVC
Event Type: Error
Description: "Virtual Server Invalid MailQueue Directory: The specified mail queue directory is not valid. Cannot start the SMTP Service."
This problem may be caused by one or more reasons. Some of the most common causes are as follows.
Cause 1This issue may occur if the Antigen antivirus event sink (version 6.5) is installed on your computer. This issue may be caused by a leak of MailMsg objects.
Exchange 2000 Server or Exchange Server 2003 has a default limit of 90,000 MailMsg objects that can be allocated. When this limit has been reached, the Exchange server cannot process additional messages. For more information about the limit, click the following article number to view the article in the Microsoft Knowledge Base:
258748 How to set a limit on the number of SMTP messages in queues
Cause 2The Exchange routing engine does not have sufficient permissions to write the messages to the BadMail, Pickup, and Queue folders that are located under the \Mailroot\VSI # folder.
Cause 3This problem may occur if your Exchange server received a large amount of spam e-mail messages. In this situation, the BadMail folder fills with messages that your server cannot handle. Additionally, the hard disk is almost full.
Because there may be several causes of this problem, use one or more of the following resolutions as appropriate for your situation.
Resolution 1To work around this issue, unbind the Antigen event sink from the SMTP virtual server in Exchange 2000 Server or in Exchange Server 2003. This workaround applies only to Antigen version 6.5. To do this, follow these steps.
Note Obtain and install the following utilities before you follow these steps:
- Tlist.exe: On the Windows 2000 CD-ROM, extract the Tlist.exe utility from the Support.cab file in the Support\Tools folder.
- Smtpreg.vbs: To obtain this, download and install the Exchange Server SDK. To do this, visit the following Microsoft Web site:
- Determine whether the Antigen event sink is loaded. To do this:
- Click Start, click Run, type cmd in the Open box, and then click OK.
- Locate the folder in which you extracted the Tlist.exe utility, and then type the following command: tlist inetinfoIf AntigenSmtpSink.dll is displayed in the list of loaded DLL files, the Antigen event sink is loaded.
- Determine whether the Antigen event sink is bound to the SMTP virtual server. To do this:
322756 How to back up and restore the registry in Windows
- Click Start, click Run, type cmd, and then click OK.
- Locate the folder in which the Smtpreg.vbs file is stored (by default, C:\Program Files\Microsoft SDK\Include), and then type the following command:cscript smtpreg.vbs /enum > before.txt
- Open the Before.txt file by using a text editor such as Notepad, and then search for "Antigen." (Note that it is bound to the SMTP Transport OnPostCategorize event.) Quit Notepad.
- Click Start, click Run, type regedit in the Open box, and then click OK.
- Navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Sybari Software\Antigen for Exchange
- On the Registry menu, click Export Registry File.
- In the File name box, type exported antigen, and then click Save.
Note If you have to undo the changes to this registry subkey, double-click the Exported Antigen.reg file that you saved.
- In the right pane of the Registry Editor window, right-click the AntigenEnabled value, and then click Modify.
- Set the AntigenEnabled value to 0x1 (by default, it is 0x3).
Note This key specifies whether the Antigen Service is to be enabled for scanning.
- 0 disables all scanning.
- 1 enables scanning in the Information Store only (Realtime, Manual, and MTA).
- 2 enables the Internet Scan Job only.
- 3 (default) enables all scanning.
- Quit Registry Editor
- Stop and then restart the Antigen IMC service.
Note When you stop the Antigen IMC service, the Simple Mail Transfer Protocol (SMTP) service is also stopped.
- To completely unload the Antigen event sink, stop and then restart the Microsoft Internet Information Services (IIS) Admin service.
This also stops all dependent services, such as the Microsoft Exchange information store, SMTP, Microsoft Exchange MTA Stacks, the World Wide Web Publishing service, and others.
- Run the tlist inetinfo command to verify that AntigenSmtpSink.dll is not displayed in the list of loaded DLL files.
- Verify that the Antigen event sink is no longer bound to the SMTP virtual server. To do this:
- Click Start, click Run, type cmd, and then click OK.
- Locate the folder in which the Smtpreg.vbs file is stored (by default, C:\Program Files\Microsoft SDK\Include), and then type the following command:cscript smtpreg.vbs /enum > after.txt
- Open the After.txt file by using a text editor such as Notepad, and then search for "Antigen." (Antigen should not appear in the text file.) Quit Notepad.
- Use Windows Explorer to check the VSI # folder. By default this folder is located in the Exchange installation point: \exchsrvr\mailrootNote VSI 1 corresponds to SMTP Virtual Server 1, VSI 2 corresponds to SMTP Virtual Server 2, and so on.
- Right-click the VSI # folder, and then click Properties.
- Click the Security tab, and then confirm that the System account exists in the Name box.
- Click the System account, and then confirm that Full Control permissions are enabled.
- Repeat steps 2 through 4 for the BadMail, Queues, and Pickup subfolders that are located under Exchsrvr\Mailroot\Vsi #.
- If you find that the System account is not listed in the Access Control List (ACL), add the System account. Additionally, and assign the account Full Control access permissions.
- Stop and then restart the Simple Mail Transport Protocol (SMTP) service and the Microsoft Exchange Routing Engine service.
Resolution 3To resolve this issue, follow these steps:
- Stop the SMTP service. To do so, follow these steps:
- In Computer Management, double-click the Services and Applications branch, and then click Services.
- In the right pane, right-click Simple Mail Transport Protocol (SMTP), and then click Stop.
- In Windows Explorer, locate the \Exchsrvr\Mailroot\Vsi # folder.
Important Do not open the BadMail folder. Depending on how much spam that the Exchange server processes, this folder may contain several hundred thousand files. If you open this folder, the server may appear to stop responding.
- Permanently delete the BadMail folder. To do this, click the BadMail folder in Windows Explorer, press and hold the SHIFT key, and then press DELETE.
Note Deleting this folder may take a long time, depending on the number of files that the folder contains.
- Create a new BadMail folder.
- Start the SMTP service.
867642 How to automatically delete messages from the Badmail folder in Exchange Server 2003 and in Exchange 2000 Server
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
238614 How to set up Regtrace for Exchange 2000
Article ID: 329167 - Last Review: 12/07/2015 12:40:21 - Revision: 2.5
Microsoft Exchange 2000 Server Standard Edition, Microsoft Exchange Server 2003 Enterprise Edition, Microsoft Exchange Server 2003 Standard Edition
- kbnosurvey kbarchive kberrmsg kbbug kbpending KB329167