Dear All,
I was looking at Endpoint protection plus for our Windows Server SBS 2008 R2 and 4 x Windows 7 Clients.
I downloaded and only installed Endpoint on the server where it crashed the server by hanging on the SOA interface after a ‘successful’ installation.
I had to power off the server and it wouldn’t restart, hanging at ‘Applying Settings’ at boot up. I rebooted again in Safe Mode and uninstalled Endpoint and Small Office Admin. This has allowed the server to start but not our POP3 Connector for Exchange 2007 to retrieve emails from our host.
We cannot start the POP3 Connector manually due to its dependent MSExchangeTransport service not being able to start due to the following:
Microsoft Exchange couldn’t start transport agents. The Microsoft Exchange Transport service will be stopped. Exception details: Failed to create type ‘Avast.ExchangeAntispam.AntispamAgentFactory’ from assembly ‘C:\Program Files\AVAST Software\Avast Business\AsEx.dll’ due to error ‘Invalid agent assembly path.’. : Microsoft.Exchange.Data.ExchangeConfigurationException: Failed to create type ‘Avast.ExchangeAntispam.AntispamAgentFactory’ from assembly ‘C:\Program Files\AVAST Software\Avast Business\AsEx.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)
at Microsoft.Exchange.Transport.Categorizer.MExEvents.Initialize(String configFilePath)
at Microsoft.Exchange.Transport.Components.CategorizerMExRuntimeLoader.Load()
The path doesn’t exist as the program has been uninstalled but something is being left behind by endpoint to execute…
Could someone please assist me in getting rid of this error so we can at least retrieve emails that we haven’t had access to, all day.
Kind regards,
Paul