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.
The activation of all modules took longer than expected to complete. Total Load Time: %1 Total Start Time: %2 Load Time Breakdown: %3 Start Time Breakdown: %4
This event indicates that an issue may exist that prevents the Microsoft Exchange Transport service (MSExchangeTransport.exe) from starting in a timely manner. You may experience this issue in one of the following scenarios.
Note These scenarios are not listed in their order of probability.
The SenderReputation database takes a long time to replay log files for a large information store database. This may indicate that the SenderReputation database is corrupted. In this scenario, MSExchangeTransport Event ID 14001 may be logged every five minutes. Additionally, a SenderReputation database event for successfully replaying log files is never displayed.
You apply an Exchange Update Rollup package to a computer on which the local computer account does not have Internet access. The binary files in the Update Rollup packages are digitally signed. This requires the computer to perform certificate validation checks to verify the packages. If the local computer account does not have direct access to the Internet, the certificate verification check must time-out. This issue may occur when the computer's default gateway does not allow for Internet access or when the computer uses an authenticating proxy server for Internet access.
An e-mail client that does not recognize the global message size restrictions is used. This may include earlier versions of Microsoft Outlook such as Microsoft Outlook 2003 SP1 and earlier versions. In this scenario, an e-mail client that does not recognize the global message size restrictions could submit excessively large messages for processing.
Exchange is installed on a domain controller.
Exchange is installed on a computer that has a slow disk subsystem.
An outdated version of an antivirus software is installed on the Exchange server.
The Microsoft Exchange Transport service controls the sending and receiving of messages in Microsoft Exchange Server 2010. When the service does not start in a timely manner, messages may become queued on the server. For more information, see Transport Architecture.
To resolve this problem, 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.
Examine the System log to determine whether the server is out of hard disk space or whether a problem affects one or more hard disk drives.
You may have to increase diagnostics logging to log the component startup sequence during the startup process of the Microsoft Exchange Transport service. To increase diagnostics logging for the Transport component, follow these steps:
In Registry Editor, locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\Current Control set\Services\MSExchangeTransport\diagnostics
Set the following REG_DWORD values to 7:
Temporarily disable any antivirus software to determine whether this improves the MSExchangeTransport startup time. If the startup time is improved, contact the antivirus vendor for an update of the program.
Move the contents of the SenderReputation folder to a new location to determine whether the issue is resolved. To do this, follow these steps:
Stop the Microsoft Exchange Transport service.
Locate the SenderReputation folder. By default, this folder has the following path:
Move the contents of the folder to a new location, and then start the Microsoft Exchange Transport service.
If Exchange is installed on a domain controller, review the information in Microsoft Knowledge Base article 940845, Services for Exchange Server 2007 or Exchange Server 2010 cannot start automatically after you install Exchange Server 2007 and Exchange Server 2010 on a global catalog server.
Allow the local computer to have account access to the Internet. For more information, see Microsoft Knowledge Base article 941990, A digitally signed .NET Framework 2.0 Windows application may start very slowly, or a Windows service may time out during startup.
If you cannot allow the computer account to have Internet access, try to increase the Windows services time-out value as a workaround. To do this, follow these steps:
In Registry Editor, locate and then click the following registry subkey:
On the Edit menu, point to New, and then click DWORD (32-bit) Value.
In the New Value #1 box, type ServicesPipeTimeout, and then press ENTER.
Right-click ServicesPipeTimeout, and then click Modify.
In the Value data box, enter the time-out value in milliseconds, and then click OK. For example, for a service time-out of 120 seconds, type 120000.
Exit Registry Editor, and then restart the computer.
Note To enable Service Control Manager to use the modified time-out value, you must restart the computer.
If you cannot allow the computer to have account Internet access, you can also try to modify the registry to reduce the certificate lookup time-out values as a workaround. To do this, specify the indicated DWORD values for the following registry subkeys:
Value name: ChainUrlRetrievalTimeoutMilliseconds
Value type: REG_DWORD
Value data: If this value is 0 (zero) or, if this value does not exist, a default value of 15000 milliseconds is used. To reduce the time-out, set this value to 5000.
Value name: ChainRevAccumulativeUrlRetrievalTimeoutMilliseconds
Value type: REG_DWORD
Value data: If this value is 0 (zero) or, if this value does not exist, a default value of 20000 milliseconds is used. To reduce the time-out, set this value to 7500.
To determine whether the issue is caused by the processing of excessively large e-mail messages, follow these steps:
Locate the mailbox or mailboxes from which the messages originate. In this scenario, the messages are being submitted. To locate the mailbox or mailboxes, use the Process Tracking log tool (Processtrackinglog.vbs).
For more information about how to obtain and run the Process Tracking log tool, see Exchange Server 2007 Process Tracking Log Tool and also see the Exchange Server Team Blog article, Process Tracking Log tool for Exchange Server 2007.
Look for entries that resemble the following:
User1@contoso.com <mailto:User1@contoso.com> submitted a message
multiple times that resulted in NDR - Size is 1303445440 bytes and sender is <>
(Postmaster for NDR)
Disconnect the mailbox or mailboxes that are stuck in submission, and then determine whether the Microsoft Exchange Transport service starts successfully.
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
If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.