ESET V4 on Server 2008 & Exchange

Hi. We have been having problmes with ESET V 4 on server 2008 and have taken it off. We now hget an event log error every time we try to start Microsoft Exchange Transport.

The Service Will Be Stopped.
Loading of component 'AgentComponent' Failed.

The service then stops.

Can someone help please?

 

Is it Small Business Server 2008? If so, was it restarted after installation / uninstallation of EMSX? Could you please elaborate more on the issues you've had with EMSX on the server?

 

Hi there. Server has been freezing up randomly and causing really slow logins. We rebooted into safe mode and run the uninstall tool. Then rebooted back into normal mode, and now exchange can't start the transport service.

Here is the error.

Microsoft Exchange couldn't start transport agents. The Microsoft Exchange Transport service will be stopped. Exception details: Failed to create type 'XmonAgent.XmonSmtpAgentFactory' from assembly 'C:\Program Files\ESET\ESET Mail Security\XmonAgent.dll' due to error 'Invalid agent assembly path.'. : Microsoft.Exchange.Data.ExchangeConfigurationException: Failed to create type 'XmonAgent.XmonSmtpAgentFactory' from assembly 'C:\Program Files\ESET\ESET Mail Security\XmonAgent.dll' due to error 'Invalid agent assembly path.'. ---> System.ArgumentException: Invalid agent assembly path.
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable.CreateAgentFactory(AgentInfo agentInfo)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable..ctor(IEnumerable agents)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.RuntimeSettings..ctor(MExConfiguration config, String agentGroup)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExRuntime.Initialize(String configFile, String agentGroup, Boolean isBridgeHead, String installPath)
at Microsoft.Exchange.Transport.Extensibility.AgentComponent.Load()

Hope you can help!

 

Sorry, forgot to add, it's Server 2008 R2 Standard.

 

Could you confirm or deny that you had the latest build of EMSX 4.2.10016 installed?

Try uninstalling the transport via the Exchange shell by entering "Uninstall-TransportAgent" or by removing it manually from agents.config (this problem was fixed in the last build mentioned above).

 

I'm not sure which version it was.

So, just to clarify, I have to remove the transport agent from exchange, and then re-setup? Are there any big hazards to this?