"Wanna" ransomware outbreak. Please see this Sophos article sophos.com/kb/126733 for advice on how to protect your organization. Immediate action recommended.
After applying Exchange 2013 Service Pack 1 to an Exchange server running PureMessage for Microsoft Exchange, the below errors are seen.
When attempting to start the Microsoft Exchange Frontend Transport service in the Services MMC:
Windows could not start the Microsoft Exchange Frontend Transport service on Local Computer. Error 1067 The process terminated unexpectedly.
Application Event Log:
Event ID: 1052 Error: Failed to create agent factory for the agent "PmE15Protocol'
Event ID: 16023 Error: Microsoft Exchange couldn't start transport agents. The Microsoft Exchange Transport service will be stopped.
System Event Log:
Event ID: 7031 Error: The Microsoft Exchange Frontend Transport service terminated unexpectedly.
First seen in PureMessage for Microsoft Exchange 4.0.1PureMessage for Microsoft Exchange 4.0
This has been identified as a Microsoft issue introduced in Exchange 2013 Service Pack 1. This issue has also impacted a number of other vendors.
Microsoft have now released a PowerShell script to resolve this issue.
Note: The Microsoft article contains additional steps to 'Uninstall third-party agents', this is not required for PureMessage for Microsoft Exchange.
If you have previously disabled the PureMessage Transport agents to workaround this issue then you will need to enable them after running the Microsoft PowerShell script.
Enable-TransportAgent PmE15Protocol -TransportService FrontEnd
Enable-TransportAgent PmE15Protocol -TransportService Hub
Enable-TransportAgent PmE15Transport -TransportService Hub
Related Information Installation fails on Exchange servers which have been updated to Exchange 2013 Service Pack 1
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. If you need technical support please post a question to our community. Alternatively for licensed products open a support ticket.