JagORBSrvErrNum enumeration

Description

Type library name

JaguarTypeLibrary

DLL name

jagproxy.dll

Defines symbolic constants for errors that can occur during server-side execution of a method call.

Table 4-3 lists the codes for server-side error numbers defined in the JagORBServerErrNum enumeration. User-defined IDL exceptions are not supported and are mapped to error number 9000.

Table 4-3: JagORBServerErrNum error codes

Symbolic Error Code

Number

Description

jagSrvMethExcepErr

9000

The method implementation threw a user-defined exception while executing in EAServer.

jagSrvMethInvalidErr

9001

The method name is either invalid or is presently not defined in the component's interface.

jagSrvMethInvalidArgErr

9002

The invocation of the component method failed because an invalid number of parameters was passed or a parameter type mismatch occurred.

jagSrvMethNotImplErr

9003

The invocation of the component method failed because the component does not implement the method.

jagSrvCompPermErr

9004

The invocation of the method in EAServer failed because user does not have the permissions to instantiate the component.

jagSrvCompDeployErr

9005

The invocation of the method in EAServer failed because component implementation was not deployed in EAServer.

jagSrvInternalErr

9006

The invocation of the method in EAServer failed due a fatal internal error.

jagSrvArgCountErr

9007

The invocation of the method in EAServer failed because an invalid parameter type was used by the method.

jagSrvSrvConnectErr

9008

The requested operation failed since the client cannot to acquire connection to the server.

jagSrvConversionErr

9009

The invocation of the method in EAServer failed due to a data conversion error.

jagSrvFreeMemErr

9010

The invocation of the method in EAServer failed while releasing memory resources.

jagSrvIntfReposErr

9011

The invocation of the method in EAServer failed while trying to access the interface repository.

jagSrvOutOfMemErr

9012

The invocation of the method in EAServer failed while trying to acquire memory from the operating system.

jagSrvOutOfResErr

9013

The invocation of the method in EAServer failed since it cannot acquire the necessary resources.

jagSrvSrvRespErr

9014

The invocation of the method in EAServer failed because there was no valid response from the server.

jagSrvInvObjrefErr

9015

The invocation of the method in EAServer failed because the object reference is invalid.

Usage

In Visual Basic, exceptions are mapped to the built-in Err object. The exception number maps to Err.Number and the description is available as Err.Description. You can handle exceptions by activating error handling code with On Error Goto statement or by checking whether Err.Number is > 0.

The proxy type library defines error numbers for client-side errors in the JagORBClientErrNum enumeration and server-side error numbers in the JagORBSrvErrNum enumeration.

See also

JagORBClientErrNum enumeration