ODBC Server Installation and Management Manual

Managing the NonStop ODBC Server
HP NonStop ODBC Server Installation and Management Manual—429395-002
4-25
Using Error and Event Messages for System
Diagnosis
Using Error and Event Messages for System
Diagnosis
This subsection summarizes error and event messages emitted by the SCS process
and by NonStop ODBC Servers. You can use these messages to diagnose
configuration errors, internal errors, system errors, and communication errors.
EMS Event Messages From the SCS Process
The following is a list of possible Event Management Service messages from the SCS
process. Detailed descriptions of EMS event messages that can be generated by SCS,
complete with exact display format and all tokens involved, are given in the NonStop
ODBC Server Messages Manual.
The SMB minor error describes the specific error condition. The common minor error
codes that might appear in an SMB-ERROR event follow:
The following SMB minor errors indicate serious problems.
10
9
ERROR_BROKEN_PIPE
The SCS process experienced an I/O error communicating with the gateway
process.
23
1
ERROR_PIPE_BUSY
The SCS process was unable to service a Named Pipes connection request
from a client program. This error occurs when the connection attempts exceed
the number of gateway processes configured for the SCS process. You have
under-configured your SCS process.
23
3
ERROR_PIPE_NOT_CONNECTED
This error indicates that a gateway process, previously connected to a client,
has closed the connection unilaterally. In this case, the gateway formally
disconnected from the SCS process. This error signals the client that the
gateway process is no longer available. Check the EMS log to determine why
the NonStop ODBC Server program terminated.
6 ERROR_INVALID_HANDLE
Client driver provided a bad pipe handle number.
11 ERROR_BAD_FORMAT
A PC client incorrectly issued a DosCallNmPipe request.