A
COM Automation Error Messages

This appendix includes the following:

• Oracle COM Automation Feature, PL/SQL Errors
  
  
• Microsoft COM Automation Errors

Oracle COM Automation Feature, PL/SQL Errors

The following is a list of Oracle COM Automation Feature PL/SQL errors and their common causes.

COM-0001: Not a boolean type

Action: Make sure that the variable is of the appropriate datatype.

COM-0002: Invalid Token or no interface for token

Action: Make sure that the interface exists.

COM-0003: Maximum Objects reached

Action: Make sure that objects are destroyed after they are used by calling DestroyObject.

COM-0004: The registered CLSID for the ProgID is invalid

Action: Check that the COM component of the specified ProgID is registered.

COM-0005: An error occurred writing the CLSID to the registry

Action: Make sure your registry can be written to and is not corrupted.

COM-0006: A specified class is not registered in the registration database

Action: Make sure the class is registered.

COM-0007: Failed to initialize COM Automation object

Action: Make sure the object is registered as a COM Automation object.

COM-0008: No interface is supported

Action: Check that the interface specified is valid.

COM-0009: Failed to get type info count

Action: Check that the object is properly registered.

COM-0010: Does not support type info implementation

Action: Check that the object is properly registered.

COM-0011: Failed to get type information

Action: Check that the object is properly registered.

COM-0012: Failed to get type attributes

Action: Check that the object is properly registered.

COM-0013: Failed to get function description at index

Action: Check that the object is properly registered.

COM-0014: Failure to invoke

Action: Check that the method name is valid for the object.

COM-0015: Bad parameter count

Action: Make sure the number of parameters for a method is equal to the count.

COM-0016: One of the arguments in rgvarg is not a valid variant type

Action: Check that the object is properly registered.

COM-0017: The application needs to raise an exception. The structure passed in pexcepinfo should be filled in

Action: Make sure the structure in pexcepinfo is initialized.

COM-0018: The requested member does not exist, or the call to Invoke tried to set the value of a read-only property

Action: Make sure the property value can be written to or the member exists.

COM-0019: This implementation of IDispatch does not support named arguments

Action: Do not use named arguments. Use standard parameter passing.

COM-0020: One of the arguments in rgvarg could not be coerced to the specified type

Action: Make sure that the coerced arguments are of compatible datatypes.

COM-0021: One of the parameter dispatch IDs does not correspond to a parameter on the method

Action: Make sure the arguments are passed in correctly.

COM-0022: One or more of the arguments could not be coerced

Action: Make sure your arguments are compatible.

COM-0023: The interface ID passed in riid is not IID_NULL

Action: Make sure the interface ID passed is IID_NULL.

COM-0024: The member being invoked interprets string arguments according to an unrecognized locale ID (LCID)

Action: Make sure your localeID is valid.

COM-0025: Not an optional parameter

Action: Make sure your argument count is correct for the number of parameters passed in.

COM-0026: Name exceeded the maximum character allowed

Action: Enter 1024 characters or less for the name.

COM-0027: This class cannot be created as part of an aggregate

Action: Do not create this class as part of an aggregate.

Microsoft COM Automation Errors

The following is a list of Microsoft COM Automation errors and their common causes. Both the hexadecimal and binary error codes are listed.

(0x800401f3) (-2147221005) Invalid class string

Cause: The specified ProgID or CLSID is not registered as a COM object in the registry of the local computer.

(0x8007007e) (-2147024770) The specified module could not be found

Cause: The specified COM object is registered as an in-process COM server (DLL file), but the DLL file could not be found or loaded.

(0x80020004) (-2147352572) Parameter not found

Cause: A named parameter was specified before a positional parameter.

Action: Ensure that all named parameters are specified after all positional parameters.

(0x80020005) (-2147352571) Type mismatch

Cause: The datatype of a PL/SQL local variable used to store a returned property value or a method return value did not match the Visual Basic datatype of the property or method return value.

Action: Ensure that the local variable is of the appropriate datatype. Or, the return value of a property or a method was requested, but it does not return a value.

(0x80020006) (-2147352570) Unknown name

Cause: The specified property or method name was not found for the specified object.

(0x80020008) (-2147352568) Bad variable type

Cause: The datatype of a PL/SQL or Java value passed as a method parameter did not match the COM Automation datatype of the method parameter, or a NULL value was passed as a method parameter.

Action: Ensure that any local variables used as method parameters are of the appropriate datatype and are set to a value other than NULL.

(0x80080005) (-2146959355) Server execution failed

Cause: The specified COM object is registered as a local COM server (.EXE file), but the .EXE file could not be found or started.