BSPXCOM

SPX Communications Module Messages

The following messages are specific to the Communications Manager on NetWare.

BSPXCOM-2: The server has insufficient memory to execute BSPXCOM.NLM

An error occurred during a memory allocation operation. Free memory by unloading NLMs or reconfiguring NLMs to use less memory. Retry the operation. If the error persists, contact Technical Support at Pervasive Software.

BSPXCOM-3: An internal error has occurred. BSPXCOM detected a semaphore allocation failure

An internal error occurred during a semaphore allocation operation. Retry the operation. If the error persists, contact Technical Support at Pervasive Software.

BSPXCOM-4: The Service Request Block (SRB) function code nn contains invalid data. Check for an incompatible version of the file BSPXCOM.NLM

Ensure that BSPXCOM's version is compatible with the version number of the workstation's MKDE Requester.

BSPXCOM-6: Another NLM is using the socket number reserved for BSPXCOM.NLM

To solve this condition, unload all other NLMs. Load BTRIEVE.NLM and NWBSRVCM.NLM, and then reload the other NLMs. This process reveals the NLM that is using BSPXCOM.NLM's socket number.

BSPXCOM-7: An SPX receive I/O error (nn) has occurred. The connection has been lost

An error occurred during an SPX-level receive operation. Refer to your operating system documentation for the definition of the error number. Retry the operation. If the error persists, contact Technical Support at Pervasive Software.

BSPXCOM-8: An SPX send I/O error (nn) has occurred. The connection has been lost

An error occurred during an SPX-level send operation. Refer to your operating system documentation for the definition of the error number. Retry the operation. If the error persists, contact Technical Support at Pervasive Software.

BSPXCOM-10: Bad connection ID detected on receive. The SPX connection was lost after the initial request began

If this message appears frequently, increase your requester's SPX Timeout parameter, which is controlled with the configuration properties. Also, check for NLMs that are monopolizing the CPU time.

BSPXCOM-11: Bad connection ID detected on send. The SPX connection was lost after the initial request began

If this message appears frequently, increase your requester's SPX Timeout parameter, which is controlled with the configuration properties. Also, check for NLMs that are monopolizing the CPU time.

BSPXCOM-12: An error (nn) was detected while trying to establish an SPX session requested by a remote workstation

An error occurred during an SPX-level session establishment operation. Refer to your operating system documentation for the definition of the error number value. Retry the operation. If the error persists, contact Technical Support at Pervasive Software.

BSPXCOM-13: The session was rejected because the session limit was reached. Increase the value specified for the Number of Remote Sessions option

Obsolete in Pervasive.SQL 8 and later versions.

Increase the value specified for the Number of Remote Sessions in the configuration properties.

BSPXCOM-14: The request for statistics from the Monitor utility was not recognized. Check for an incompatible version of the utility or BSPXCOM.NLM

Ensure that your BSPXCOM.NLM version is compatible with the version number of the Monitor utility.

BSPXCOM-15: An internal error has occurred. BSPXCOM did not recognize the GET_EIM_STATS function

Ensure that the version of BSPXCOM.NLM is compatible with the version number of the Monitor utility.

BSPXCOM-18: A thread initialization error has occurred

An error occurred during BSPXCOM.NLM thread initialization. Refer to the Pervasive Software Event Log (PVSW.LOG) for error messages preceding this one. Correct the problem and retry the operation.

BSPXCOM-19: A BeginThread() error (nn) has occurred

An error occurred during a BeginThread operation. Refer to your operating system documentation for the definition of the error number value. Retry the operation. If the error persists, contact Technical Support at Pervasive Software.