Using the Node Management Services (NMS) Utilities (32022-90053)

292 AppendixA
NMS Error Messages
ND Error Messages
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Domain report in path report list too short (< 6 bytes).
(NDIERR 252)
NDIERR 252 CAUSE: This is an internal error.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Version of domain report in path report list <> 0.
(NDIERR 253)
NDIERR 253 CAUSE: The version number (1st octet) of a domain indicates an
unsupported version.
ACTION: Possible version mismatch; reinstall the product. If this fails,
see “Submitting an SR” at the beginning of this appendix.
MESSAGE: Domain number of domain report in path report list 1.
(NDIERR 254)
NDIERR 254 CAUSE: This is an internal error.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Cannot read a node name back reference record —
corrupt file likely. (NDIERR 260)
NDIERR 260 CAUSE: Possible corrupt network directory file.
ACTION: Restore the data and key files from a back-up tape. If this
fails, see “Submitting an SR” at the beginning of this appendix.
MESSAGE: A required node name record is not in dir — corrupt file
likely. (NDIERR 261)
NDIERR 261 CAUSE: Possible corrupt network directory file.
ACTION: Restore the data and key files from a back-up tape. If this
fails, see “Submitting an SR” at the beginning of this appendix.
MESSAGE: FUPDATE failed — internal error. (NDIERR 262)
NDIERR 262 CAUSE: This is an internal error.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: FGETINFO failed — internal error. (NDIERR 270)
NDIERR 270 CAUSE: This is an internal error.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: FFINDBYKEY failed — corrupt file likely. (NDIERR 271)
NDIERR 271 CAUSE: Possible corrupt network directory file.
ACTION: Restore the data and key files from a back-up tape. If this
fails, see “Submitting an SR” at the beginning of this appendix.