RDMI Error Messages
The following new RDMI error messages are being introduced:
Container message used to display errors from the component middleware layer.
This message is returned if RDMI could not load and/or initialize the DLL which deals with the communication with the selected middleware. This can happen if the selected middleware is not installed, or if the initialization of that middleware fails. Users should check the middleware installation.
Generic message returned if USoft is not able to call the specified method. The creation of the component was successful, but the calling of the method was not.
If the Show Component Errors deployment configuration parameter in the Authorizer is set to True, more specific messages returned by the component may also be displayed. If the property is set to False, users can check the message history for details.
Generic message returned if USoft is not able to create the specified component.
If the Show Component Errors application property is set to True, more specific messages returned by the component may also be displayed. If the property is set to False, users can check the message history for details.
The error can have several causes: the component may not exist, the physical name as specified in the definer may not be correct, or perhaps a remote machine where the component resides is not switched on.
The specified method or protocol does not exist for the specified component. Users should check definitions of their RDMI components in the Definer.
The number of runtime input parameters does not match the number of input parameters as defined in the repository (i.e., in the Definer) for the specific method or protocol. If an association with the query protocol was defined, users should check parameters for the EXE method of the protocol association.