MSExchangeTransport 17012

  • Article

 

This article provides an explanation and possible resolutions for a specific Exchange event. If you don't find what you’re looking for here, try searching Exchange 2010 Help.

Details

Product Name

Exchange

Product Version

14.0

Event ID

17012

Event Source

MSExchangeTransport

Category

Storage

Symbolic Name

JetInitInstanceOutOfMemory

Message Text

%1: The database could not allocate memory. Please close some applications to make sure you have enough memory for Exchange Server. The exception is %2.

Explanation

This Error event may indicate that the Microsoft Exchange Server 2010 Transport server is under a heavy load. This Error event is logged when the Microsoft Exchange Transport service has insufficient memory to run the Transport database Mail.que. If the Microsoft Exchange Transport service is unable to load the Transport database, the service stops.

Starting with Microsoft Exchange Server 2007, the Microsoft Exchange Transport service uses an Extensible Storage Engine (ESE) database for mail queue storage. This design change improves read and write performance with respect to messaging queues and also allows for the messaging queues to be backed up.

By default, the Exchange 2010 Transport database (Mail.que) is located in the following directory:

%ProgramFiles%\Microsoft\Exchange Server\V14\TransportRoles\data\Queue

If the Transport server has insufficient RAM to run the Transport database, the Microsoft Exchange Transport server will be unable to process messages and may shut down.

This issue may occur when one or more of the following conditions are true:

  • Many uncommitted database transactions (version buckets) exist. This may be caused by virus-related issues, corrupted messages, queue database integrity issues, or hard disk drive-related issues, such as performance or storage space issues.

  • A very large message size limit is configured in Exchange.

  • The server does not have enough RAM installed to host the Exchange roles that it is running.

  • A file-level antivirus program does not have exclusions configured for the Exchange-related files and directories.

  • The server is running as a virtual machine that is subject to the memory overcommit feature in the virtualized environment.

User Action

To troubleshoot this issue, do one or more of the following:

  • Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.

  • Review the Operations Console in Operations Manager for detailed information about the cause of this problem. For more information, see the "Introduction" section in this article.

  • If a file-level antivirus scanner is running, verify that antivirus exclusions are configured appropriately. For more information, see File-Level Antivirus Scanning on Exchange 2010.

  • Examine the global message size limits in Exchange. To do this, follow these steps:

    1. Start the Exchange Management Console, expand Organization Configuration, and then click Hub Transport.

    2. In the details pane, click the Global Settings tab, click Transport Settings, and then click Properties.

    3. On the General tab, review the transport limits. By default, the maximum message size is 10 MB.

    For more information, see Understanding Message Size Limits.

  • To view individual message limits, follow these steps:

    1. In the Exchange Management Console, expand Recipient Configuration, and then click Mailbox.

    2. In the details pane, click a mailbox, and then click Properties.

    3. Click the Mail Flow Settings tab, click Message Size Restrictions, and then click Properties.

  • Verify that the server has enough RAM installed for the Exchange roles that are running. For more information, see the following topics:

  • You may want to review the back pressure configuration settings on the server. This information is stored in the EdgeTransport.exe.config file. The file is located in the following folder on the Transport server:

    %ProgramFiles%\Microsoft\Exchange Server\V14\Bin

    Note   We recommend that you do not modify the back pressure settings.

    For more information about the back pressure settings, see the "Back Pressure Configuration Options in the EdgeTransport.exe.config File" section in Understanding Back Pressure.

  • You may want to increase diagnostics logging to log the components in the transport pipeline. To increase diagnostics logging for the Transport components, follow these steps:

    1. In the Exchange Server 2010 Management Console, expand Server Configuration, and then click Hub Transport.

      Note   For an Edge Transport server, click Edge Transport.

    2. In the Actions pane, click Manage Diagnostic Logging Properties for the appropriate server.

    3. Expand MSExchangeTransport.

    4. Click the following components, and then click Expert, then click Configure for each component:

    • Smtpreceive

    • Smtpsend

    • DSN

    • Components

    • Remote Delivery

  • If Exchange is running on a virtual machine, verify that the memory over-commit or memory over-subscription functionality is turned off for the particular virtual machine. For more information, see the "Exchange Server Memory Requirements and Recommendations" section under "Hardware Virtualization" in Exchange 2010 System Requirements.

  • Determine whether the transport database is corrupted. To do this, follow these steps:

    1. Stop the Microsoft Exchange Transport service.

    2. Remove the transport database. To do this, rename the following folder:

      %ProgramFiles%\Microsoft\Exchange Server\V14\TransportRoles\data\Queue

    3. Start the Microsoft Exchange Transport service to determine whether mail flow is restored.

  • Resolve your issue by using self-support options, assisted support options, and other resources. You can access these resources from the Exchange Server Solutions Center. From this page, click Self-Support Options in the navigation pane to use self-help options. Self-help options include searching the Microsoft Knowledge Base, posting a question at the Exchange Server forums, and other methods. Alternatively, in the navigation pane, you can click Assisted Support Options to contact a Microsoft support professional. Because your organization may have a specific procedure for directly contacting Microsoft Product Support Services, be sure to review your organization's guidelines first.

For more information about the transport pipeline in Exchange 2010, see Understanding Transport Pipeline and also the Exchange Server Team blog article,

Exchange 2010 Transport Architecture Diagrams Available for Download.

The content of each blog and its URL are subject to change without notice. The content within each blog is provided "AS IS" with no warranties, and confers no rights. Use of included script samples or code is subject to the terms specified in the Microsoft Terms of Use.