After installing Service Pack 1 for Exchange 2013, the following error may occur:
451 4.7.0 Temporary server error. Please try again later. PRX5
The transport service crashes as soon as a mail is being delivered. This problem is caused by incorrect XML data:
http://support.microsoft.com/kb/2938053/en-us
Microsoft provides a Fix-It tool for this, which can be found under the link above. This event can be found in the Exchange Server event log (as information):
Source: MSExchangeTransport
ID: 7001
The service is terminated. Reason: Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Loading of component 'SmtpReceiveAgents' failed. -> Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Error loading the agent component. -> Microsoft.Exchange.Data.ExchangeConfigurationException: Error creating type 'XmonAgent.XmonSmtpAgentFactory' from assembly 'C:\Program Files\ESET\ESET Mail Security\XmonAgent.dll' due to error 'type not found'.
for Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable.CreateAgentFactory(AgentInfo agentInfo)
for Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable..ctor(IEnumerable agents, FactoryInitializer factoryInitializer)
for Microsoft.Exchange.Data.Transport.Internal.MExRuntime.RuntimeSettings..ctor(MExConfiguration config, String agentGroup, FactoryInitializer factoryInitializer)
for Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExRuntime.Initialize(String configFile, String agentGroup, ProcessTransportRole processTransportRole, String installPath, FactoryInitializer factoryInitializer)
for Microsoft.Exchange.Transport.Extensibility.AgentComponent.Load()
- End of internal exception stack monitoring -
for Microsoft.Exchange.Transport.Extensibility.AgentComponent.Load()
for Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
for Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount)
for Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
- End of internal exception stack monitoring -
for Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
for Microsoft.Exchange.Transport.Components.Activate()
In my case, it was a virus scanner (ESET) that installed the corresponding transport agents:
If the Fix-It from Microsft cannot solve the problem, the transport agents can be temporarily deactivated:
The transport service should then be able to be started again and remain started.
