13.23 BCC Error Codes

The following table lists the different BCC error codes by number and gives a brief description for each error code.

Table 13-3 BCC Error Codes and Messages

Error Code Number

Message

1000

Unknown error.

1001

Received XML is invalid.

1002

The object pointers in eDirectory for the given cluster resource are invalid.

1003

The referenced object is not a valid NCS/BCC object.

1004

The referenced cluster resource is in an invalid state.

1005

The specified resource or cluster is not enabled for Business Continuity.

1006

An invalid parameter was passed to the BCC API.

1007

Attempt to allocate memory failed.

1008

Attempt to communicate with the BCC VFS system failed.

1009

The size of the specified buffer is not large enough.

1010

Error performing a DSML read.

1011

Error performing a DSML modify.

1012

Operation not supported.

1013

Error obtaining lock on synchronization object.

1014

Invalid credentials.

1015

Error returned from the NICI API.

1016

Cannot find peer cluster data.

1017

Invalid BCC API version.

1018

Could not find a pool for the specified cluster resource.

1019

Error managing the SAN via the Novell SAN Management Interface.

1020

CIM Client error.

1021

Error creating a system resource (mutex, semaphore, etc.).

1022

File IO error.

1023

No data.

1024

Not a member of the cluster.

1025

Invalid token in the script.

1026

Invalid or unknown cluster.

1027

The NSMI script is too long. It must be less than 64 KB.

1028

The cluster-enabled pool resource does not contain a volume.

1029

An operation has timed out.

1030

The specified resource is already busy.

The error code numbers are recorded in a log file that you can use to view status changes for BCC.

The path to the log file on Linux is /var/log/messages. You can search for BCCD to view BCC related messages and entries in the log file.