Error Code | Description |
1000 | variable text threw a SiebelException: code(ErrorCode), msg(Message). ErrorCode is the Siebel exception code and Message is the exception message returned by Siebel. |
Explanation: A SiebelException occurred. | |
Action: Varies according to cause. | |
1001 | variable text threw: type(ExceptionType), msg(Message). ExceptionType is the type of exception and Message is the exception message returned by the Siebel Adapter. |
Explanation: An AdapterException has occurred. This error code is reserved for all exceptions that do not have a specific exception message listed below. | |
Action: Varies according to cause. | |
1002 | Invalid method inputs. |
Explanation: Invalid inputs to the method. | |
Action: Retry the operation with valid inputs. | |
1003 | An MVL field must be specified at each level in order to support the next query level. |
Explanation: An internal error occurred with an adapter service that uses a multi-valued link (MVL) business component. | |
Action: Ensure that the adapter service configuration includes an MVL business component in the Navigation Path tab. | |
1004 | Unable to {variable text} fields. |
Explanation: An exception was thrown when the adapter could not deactivate business component fields before executing a Query on the business component. | |
Action: Check the business component definition to ensure that the specified fields are included in the business component, and that there are no restrictions on the fields that may prevent the adapter from deactivating the field. | |
1005 | Unable to extract fields from the business component after a Query operation. |
Explanation: The operation failed, throwing a SiebelException: code(ErrorCode), msg(Message). Indicates a failure in retrieving business component fields after executing a Query. | |
Action: Ensure that the specified fields are included in the business component definition, and that there are no restrictions on the fields that may prevent the adapter from reading the field values. | |
1006 | Cannot set Query on the business component when performing an Insert operation. |
Explanation: Missing search expressions for the selected multi-value link and additional business components. | |
Action: Using the Search tab, define search expressions for the selected multi-valued link and additional business components. | |
1007 | Select {variable text} on the Navigation Path tab before you specify search criteria for it. |
Explanation: You did not select {variable text} on the Navigation Path tab. | |
Action: Select {variable text} on the Navigation Path tab before you specify search criteria for it on the Search tab. | |
1008 | Threw a non-fatal exception: type(ErrorType), msg(Message). ErrorType is the type of exception and Message is the exception message returned by the Siebel Adapter. |
Explanation: A non-fatal AdapterException has occurred. | |
Action: No response is necessary. For example, setRepositoryContext() throws an exception since it cannot be called on certain business components. This exception is logged, and does not require any user action. | |
1009 | The placeholder {variable text} does not correspond to a field in the input |
Explanation: The name of an input variable does not match the placeholder in the query specification. | |
Action: Save the change you made to the input variable name. | |
1010 | No records were returned as a result of the Query; unable to perform {variable text}. |
Explanation: Query failed to return one or more records when performing one of the following operations: Delete, Update, or Associate. | |
Action: Check the adapter service input and the search criteria specified in the Search tab. | |
1011 | Note: Message 1011 is intentionally omitted. |
1012 | Must select two business components for an Associate operation. |
Explanation: You failed to select two business components. | |
Action: Select two business components in the Navigation Path tab, and specify a search expression for each one in the Search tab. | |
1013 | Business service operation input, {variable text}, is a required value. |
Explanation: The names of a Business Service and a Business Service method are required parameters when executing the BusinessServiceOperation adapter service template. | |
Action: Specify the names of a Business Service and a Business Service method in the Business Service Inputs field on the Siebel Business Service Inputs/Outputs tab. | |
1014 | The number of input keys and values must match. |
Explanation: The arrays of Siebel property set keys and Siebel property set values that you selected contain a different number of keys and values. | |
Action: In the Business Service Inputs field on the Siebel Business Service Inputs/Outputs tab, ensure that the array of Siebel property set keys and the array of Siebel property set values contain the same number of keys and values. | |
1015 | There was no response from the Siebel Server. |
Explanation: An existing adapter connection object could not communicate with the Siebel Server, perhaps due to loss of network connectivity or Siebel Server shutdown. Action: The adapter will attempt to clean up the Siebel Adapter connection pool and re-connect to the Siebel Server. | |
Action: If the problem persists, restart the Siebel Adapter. | |
1016 | Invalid connection; please retry operation. |
Explanation: The adapter received a null connection object. | |
Action: Retry the operation. If the problem persists, restart your adapter connection using Integration Server Administrator. | |
1017 | Threw a SiebelException: code ({ErrorCode}), msg ({Message}). The connection pool will now be recycled. Please retry your operation. |
Explanation: An existing adapter connection object could not communicate with the Siebel Server, perhaps due to loss of network connectivity or Siebel Server shutdown. The BOI API returns an error code and error message indicating this fact. | |
Action: Retry the operation. If the problem persists, restart the Siebel Adapter. | |
1018 | Unable to get {variable text}. Not connected to Siebel Server; please check your network connection and make sure the Siebel Server is running. |
Explanation: Occurs when a stale connection is retrieved from the connection pool. A connection becomes stale when the adapter loses a physical connection to the Siebel Server, but the adapter considers the connection to be active. This can occur when the network connection has gone down or the Siebel Server shuts down unexpectedly. | |
Action: The adapter removes the stale connection and recycles that connection's pool. That is, it shuts down the connection pool and re-starts it. If this problem persists, please reset your Siebel Server connections. | |
1019 | One or more inputs are missing, Please check your inputs and retry the operation. |
Explanation: Improper inputs were passed to the AttachmentOperation or the InvokeBusinessComponent adapter service template. | |
Action: For an Attachment adapter service, check the values on the Attachment Operation Inputs tab. For an Invoke Business Component adapter service, check the values on the Invoke Business Component Method - Inputs tab. | |
1020 | Siebel Attachment operation returned: {variable text}. |
Explanation: Indicates whether the Attachment operation succeeded. | |
Action: None required. |