• Article

How Archiving Failures Are Handled

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

If a message cannot be archived, one of the following will happen:

  • If the message fails to reach the destination queue for any reason (including permissions issues or network issues) the Office Communications Server Front End service will do one of the following:

    • If the archiving and CDR agent is running in critical mode, the Front End service will write an event to the event log and then shut down the service. The time that it takes for the service to shut down varies depending on the situation, but the maximum is 45 minutes. For instance, in the case of a permissions issue, the service will shut down immediately. For network issues, it can take an average of 30 minutes. You can configure these timeout periods in Windows Management Instrumentation (WMI) as described in the following section.

    • If the archiving and CDR agent is not running in critical mode, write an event to the event log.

  • If the message reached the destination queue but the Archiving and CDR Server cannot pick it up for 45 minutes, the Front End service may do one of the following:

    • Shut down after 45 minutes (WMI configurable) if the archiving is running in critical mode.

    • Write an event to the event log if the archiving and CDR agent is not running in critical mode.

  • If the message is picked up by the Archiving and CDR Service component but the Archiving and CDR Server fails to write to the database, then the message is written in a log file (the stored procedure name that was called and all the parameters), and an error is written to the event log if the message is critical. A message is critical if the archiving and CDR agent that sent the message is running in critical mode and the message itself contains the body of an instant message; otherwise, a warning is written to the event log. If the attempt to write to the log file also fails (for example, because the disk is full) and the message is critical, Archiving and CDR Server will shut itself down, and the message that the Archiving and CDR Service component was processing is returned to Message Queuing as if it had never been read. At this point, the Office Communications Server will do one of the following:

    • Shut down after 45 minutes (WMI configurable) if the archiving and CDR agent is running in critical mode.

    • Write an event to the event log if the archiving and CDR agent is not running in critical mode.

  • If the SQL database is unavailable or is stopped, the Archiving and CDR Server will continuously try to connect to the SQL database; however, if the Archiving and CDR Server is stopped before SQL becomes available, all of the messages will be returned to Message Queuing. At this point, the Office Communications Server will do one of the following:

    • Shut down after 45 minutes (WMI configurable) if the archiving and CDR agent is running in critical mode.

    • Write an event to the event log if the archiving and CDR agent is not running in critical mode.

      Note

      If SQL Server is not running and you want to stop the Archiving and CDR service immediately, use Windows Task Manager to end the RTCArch.exe process. Any messages that are sent while the database is down will be returned to the queue and will be archived when the database is running again.