Summary
These messages are from the data manager, but are specifically related to nodes and node groups.
Details
These messages are from the data manager, but are specifically related to nodes and node groups.
| Message Number | Name | Explanation | Action |
|---|---|---|---|
| 3146 | ERR_NODE_SERVER_TARGET_EXIST | Contact Catalogic Software Technical Support. | |
| 3147 | ERR_NODE_INVALID_SERVER_TARGET | Contact Catalogic Software Technical Support. | |
| 3148 | ERR_NODE_DIFF_CLUSTER | Contact Catalogic Software Technical Support. | |
| 3149 | ERR_NODE_INVALID_EXTINFO | Contact Catalogic Software Technical Support. | |
| 3150 | ERR_NODE_NODETYPE_UPDATE | The attempt to change this nodetype failed. To update a node of type Novell or Windows, you must delete the previous definition and replace it with a new one. | |
| 3151 | ERR_NODE_UNKNOWN_TOKEN | An unrecognized command for manipulating nodes was issued. | |
| 3152 | ERR_NODE_WRONG_TOKEN | The node message processor was expecting one message, but received another. | |
| 3153 | ERR_NODE_DOESNOT_EXIST | The specified node does not exist. | The most common cause of this error is a database inconsistency in the controller node of a device. For example, you may change the name of a node that actually controls a Tape Library or tape drive in Enterprise/Group/Node without reassigning the controller node in device control. The solution is to check all of the controller nodes for validity in your configuration. This message may also occur if your old backup definition references a node that no longer exists. |
| 3154 | ERR_NODE_ALREADY_EXIST | The node is already in the database. | |
| 3155 | ERR_NODE_EXIST_IN_MEMBER_LIST | The node does not exist in the member list. | |
| 3156 | ERR_NODE_INVALID_RECORD | An invalid record pointer was passed to the node message processor. | |
| 3157 | ERR_NODE_INSERT_RECORD | A node message processor record insertion operation failed. | |
| 3158 | ERR_NODE_FLUSH_HEADER | An attempt to flush the header of a node record failed. | |
| 3159 | ERR_NODE_FLUSH_FILE | A node message processor file flush operation failed. | |
| 3160 | ERR_NODE_INVALID_NAME | The node name is invalid. | Specify a name that is 48 or fewer characters, without spaces. |
| 3161 | ERR_NODE_INVALID_NODETYPE | The type specified for this node is unrecognized. | |
| 3162 | ERR_NODE_INVALID_NODEADDR | The IP or IPX address for this node is invalid. | |
| 3163 | ERR_NODE_INVALID_OPSYS | The operating system information is in the wrong format. | |
| 3164 | ERR_NODE_INVALID_SERVERNAME | The name of the Netware server for this node is invalid. | |
| 3165 | ERR_NODE_INVALID_TSANAME | The name of the TSA is not in the correct format. | |
| 3166 | ERR_NODE_INVALID_TARGETNAME | The name of the target is not in the correct format. | |
| 3167 | ERR_NODE_INVALID_USERNAME | The user name is in the wrong format. | |
| 3168 | ERR_NODE_INVALID_PASSWORD | The login password is in the wrong format. | If this is a NDMP node, the following special characters are not supported. ? ; * and the character. |
| 3169 | ERR_NODE_INVALID_DPOOL | The device pool is invalid for the node specified. | |
| 3170 | ERR_NODE_INVALID_TPOOL | The media pool is invalid for the node specified. | |
| 3171 | ERR_NODE_INVALID_SERVER_TSA_TARGET | The combination of server, TSA, and target is not valid. | |
| 3172 | ERR_NODE_SERVER_TSA_TARGET_EXIST | The specified combination of server, TSA, and target does not exist. | |
| 3173 | ERR_NODE_BOTH_NODEADDR_SERVER_EXIST | Contact Catalogic Software Technical Support. | |
| 3174 | ERR_NODE_BOTH_NODEADDR_SERVER_MISSING | Contact Catalogic Software Technical Support. | |
| 3175 | ERR_NODE_SERVER_DOESNOT_EXIST | The Netware server does not exist. | |
| 3176 | ERR_NODE_SERVER_ALREADY_EXIST | Contact Catalogic Software Technical Support. | |
| 3177 | ERR_NODE_NODEADDR_DOESNOT_EXIST | Contact Catalogic Software Technical Support. | |
| 3178 | ERR_NODE_NODEADDR_ALREADY_EXIST | A duplicate IP address was specified. | |
| 3179 | ERR_NODE_NODEADDR_SERVER_SPECIFIED | Contact Catalogic Software Technical Support. | |
| 3180 | ERR_NODE_REACH_MAX_NODE_LIMIT | The maximum node limit was reached. | |
| 3181 | ERR_GROUP_UNKNOWN_TOKEN | An unrecognized command for manipulating node groups was issued. | |
| 3182 | ERR_GROUP_WRONG_TOKEN | The node group message processor was expecting one message, but received another. | |
| 3183 | ERR_GROUP_DOESNOT_EXIST | The specified node group does not exist. | |
| 3184 | ERR_GROUP_ALREADY_EXIST | A node group by this name is already in the database. | |
| 3185 | ERR_GROUP_EXIST_IN_MEMBER_LIST | This node group does not exist the member list. | |
| 3186 | ERR_GROUP_IS_EMPTY | The specified node group is empty. | |
| 3187 | ERR_GROUP_ISNOT_EMPTY | The specified node group cannot be deleted until it is empty. | |
| 3188 | ERR_GROUP_INVALID_RECORD | An invalid record pointer was passed to the node group message processor. | |
| 3189 | ERR_GROUP_INSERT_RECORD | A node group message processor record insertion failed. | |
| 3190 | ERR_GROUP_FLUSH_HEADER | An attempt to flush the header of a node group record failed. | |
| 3191 | ERR_GROUP_FLUSH_FILE | A node group message processor file flush failed. | |
| 3192 | ERR_GROUP_INVALID_NAME | The node group name is invalid. | Specify a name that is 48 or fewer characters, without spaces. |
| 3193 | ERR_GROUP_ALREADY_ASSIGNED | The node group has already been assigned to this administrator. | |
| 3194 | ERR_GROUP_ISNOT_ASSIGNED | The node group is not assigned to an administrator. | |
| 3195 | ERR_GROUP_EXIST_IN_RESOURCE_LIST | The node group is not in the resource list. . | |
| 3196 | ERR_LOGICAL_NODES_ALREADY_EXIST | The logical node already exists. | |
| 3197 | ERR_IPADDRESS_METHOD_ALREADY_USED | The IP address method for scanning the node is already used; try scanning by hostname instead. | |
| 3198 | ERR_HOSTNAME_METHOD_ALREADY_USED | The hostname address method for scanning the node is already used; try scanning byIP address instead. | |
| 3199 | ERR_BOTH_METHODS_ALREADY_USED | Both the hostname and IP address node scan method are already in use. |