Normally, the exception conditions reported via the DSI minor codes indicate an error on the server side. The user DSI code must be fixed in order to correct these types of errors.
BAD_INV_ORDER system exception. In a normal DSI scenario, the set_result( ) operation of the ServerRequest pseudo object is called a single time after the arguments( ) operation. This occurs if set_result( ) is called before arguments( ) has been called. BAD_INV_ORDER system exception. Similar to the MINOR_SET_RESULT_BEFORE_ARGS minor code described above, this occurs if set_result( ) is called after a previous call to set_result( ). BAD_INV_ORDER system exception. In a normal DSI scenario, the set_result( ) operation of the ServerRequest pseudo object is called once after the arguments( ) operation. However, if an exception was raised by a call to set_exception( ), then set_result( ) may not be called. This minor code is generated if set_result( ) is called after set_exception( ) has been called. BAD_INV_ORDER system exception. In a normal DSI scenario, the ctx( ) operation of the ServerRequest pseudo object, if called, must be called after the arguments( ) operation. This minor code is generated if ctx( ) is called after arguments( ). BAD_INV_ORDER system exception. In a normal DSI scenario, the ctx( ) operation of the ServerRequest pseudo object, if called, must be called a single time after the arguments( ) operation. This minor code will be generated if ctx( ) is called a second time after arguments( ). BAD_INV_ORDER system exception. In a normal DSI scenario, the ctx( ) operation of the ServerRequest pseudo object, if called, must be called after the arguments( ) operation is called and before the call is made to set_result( ). This minor code is generated if ctx( ) is called after set_result( ) is called. BAD_INV_ORDER system exception. In a normal DSI scenario, the ctx( ) operation of the ServerRequest pseudo object, if called, must be called after the arguments( ) operation is called before any call is made to set_exception( ). This minor code will be generated if ctx( ) is called after set_exception( ) is called. MARSHAL system exception. In a normal DSI scenario, the ctx( ) operation of the ServerRequest pseudo object, if called, must be called after the arguments( ) operation is called and before the call is made to set_result( ). When set_result( ) is called, the user must supply all output arguments that were previously returned by the call to arguments( ). This minor code is generated if the call to set_result( ) does not contain all the output parameters that were returned by the call to arguments( ).
In addition, this minor code can be generated if you call set_result( ) without having previously called ctx( ) when the operation IDL contains a context expression.
BAD_PARAM system exception. In normal DSI processing, the user can indicate that an exception is to be returned to the client by calling set_exception( ). The Any passed to set_exception( ) must contain either a system exception or a user-defined exception, as specified in the raises( ) expression of the invoked operation's IDL definition. This minor code is generated if an Any is passed that does not contain a valid exception. BAD_INV_ORDER system exception. If arguments( ) or set_exception( ) has been called, calling arguments( ) again on the same ServerRequest will result in the generation of this minor code. Note that calling set_exception( ) obviates the need to call arguments( ). BAD_INV_ORDER system exception. In a normal DSI scenario, the arguments( ) operation of the ServerRequest pseudo object must be called exactly once. However, arguments( ) may only be called if no exception has been processed by a call to set_exception( ). This minor code is generated if arguments( ) is called after there has been a call to set_exception( ). BAD_INV_ORDER system exception. In a normal DSI scenario, the arguments( ) operation of the SeverRequest pseudo object must be called once (unless the client makes a call to the set_exception( ) operation). Such a call must be made, even if the operation signature contains no parameters. This minor code is generated if arguments( ) is not called. BAD_INV_ORDER system exception. In a normal DSI scenario, the user may indicate that an exception is to be returned to the client by calling set_exception( ). This occurs if the set_exception( ) operation is called more than once during a single DSI method invocation.