This is the Trace Id: 2e58fba48ea699f985cdc47bec188f20

Bring the world closer with Bing Wallpaper

Download the free app and enjoy breathtaking views with a new background each day.
A laptop displaying a colorful seascape from Bing Wallpaper.

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

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.

Important! Selecting a language below will dynamically change the complete page content to that language.

Download
  • Version:

    1.0

    Date Published:

    7/15/2024

    File Name:

    Exchange2013-KB2938053-FixIt.zip

    File Size:

    770 bytes

    KB Articles:

    KB2938053

    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.
  • Supported Operating Systems

    Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Standard, Windows Server 2012, Windows Server 2012 R2


    Exchange Server 2013 SP1 System Requirements and Prerequisites
    For information about Exchange 2013 system requirements and prerequisites, see the following topics:
  • 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.

Follow Microsoft