30.10.2014 Views

Administration Guide - Avaya Support

Administration Guide - Avaya Support

Administration Guide - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

MAS Alarms<br />

MAS Alarm - VS SPOOL 1<br />

Level<br />

Minor.<br />

System Descriptor<br />

Message spool directory access failed.<br />

Description<br />

This alarm indicates that the system is unable to access the message spool directory.<br />

Repair Procedure<br />

There is no repair procedure for this alarm. Once the alarm has been raised, if the<br />

system is then able to access the message spool directory, then the problem is<br />

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

When this alarm is raised, you can locate and view more detailed information about the<br />

failure by checking the Event Viewer Application log:<br />

Although there is no repair procedure for this alarm, you can identify the registry key<br />

that caused the problem by checking the Event Viewer Application log:<br />

1. Click the Start > Programs > Administrative Tools > Services menu<br />

command to start the Services monitor.<br />

2. In the Tree pane, select Event Viewer (Local), expanding the tree if<br />

necessary.<br />

3. Double-click Application.<br />

The system displays the Application log.<br />

4. Locate the most recent entry for a 1527 or (unintentional) 1014 event.<br />

Note: A manual service shutdown currently results in a 1014 event being<br />

generated.<br />

If the system does not resolve the alarm automatically within a period of a few minutes,<br />

contact your <strong>Avaya</strong> technical support representative for assistance.<br />

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

A–84 MAS <strong>Administration</strong> <strong>Guide</strong><br />

February 2007

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

Saved successfully!

Ooh no, something went wrong!