Microsoft Download Center Archive

Third-party transport agents cannot be loaded correctly in Exchange Server 2013 SP1

  • Published:
  • Version: 1.0
  • Category: Tool
  • Language: English

Describes an issue in which the Exchange Transport service cannot start in Exchange Server 2013. This issue occurs when third-party transport agents do not load correctly.

  • After you install Microsoft Exchange Server 2013 Service Pack 1 (SP1) or you upgrade an existing Microsoft Exchange Server 2013 installation to Exchange Server 2013 SP1, third-party or custom-developed transport agents cannot be installed correctly. Additionally, the Microsoft Exchange Transport service (MSExchangeTransport.exe) cannot start automatically. Specifically, you cannot enable third-party products that rely on transport agents. For example, you cannot enable anti-malware software or custom-developed transport agents. When the installation fails, you also receive an error message that resembles the following:The TransportAgentFactory type must be the Microsoft .NET class type of the transport agent factory.
Knowledge Base Articles:

Files

Status: Live

This download is still available on microsoft.com. The downloads below will come directly from the Microsoft Download Center.

FileSize
Exchange2013-KB2938053-FixIt.zip
SHA1: 2e8d8506b17a842023e466e4d312c63295bf4174
1 KB

File sizes and hashes are retrieved from the Wayback Machine’s indexes. They may not match the latest versions of files hosted on Microsoft servers.

System Requirements

Operating Systems: Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Standard, Windows Server 2012, Windows Server 2012 R2

Installation Instructions

  • Microsoft has developed a PowerShell script that corrects a formatting error in the configuration files that govern the Transport Extensibility that is built into Exchange Server 2013. To resolve the formatting error so that Transport Extensibility and third-party products that use this capability function correctly, run the script on a server that experiences the symptoms that are mentioned in the “Symptoms” section.