frannac 0 Posted June 22, 2014 Share Posted June 22, 2014 Could someone please help me with the following errors ? Cmdlet failed. Cmdlet Set-TransportAgent, parameters {Identity=ESET Filtering AV Agent, Priority=2}. Cmdlet failed. Cmdlet Enable-TransportAgent, parameters {Identity=ESET Filtering AV Agent}. Cmdlet failed. Cmdlet Install-TransportAgent, parameters {Name=ESET Filtering AV Agent, TransportAgentFactory=XmonAgent.XmonAgentFactory, AssemblyPath=E:\Program Files\ESET\ESET Mail Security\XmonAgent.dll}. We're rolling out a new exchange server and busy with testing phase when we saw the above. Link to comment Share on other sites More sharing options...
ESET Moderators Aryeh Goretsky 386 Posted June 22, 2014 ESET Moderators Share Posted June 22, 2014 Hello, Can you tell us which version of ESET Mail Security for Microsoft Exchange Server and Microsoft Exchange Server (incl. SP level for the latter) you are running? Regards, Aryeh Goretsky Link to comment Share on other sites More sharing options...
Administrators Marcos 5,259 Posted June 24, 2014 Administrators Share Posted June 24, 2014 Does the following help? - disable ESET Transport agent in the advanced setup - wait at least 1-2 minutes for the change to apply - enable ESET Transport agent - wait at least 1-2 minutes for the change to apply - check if the issue persists Link to comment Share on other sites More sharing options...
Steven Theck 2 Posted June 30, 2014 Share Posted June 30, 2014 (edited) I am experiencing the same issue as frannac. I am using ESET Mail Security for Microsoft Exchange Server version 4.5.10022.0 on MS Exchange version 15.0.847.32 (2013 SP 1). I tried what Marcos recommended and it did not fix the issue. After digging deeper into the problem, I found that the "ESET Filtering AV Agent" Transport Agent is not being created in Exchange. I tried manually creating the Transport Agent from the PowerShell and received the following error: The TransportAgentFactory type "XmonAgent.XmonAgentFactory" doesn't exist. The TransportAgentFactory type must be the Microsoft .NET class type of the transport agent factory. Parameter name: TransportAgentFactory + CategoryInfo : InvalidArgument: ( [Install-TransportAgent], ArgumentException + FullyQualifiedErrorId : [Server=ExchangeServer,RequestId=5e13cc9d-1a7a-41b5-8822-bd8dcf4cf101,TimeStamp=6/30/2014 1 1:11:42 AM] [FailureCategory=Cmdlet-ArgumentException] 890B4548,Microsoft.Exchange.Management.AgentTasks.InstallTr ansportAgent + PSComputerName : exchangeserver.corp.mydomain.com Edited June 30, 2014 by Steven Theck Link to comment Share on other sites More sharing options...
Solution Steven Theck 2 Posted June 30, 2014 Solution Share Posted June 30, 2014 I found my solution to the problem, and hopefully it will help frannac and any others experiencing the issue. The errors occur with Exchange 2013 SP1 only, and are due to invalid XML code in the global assembly cache (GAC) policy configuration files. A permanent fix will be released with CU5, but Microsoft has released a fix for now. hxxp://support.microsoft.com/kb/2938053 Link to comment Share on other sites More sharing options...
frannac 0 Posted July 13, 2014 Author Share Posted July 13, 2014 Hi, sorry for the late reply, I actually managed to fix the issue by upgrading my Eset to the latest version. Even before upgrading to CU5 for exchange. But thank you Steven Theck ! Link to comment Share on other sites More sharing options...
Ronal 0 Posted March 10, 2015 Share Posted March 10, 2015 EDB repair tool can easily resolve exchange server. Link to comment Share on other sites More sharing options...
Recommended Posts