3.6.0 Matrix Server Event Notification Guide (5697-7150, December 2007)

Table Of Contents

Chapter 3: Event Messages 39

17031 <server> has lost a significant portion of its SAN access, including access to

all the membership partitions, possibly due to a SAN hardware failure. As a

result, this server is ineligible to become the matrix ADM.

Action. The specified server is unable to write to any of the membership

partitions. Ensure that the server can access the membership partitions and

also has write access to them. Also check for hardware problems that can

limit access to the partitions. If the disks containing the membership

partitions have failed, you will need to recreate the partitions. (See

“Membership Partitions” in the PolyServe Matrix Server Administration Guide

for more information.)

17032 <server> losing SAN access resolved.

Action. None. Alert 17031 is resolved.

17033 One or more volumes have the old device format and should be manually

upgraded to enable volume disaster recovery. See the Matrix Server

Upgrade Guide for further information.

Action. You will not be able to use the volume disaster recovery feature

until the unstriped volume is recreated. Be sure to back up the filesystem on

the volume before recreating it. See the Matrix Server Upgrade Guide for a

procedure to recreate the volume.

17034 Volume format issue resolved.

Action. None. Alert 13919 is resolved.

40500 Cannot access the volume for path: <path>.

Action. The Virtual SQL instance cannot access the specified location on the

shared storage. Check SAN access for all nodes included in the Virtual SQL

Server associated with the Virtual SQL instance. Also check the matrix log

and the Service event log for a possible cause of the failure.

40501 Inaccessible volume failure resolved.

Action. None. Alert 40500 is resolved.

40502 Failure to start NT service <service>.

Action. Check the matrix log and the Service event log for a possible cause

of the failure. If the shared storage is mounted, check the ERRORLOG for

the instance on the SAN. If you are unable to resolve this problem, contact

HP Support.

40503 NT service start failure resolved.

Action. None. Alert 40502 is resolved.

ID Message and Corrective Action