RPC HELP Debugging Broker Error Messages

From VistApedia
Jump to: navigation, search

Broker Error Messages

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

  • Error/Message: Insufficient Heap
  • Name: XWB_NO_HEAP
  • Number: 20001
  • Description: 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.
  • Error/Message: M Error - Use ^XTER
  • Name: XWB_M_REJECT
  • Number: 20002
  • Description: The VistA M Server side of the application errored out. The Kernel error trap has recorded the error.
  • Resolution: Examine the Kernel error trap (via DO ^XTER on server) for more information and specific corrective actions.
  • Error/Message: Signon was not completed
  • Name: XWB_BadSignOn
  • Number: 20004
  • Description: 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 VistA Sign-on window.
  • Error/Message: BrokerConnections list could not be created
  • Name: XWB_BldConnectList
  • Number: 20005
  • Description: 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.
  • Error/Message: RpcVersion cannot be empty
  • Name: XWB_NullRpcVer
  • Number: 20006
  • Description: 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.
  • Error/Message: Remote procedure not registered to application
  • Name: XWB_RpcNotReg
  • Number: 20201
  • Description: This error indicates the application attempted to execute an RPC that 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.

NOTE: For common Winsock error messages, please refer to the RPC Broker "FAQ: Common Winsock API Error/Status Messages" on the Web at: http://vista.med.va.gov/broker/docs/winsock.asp.

Retrieved from "https://vistapedia.com/index.php?title=RPC_HELP_Debugging_Broker_Error_Messages&oldid=16620"