[E2013][TA] Exchange 2013 SP1 transport agent "type not found" issue:
http://social.technet.microsoft.com/Forums/exchange/en-US/b0a54baa-cb03-4b18-8533-177c60f715f6/e2013ta-exchange-2013-sp1-transport-agent-type-not-found-issue?forum=exchangesvrdevelopment

"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?"

On 2/27/2014 12:07 PM, Adam Farage wrote:
:) Im not trolling, and the third party transport plugins eh? I would have to try that out tonight in my lab (if I am not too lazy and can put it back together).

Do we know in detail what actually breaks, is it just the third party transport agents or the transport services dreadlock?

------------------------------------------------------------------------
Date: Thu, 27 Feb 2014 14:44:10 -0500
Subject: Re: [Exchange] Just so you know....
From: [email protected]
To: [email protected]

Well, yes. But his language suggested he was looking for something, not wanting to create strife and discord.


On Thu, Feb 27, 2014 at 2:37 PM, Richard Stovall <[email protected] <mailto:[email protected]>> wrote:

    I think you're assuming he's not trolling...

    :)


    On Thu, Feb 27, 2014 at 2:26 PM, Jonathan Link
    <[email protected] <mailto:[email protected]>> wrote:

        Well, I think you're trawling, not trolling... :D


        On Thu, Feb 27, 2014 at 2:23 PM, Adam Farage
        <[email protected] <mailto:[email protected]>> wrote:

            Completely understood :) I will troll through the Technet
            forums to see if I can get some inkling of what it could be.

            
------------------------------------------------------------------------
            From: [email protected] <mailto:[email protected]>
            To: [email protected]
            <mailto:[email protected]>
            Subject: RE: [Exchange] Just so you know....
            Date: Thu, 27 Feb 2014 19:16:09 +0000


            At this point they are considered NDA. Since multiple TAPs
            are reporting it, it’s a good bet I’ll be able to say
            something soon.

            *From:*[email protected]
            <mailto:[email protected]>
            [mailto:[email protected]
            <mailto:[email protected]>] *On Behalf Of
            *Adam Farage
            *Sent:* Thursday, February 27, 2014 2:10 PM
            *To:* [email protected]
            <mailto:[email protected]>
            *Subject:* RE: [Exchange] Just so you know....

            Care to share, or are they NDA?

            I haven't deployed 2013 for a large (10,000+ users) yet,
            but I do have one coming up in a few weeks...
            
------------------------------------------------------------------------
            From: [email protected] <mailto:[email protected]>
            To: [email protected]
            <mailto:[email protected]>

            Subject: [Exchange] Just so you know....
            Date: Thu, 27 Feb 2014 19:02:47 +0000

            There are a couple of important issues bubbling up from
            Exchange 2013 SP1…. I’m running it in prod, but you may
            want to hold off a week or two until we see how those play
            out…





--
Got your CryptoLocker prevention in place?
http://www.thirdtier.net/2013/10/cryptolocker-prevention-kit-updates/
Only two more patching days of XP.... are you ready?



Reply via email to