TDP3524 "npname" "CONNECT" FAILED -- SERVER NP IS NOT STARTED - Teradata Tools and Utilities

Teradata Director Program (TDP Prefix) Messages

Product
Teradata Tools and Utilities
Release Number
15.xx,16.xx
Language
English (United States)
Last Update
2018-10-23
dita:id
B035-1096-TDP
lifecycle
latest
Product Category
Teradata® Tools and Utilities

TDP3524 "npname" "CONNECT" FAILED -- SERVER NP IS NOT STARTED

Explanation:

When attempting to establish communication with the Teradata Database using the displayed NP, Connect processing was rejected by the encapsulation protocol because the SERVER NP was not operational (Connect_done result 1).

Generated By:

TDP.

Notes:

If START processing has not yet completed, the START will fail, otherwise, the NP enters the PERM ERR state and will not be used further. Any requests that are active on the NP will be failed and the associated sessions will be logged off. Sessions without active requests or with requests active on other NPs are unaffected.

Remedy:

Subsequent use of the NP may be attempted by first issuing the TDP STOP NP command (necessary only if the NP is in the PERM ERR state), then the TDP START NP command. Contact Customer Support personnel and provid the text of this message.