Broker Error Messages

The following list of errors/messages are Broker-specific and are not Winsock related:

Error/Message Name Number Description
Insufficient Heap XWB_NO_HEAP 20001 This is a general error condition indicating insufficient memory. It can occur when an application allocates memory for a variable. This error can occur for some of the following reasons:
  • Too many open applications

  • Low physical memory

  • Small virtual memory swap file (if dynamic, maybe low disk space)

  • User selecting too many records

Resolution: Common solutions to this error include the following:

  • Close some or all other applications

  • Install more memory

  • Increase the swap file size or, if dynamic, leave more free space on disk

  • Try working with smaller data sets

  • Reboot the workstation
M Error - Use ^XTER XWB_M_REJECT 20002 The server side of the application errored out. The error has been recorded by the Kernel error trap.

Resolution: Examine the Kernel error trap for more information and specific corrective actions.
Signon was not completed XWB_BadSignOn 20004 This error indicates the user did not successfully signon.

Resolution: Either the Access and Verify codes were incorrect or the user pressed the Cancel button on the signon window.
BrokerConnections list could not be created XWB_BldConnectList 20005 This error is a specific symptom of a low memory condition.

Resolution: Please refer to the "Insufficient Heap" error message for a more detailed explanation and corrective measures.
RpcVersion cannot be empty XWB_NullRpcVer 20006 This error occurs when an RPC does not have an associated version number. Each RPC must have a version number.

Resolution: Contact the developers responsible for the application software to take corrective action.
Remote procedure not registered to application XWB_RpcNotReg 20201 This error indicates the application attempted to execute an RPC which was not entered into the RPC multiple field in the REMOTE PROCEDURE file (#8994) for this application.

Resolution: The developers responsible for the application should be contacted.

As a "last resort" corrective measure, you may try to re-index the cross-reference on the RPC field (#.01) in the REMOTE PROCEDURE file (#8994) with the RPC field (#320) of the OPTION file (#19). Ideally, this should only be attempted during off or low system usage.