The Office Communications Server Front-End service terminated with service-specific error 2147975170 (0x80078002)

Sometimes you get Front End Services to stop unexpectedly and in the event error you receive the message:  “The Office Communications Server Front-End service terminated with service-specific error 2147975170 (0x80078002)”.

This is a rare event, but it might occur in scenarios when the Archiving Setting “Shutdown if archiving fails” is enabled or something happens to Archiving Server, such as the service stopping or the server going offline (power failure, hardware failure or another reason).

archiving01

Keep in mind that disabling options should be our last resort, I mean, if this option is enabled there must be a reason for that. The first step would be trying to figure out what problem occurred in Archiving Server.

In the Event Viewer look for this:

The Office Communications Server Front-End service terminated with service-specific error 2147975170 (0x80078002).
Event ID: 7024
OCS2007R2-FE
Event ID: 30511

Office Communications Server Archiving Agent or Archiving Service is unable to read/write to MSMQ queue in a timely fashion.

Acknowledgement class: 32770.
Cause: This could happen if the Archiving Agent receives a negative acknowledgement from the service.
Resolution:
Check Office Communications Server Archiving Agent permissions, Archiving Service permissions and restart services, if required.
Event ID: 12304
The component Live Communications IM Archiving Agent (application: Default) reported a critical error: code 80078002 (). The service has to stop.
Evenrd ID: 61013
The process IMMcuSvc(5080) failed to send health notifications to the MCU factory at https://*******************/LiveServer/MCUFactory/.
Failure occurrences: 5, since 6/27/2013 9:55:46 AM.

This happens when “Shutdown if archiving fails” is enabled. To solve this we have to fix the Archiving Server or disable the options.
In Office Communicator Server 2007 R2, Microsoft has split Monitoring Settings and Archiving Settings in Pool View and we have now this:

archiving02

If Archiving fails we can get the following errors:

Event Type: Error
Event Source: OCS Server
Event Category: (1000)
Event ID: 12304
Date: 29/7/2013
Time: 17:31:27
User: N/A
Computer: OCS2007R2-FE
Description:
The component Live Communications IM Archiving Agent (application: Default) reported a critical error: code 8007045A (Archiving and CDR Agent failed to archive a message due to an internal error). The service has to stop.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Another example is:

Event Type: Error
Event Source: OCS Server
Event Category: (1000)
Event ID: 12304
Date: 29/7/2013
Time: 20:48:31
User: N/A
Computer: OCS2007R2-FE
Description:
The component Live Communications IM Archiving Agent (application: Default) reported a critical error: code 0 (a negative acknowledgement from MSMQ). The service has to stop.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Or for instance:

Event Type: Error
Event Source: OCS Archiving Agent
Event Category: (1011)
Event ID: 30511
Date: 29/7/2013
Time: 20:48:31
User: N/A
Computer: OCS2007R2-FE
Description:
Office Communications Server Archiving Agent or Archiving Service is unable to read/write to MSMQ queue in a timely fashion.

Queue: Archiving Server acknowledgement class: 32770. Time to reach queue has expired.
Cause: This could happen if the Archiving Agent receives a negative acknowledgement from the service. One or more messages have timed out and have been dropped.
Resolution:
Check Office Communications Server Archiving Agent permissions, Archiving Service permissions and restart services, if required.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.