If you are not in Critical Mode,
an error is written to the Event Log but the Front-End Service continues to function.
Because MSMQ is used as the underlying transport mechanism for archiving, failure
may not happen instantly, as messages can be queued on the front-end server if the Archiving
and CDR Server is not accessible. This helps to ensure that temporary network outages or
a reboot of the Archiving and CDR Server does not result in an archiving failure.
If the archiving agent is unable to submit messages to the MSMQ queue on the front-end
server, a failure will be instant. These failures are usually due to a confi guration issue or to
the Message Queuing Service not running.
If messages cannot be sent to the Archiving and CDR Server, the messages will sit in
the message queue for 30 minutes until a failure is issued. If messages are sent to the Archiving
and CDR Server but the archiving service is not running or is unable to process the messages
for any reason, after 45 minutes a failure will occur; you can confi gure both of these timeout
periods through Windows Management Instrumentation (WMI).
If the archiving service is unable to write messages to the database for any reason other
than the SQL server being unavailable, the messages are written to a log fi le which is then
processed when it becomes possible to write to the database again; if it is not possible to write
to the log fi le, the messages are returned to the MSMQ queue to be reprocessed when
possible.
Pages:
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260