The ODA logs error messages to the ODA log. It logs any abnormal condition that it encounters during processing, regardless of the trace level.
The message contains a detailed description of the condition and the outcome and may also include extra information that may aid in debugging, such as business object dumps or stack traces (for exceptions).
Table 24 lists possible errors and the action you can take to remedy each one.
Error message | Description | Corrective action |
---|---|---|
The specified path does not exist: <path name> |
The connector ODA property BuyerPath is not set or is invalid. |
Verify that the BuyerPath property is set correctly. |
File not found: <file name> |
The specified meta-data file could not be found. |
Verify that the BuyerPath property is set correctly.
|
Class not found for file: <file name |
The ABClassMeta class cannot be found, or the meta-data file was created with a backlevel ABClassMeta class |
Verify that the ABClassMeta class is in the class path.
|
IO Error reading file: <file name> |
The ODA receives an error when reading a meta-data file. |
Verify that the user has the authority to open the file.
|
The ABClassMeta is null for class name: <class name> variant name: <variant name> |
A meta-data file could not be found for the specified class and variant. |
Regenerate the meta-data file from Ariba Buyer. |
Error creating BusObjAttr for <field name> in class <class name> |
An error occurred when adding the specified attribute to the business object definition for the specified class. | Verify that:
|
Error creating Business Object definition: <BO name>. Error Text: <error text> |
The ODA receives an error when creating a business object definition. | See the error text for more information. |