30.10.2014 Views

Administration Guide - Avaya Support

Administration Guide - Avaya Support

Administration Guide - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

MAS Alarms<br />

MAS Alarm - VS EXCEPTION 3<br />

Level<br />

Major.<br />

System Descriptor<br />

An exception was caught and handled. The caller/subscriber was disconnected. An MP<br />

was run.<br />

Description<br />

This alarm indicates that the MM Messaging Application Server service has caught<br />

and handled an exception. The system disconnected the caller or subscriber. The<br />

system also ran a maintenance procedure (MP) to stop and restart the MM Messaging<br />

Application Server service.<br />

This alarm is generated by a Windows NT warning event 1772 or 1773. It generally<br />

indicates a software bug.<br />

Repair Procedure<br />

If the MM Messaging Application Server service restarts successfully, then the<br />

system considers the alarm resolved and generates a resolved-alarm event.<br />

You should contact your <strong>Avaya</strong> technical support representative and let them know<br />

about it, even if the alarm is resolved.<br />

<strong>Avaya</strong> Modular Messaging Release 3.1 with the <strong>Avaya</strong> MSS<br />

February 2007 MAS <strong>Administration</strong> <strong>Guide</strong><br />

A–57

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!