Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Outgoing SMTP messages remain in the outgoing message queue, and event ID 4000 is logged on the computer that is running Exchange 2000 Server and Exchange Server 2003

Outgoing SMTP messages remain in the outgoing message queue, and event ID 4000 is logged on the computer that is running Exchange 2000 Server and Exchange Server 2003

View products that this article applies to.

Symptoms

You may experience the following symptoms on a computer that is running Microsoft Exchange Server 2003 and Microsoft Exchange 2000 Server:
  • Incoming Simple Mail Transfer Protocol (SMTP) messages are delivered to e-mail recipients.
  • Outgoing SMTP messages remain in the outgoing message queue on the Exchange computer and are not delivered to some domains.

    Note If you perform additional troubleshooting, you notice that mail is successfully delivered only to e-mail servers that advertise the Extended Simple Mail Transfer Protocol (ESMTP) CHUNKING verb. Examples of e-mail servers that advertise the CHUNKING verb include Exchange 2003 and Microsoft Exchange 2000 Server.
  • In Exchange Server 2003, the following event is logged in the Application log:

    Event type: Warning
    Event source: MSExchangeTransport
    Event category: Connection Manager
    Event ID: 4000
    Description: Message delivery to the remote domain 'remotesmtphost.com' failed for the following reason: The handle is invalid.


    In Exchange 2000 Server, the following event is logged in the Application log:

    Event type: Warning
    Event source: smtpsvc
    Event category: None
    Event ID: 4000
    Description: Message delivery to the remote domain ' remotesmtphost . com ' failed for the following reason: The handle is invalid.

↑ Back to the top

Cause

This issue may occur if the local operating system account (SYSTEM) either cannot read from the temporary directory on the computer or cannot write to the temporary directory on the computer.

Note Exchange may create a temporary file that named "Dst*.tmp" in the temporary directory when remote domains do not support the bdat command.

↑ Back to the top

Resolution

To troubleshoot this issue, follow these steps:
  1. Right-click My Computer, and then click Properties.

    Note In Microsoft Windows Server 2003, click Start, right-click My Computer, and then click Properties.
  2. Click the Advanced tab, and then click Environment Variables.
  3. In the System variables list, note the values that correspond to the TEMP variable and the TMP variable. For example, note the values from the following table.
    VariableValue
    TEMPC:\WINNT\TEMP
    TMPC:\WINNT\TEMP
  4. For the folder that you noted in step 3, verify all the following:
    • Verify that a valid path to the folder exists. To change the path back to default value, follow these steps:
      1. Click the variable that is named TEMP, and then click Edit.
      2. Change the variable value to %SystemRoot%\TEMP, and click OK.
      3. Click the variable that is named TMP, and then click Edit.
      4. Change the variable value to %SystemRoot%\TEMP, and click OK.
      5. Restart Exchange to enable the new system environment variables to take affect.
      Note You may also change the TEMP variable and the TMP variable by using Regedit.exe. They are located in the following registry location:
      HKEY_Local_Machine\System\CurrentControSet\Control\SessionManager\Environment
    • Verify that the drive where the folder is located has sufficient hard disk space available.
    • Verify that the SYSTEM account has Full Control permissions assigned for the folder or that the SYSTEM account has at least Read permissions and Write permissions to the folder. To do this, follow these steps:
      1. Start Windows Explorer, locate and then right-click the folder that the TEMP variable or the TMP variable points to, and then click Properties.
      2. In the Temp Properties dialog box, click the Security tab, and then click SYSTEM in the Name list.
      3. Verify that the Full Control check box is selected in the Allow column.

        Note If the Full Control check box is not selected in the Allow column, verify that the Read check box in the Allow column is selected and that the Write check box in the Allow column is selected.
    • If you are running a file-level antivirus program, make sure that the antivirus program has not locked the files in the TEMP folder. For more information about how to do this, contact the antivirus program vendor.

      For information about your hardware manufacturer, visit the following Web site:
      http://support.microsoft.com/gp/vendors/en-us
    • If disk quotas are enabled on the volume where the folder is located, verify that the quota has not been reached. To view the quota settings for a particular volume, follow these steps:
      1. Right-click the volume, and then click Properties.
      2. Click the Quota tab.
      For more information about how to manage disk quotas, visit the following Microsoft Web site:
      http://technet2.microsoft.com/windowsserver/en/library/ac77bbbe-72f5-4d4e-b651-33680bdb9f791033.mspx

↑ Back to the top

More information

For more information about how to configure or deploy Exchange 2003, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/bb123872.aspx

↑ Back to the top

Keywords: KB899392, kbprb, kbtshoot, kbexchstore

↑ Back to the top

Article Info
Article ID : 899392
Revision : 3
Created on : 9/3/2013
Published on : 9/3/2013
Exists online : False
Views : 300