none
[E2013][TA] Exchange 2013 SP1 transport agent "type not found" issue

    General discussion

  • Our transport agents fail to install or run with "type not found" errors under Exchange 2013 Service Pack 1.

    The agents in question reference the Exchange 2007 public assemblies (version 8.0) to achieve Exchange version-neutrality. This has worked fine since Exchange 2007 and was enabled by an assembly redirection policy that Microsoft shipped with Exchange. This policy mapped 8.0 assemblies to the most recent version.

    While investigating this issue, we have found Exchange 2013 SP1 still has such policy in place, but the policy is not a valid XML file. According to the the Assembly Binding Log Viewer (fuslogvw.exe), this causes the redirection policy to be ignored. Once we remove the offending comment line (new to SP1), the redirection policy seem to get applied and the transport agents install just fine.

    If we are missing something and this is not a bug, what is the recommended practice now to build transport agents that are not specifically linked against a given Exchange release?

    Thursday, February 27, 2014 11:41 AM

All replies