- CWYEB0001S: An incorrect value {0} for the adapterTypeID element was encountered.
- Explanation: The adapterTypeID element is incorrect. The adapter expects the type to be Siebel Resource Adapter.
- User Action: Verify that the correct adapterTypeID value is being passed to the enterprise metadata discovery tool.
- CWYEB0002S: The import configuration properties could not be created. Reason {0}
- Explanation: The import configuration properties could not be created.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB0003S: The property group for the filter property could not be obtained. Reason {0}.
- Explanation: The adapter was unable to get the property group for the filter property.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB0004S: The Siebel business service methods could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the methods for the Siebel business service.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB0005S: The Siebel integration objects could not be retrieved for the Siebel business service method. Reason {0}.
- Explanation: The adapter was unable to retrieve the Siebel integration objects for the Siebel business service method.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB0006S: The selection properties could not be created. Reason {0}.
- Explanation: The adapter was unable to create the selection properties.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB0007S: The metadata tree could not be constructed. Reason {0}.
- Explanation: The adapter was unable to construct the metadata tree with the Siebel objects.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB0008S: The top level Siebel objects could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the top level Siebel objects from the Siebel EIS.
- User Action: Verify that the filter property value provided is correct. If incorrect, fix the same and retry.
- CWYEB0012S: The primary business component of the Siebel business object could not be obtained. Reason {0}.
- Explanation: The adapter was unable to get the primary business component of the Siebel business object from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB0013S: The metadata object for Siebel business component could not be created. Reason {0}.
- Explanation: The adapter was unable to create the metaobject instance for the Siebel business component.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB0014S: The metadata object for the SiebelExistsResult business object could not be created. Reason {0}.
- Explanation: The adapter was unable to create the metadata object instance for the SiebelExistsResult business object.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB1000S: The unified properties could not be created. Reason {0}.
- Explanation: The adapter was unable to create the unified properties.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB1001S: The activation specification properties could not be created. Reason {0}.
- Explanation: The adapter was unable to create the activation spec properties.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB1002S: The resource adapter properties could not be created. Reason {0}.
- Explanation: The adapter was unable to create the resource adapter properties.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2000S: The Siebel repository objects could not be retrieved and set. Reason {0}.
- Explanation: The adapter was unable to retrieve the Siebel repository objects from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2001S: The ID for the Siebel repository could not be retrieved and set. Reason {0}.
- Explanation: The adapter was unable to retrieve the ID for the Siebel repository, from the Siebel EIS.
- User Action: The Siebel repository name provided in the connection properties window is likely to be invalid. If invalid, correct the same and retry. If not, check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2002S: The Siebel integration objects could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the Siebel integration objects from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2003S: The corresponding Siebel integration components for the Siebel integration object could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the Siebel integration components for the Siebel integration object, from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2004S: The Siebel business services could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the Siebel business services from the Siebel EIS.
- User Action: The filter property value provided might not invalid. Correct the same and retry. If not, check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2005S: The methods for the Siebel business service could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the Siebel business service methods from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2008S: The complex type arguments of the Siebel business service method could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the complex-type arguments that do not have the Siebel integration object type set.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2010S: The simple attributes of the Siebel integration component could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the simple attributes for the Siebel integration component, from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2012S: The attributes for the Siebel business service method could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the attributes for the Siebel business service method, from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2013S: The child integration components for the Siebel integration component could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the child integration components for the Siebel integration component, from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2014S: The top level Siebel integration component name for the Siebel integration object could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the top level Siebel integration component name for the Siebel integration object, from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2015S: The Siebel business objects having a primary business component could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the Siebel business objects that have the primary business component set, from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2016S: The Siebel business components under the Siebel business object could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the Siebel business components under the Siebel business object, from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2017S: The primary business component of the Siebel business object could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the primary business component of the Siebel business object, from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2018S: The single-valued fields of the Siebel business component could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the single valued fields of the Siebel business component, from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2019S: The primary multi-valued fields of Siebel multi-value links could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the primary multi-valued fields of Siebel multi-value links, from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2020S: The primary field in the Siebel multi-value group could not be found. Reason {0}.
- Explanation: The adapter was unable to find the primary field in the Siebel multi-value group, from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2021S: The simple-linked business component of the Siebel business object could not be retrieved. Reason {0}.
- Explanation: The adapter was unable to retrieve the simple-linked business component of the business object, from the Siebel EIS.
- User Action: Check the logs to determine the cause and take the necessary steps to resolve the problem.
- CWYEB2022S: The content of application-specific information {0} is not set for the field {1} in the business object.
- Explanation: The application-specific content is not set for the field in the business object.
- User Action: You should manually add the application-specific information values to the corresponding field in the generated business object.
- CWYEB3101S: The object level metadata for business object {0} could not be retrieved.
- Explanation: The metadata for the specified object could not be retrieved.
- User Action: Ensure that the business object level metadata is populated for the specified business object.
- CWYEB3102S: An exception occurred while processing the service data object (SDO), reason: {0}.
- Explanation: The output property set is empty.
- User Action: Check the log file for the reason. Correct the errors and resend the transaction.
- CWYEB3103S: The metadata for property " {0} " could not be obtained.
- Explanation: This error can occur if the metadata is empty or invalid for the specified property.
- User Action: Correct the metadata for the specified property in the business object.
- CWYEB3104S: A Siebel exception occurred. Reason: {0}.
- Explanation: The invocation of the specified method on the business service failed.
- User Action: Check the log file for the reason. Correct the errors and resend the transaction.
- CWYEB3105S: No key attribute is found set.
- Explanation: The object key specified in the Object Key field of the event component appears to be empty.
- User Action: Correct the object key in the event table.
- CWYEB3106W: Attribute {0}, defined as the PrimaryRowId, is empty.
- Explanation: The attribute value that is specified as the PrimaryRowId is empty.
- User Action: Ensure that the attribute specified as the PrimaryRowId is populated.
- CWYEB3107W: The business object level metadata is empty.
- Explanation: The business object level metadata cannot be empty, it needs to be set.
- User Action: Ensure that the object level metadata is populated with the correct information.
- CWYEB3108W: Attribute {0} is defined as a single container, but multiple objects were returned.
- Explanation: The attribute in the business object is defined as a single container, but more than one object was retrieved.
- User Action: If the specified object is defined as a single container, change the definition to multiple if necessary.
- CWYEB3109S: The property set could not be constructed from the input business object.
- Explanation: The property set could not be constructed from the input business object.
- User Action: Check the log file for the exact error message. Take corrective action as needed and resend the transaction.
- CWYEB3110S: The method invoked on the business service, has failed.
- Explanation: The method invoked on the business service, has failed.
- User Action: Check the log file for the exact error message. Take corrective action as needed and resend the transaction.
- CWYEB3111S: The business object could not be created from the output property set.
- Explanation: The business object could not be created from the output property set.
- User Action: Check the log file to get the exact error message. Take corrective action as needed and resend the transaction.
- CWYEB3112S: Application-specific information for the business service name is missing from the business object {0}.
- Explanation: The transaction has been terminated as the application-specific information for the BSN tag is empty.
- User Action: Set the object level application-specific information for the tag, BSN.
- CWYEB3113S: Application-specific information is null in the business object {0} for the attribute {1}.
- Explanation: The transaction has been terminated as the application-specific information for the FN tag is empty.
- User Action: Set the FN tag with the field name of the specified attribute.
- CWYEB3201S: Logging off failed! Reason {0}
- Explanation: If the Siebel server is down, the adapter will fail when trying to log off the beans.
- User Action: Check the Siebel server log file for the error.
- CWYEB3202S: Detach failed!
- Explanation: If the Siebel server is down, the adapter will fail when trying to detach the beans.
- User Action: Check the Siebel server log file for the reason.
- CWYEB3203S: Login failed!
- Explanation: If the Siebel server is down, the login attempt will fail.
- User Action: Check your Siebel server log file for the reason
- CWYEB3301S: The managed connection is invalid.
- Explanation: The managed connection not an instance of the SiebelManagedConnection class.
- User Action: Check the managed connection.
- CWYEB3302S: An error occurred while processing the request.
- Explanation: An error occurred while processing the request.
- User Action: Check the log file for the error message.
- CWYEB3401S: The EventID is invalid.
- Explanation: The EventID is invalid.
- User Action: Ensure that the event ID is of the correct data type.
- CWYEB3402S: The event time in the event component could not be converted into the proper DateTime format.
- Explanation: The event time in the event component might not be in the correct format.
- User Action: Correct the event time.
- CWYEB3403S: The event status could not be updated.
- Explanation: The adapter could not update the event status for the corresponding record in the event component.
- User Action: Check the log file for the reason.
- CWYEB3404S: The event priority could not be parsed.
- Explanation: The adapter could not parse the event priority for the corresponding record in the event component.
- User Action: Check the log file for the message.
- CWYEB3405S: The event status could not be parsed.
- Explanation: The adapter could not parse the event status for the corresponding record in the event component.
- User Action: Check the event status value in the event table and correct it.
- CWYEB3406S: The application-specific information for the event method is empty for business object {0}.
- Explanation: The application-specific information event method should not be empty.
- User Action: Enter the correct value for the event method in the business object level application-specific information.
- CWYEB3407S: The event type is invalid.
- Explanation: The event type must be either Create, Update, or Delete.
- User Action: Check the event type specified in the event store and correct it.
- CWYEB3501S: The top level Siebel business component cannot be found.
- Explanation: The business component name is not set on the application-specific information of the data object.
- User Action: Check the data object definition file.
- CWYEB3502S: More than one record was returned for the top level business component.
- Explanation: The primary key property values are not unique for the business component {0}.
- User Action: Check the value of the properties that are primary keys in the data object.
- CWYEB3503S: Records of the child component {0} could not be retrieved.
- Explanation: The child component does not match the Siebel business component.
- User Action: Check the container metadata of this property to see if the business component matches the Siebel enterprise information system (EIS).
- CWYEB3504S: More than one record was returned for the pickList business component: {0}.
- Explanation: The value of the From property is not unique for the pickList business component.
- User Action: Check the value of the From property, which is a foreign key of this pickList component.
- CWYEB3505S: The search specification for this pickList business component could not be set: {0}.
- Explanation: The value of the From property is not set for the pickList business component.
- User Action: Ensure that the value is set for the From property, which is a foreign key of this pickList component.
- CWYEB3506S: The search specification for this simple attribute pickList business component cannot be set. The value of the restrict property: {0} is not set.
- Explanation: The value of the restrict property is not set for the pickList business component, it should be set.
- User Action: Ensure that the value is set for the Restrict property. This will be a foreign key in this pickList business component.
- CWYEB3507S: The corresponding business component of the following property cannot be obtained: {0}.
- Explanation: The metadata information of the property is not correct.
- User Action: Check the property metadata for this property, and compare it with the data structure in Siebel.
- CWYEB3508S: The field {0} of the Siebel business component {1} cannot be updated.
- Explanation: The specified field of the Siebel business component configuration does not have update permissions.cannot be updated.
- User Action: Check the business component configuration of the Siebel enterprise information system (EIS) to confirm if the field is inactive. If yes, do the needful to make it updatable.
- CWYEB3509S: The property metadata definition is not correct. Error :{0}.
- Explanation: The property metadata definition is wrong.
- User Action: Check the application specific information of the property, correct the same as needed and resend the transaction.
- CWYEB3510S: The key property {0} value is null.
- Explanation: The key property value is null.
- User Action: Check the key property's value to see if it is set or not.
- CWYEB3511S: No record was retrieved using the search criteria provided.
- Explanation: No record exists in the Siebel system with these key values.
- User Action: Ensure that the key properties' values are correct.
- CWYEB3514S: The <To> application-specific information value of the pickList component is either empty or null.
- Explanation: The <To> application-specific information of the picklist component is either empty or null. Update it with the right value and resend the transaction.
- User Action: Check the business object definition of the <To> attribute of the pickList component in the metadata.
- CWYEB3515S: The fields in the <To> and <From> attributes of the pickList component do not match.
- Explanation: The fields in the <To> and <From> attributes of the pickList component must match.
- User Action: Check the business object definition of the <To> and <From> attributes of the pickList component in the metadata.
- CWYEB3516S: The property name specified in the <From> attribute of the pickList component metadata is not defined in the current data object.
- Explanation: The property name specified in the <From> attribute of the pickList component metadata is not defined in the current data object.
- User Action: Check the business object definition of the <From> attributes of the pickList component in the metadata and correct the same.
- CWYEB3518S: More than one record was returned for the pickList business component: {0}.
- Explanation: The value of the metadata of the restrict field of this simple pickList component might not be set correctly.
- User Action: Check the metadata of the restrict field of this simple pickList component.
- CWYEB3519S: The property {0} is not found in the definition of the object {1}.
- Explanation: The value of the application-specific information in the metadata of this component might not be set correctly.
- User Action: Check the metadata value to see if this is a correct property name.
- CWYEB3551S: The record for the picklist cannot be created. It is either bound or not allowed. Return {0}.
- Explanation: The record for the pick list cannot be created. It is either bound or not allowed.
- User Action: Check the log file for further information and take corrective action as needed.
- CWYEB3552S: A new record cannot be created for the Siebel business object {0}, business component {1}.
- Explanation: The input Siebel business object name and business component cannot be found in the Siebel server.
- User Action: Check the names of the input Siebel business object and business component.
- CWYEB3553S: A record cannot be created in the Siebel Server. Return {0}
- Explanation: A record cannot be created in the Siebel server.
- User Action: Check the details of the error in the log file.
- CWYEB3554S: More than one association component was found.
- Explanation: More than one association component was found based on your input value.
- User Action: The object representing the association component in the data object hierarchy does not contain unique values. Correct the same and resend the transaction.
- CWYEB3555S: The Siebel business component cannot be associated. Return: {0}.
- Explanation: The Siebel business component cannot be associated.
- User Action: Check the Siebel server exception in the log file.
- CWYEB3556S: An error occurred during the creation of the child business component. Return {0}.
- Explanation: An error occurred during the creation of the child business component.
- User Action: Check the log file for further information.
- CWYEB3558S: A record for the Siebel business component cannot be written.
- Explanation: A record for the Siebel business component cannot be written.
- User Action: Check the Siebel server exception in the log file and take corrective action as needed.
- CWYEB3559S: An error occurred while writing the record for the Siebel business component. Return {0}.
- Explanation: An error occurred while writing the record for the Siebel business component.
- User Action: Check the log file for further information.
- CWYEB3560S: An error was found while picking the record for the Siebel business component. Return {0}.
- Explanation: An error was found while picking the record for the Siebel business component.
- User Action: Check the log file for further information and take corrective action as needed.
- CWYEB3562S: The field value in the Siebel server cannot be set. Return {0}.
- Explanation: The field value in the Siebel server cannot be set.
- User Action: Check the Siebel server exception in the log file and take corrective action as needed.
- CWYEB3563S: The required field {0} is not set in the input data object.
- Explanation: The required field is not set in the input data object, it should be set.
- User Action: Fill in values for the required fields in the input data object.
- CWYEB3564S: The input data object contains an invalid object definition. Return {0}.
- Explanation: The input data object contains an invalid object definition.
- User Action: Check the log file for the reason and take corrective action as needed.
- CWYEB3565S: Either the Siebel business object instance or the business component instance cannot be released. Return {0}.
- Explanation: Either the Siebel business object instance or the business component instance cannot be released.
- User Action: Check the log file for the exact error and take corrective action as needed.
- CWYEB3566S: The destination data object does not have the field {0} that the source data object has.
- Explanation: The destination data object does not have the field that the source data object has.
- User Action: Check the destination data object and add the corresponding attribute. If not needed, remove the attribute from the source data object.
- CWYEB3571S: The Siebel business object or component cannot be obtained. Return {0}.
- Explanation: The Siebel business object or component cannot be obtained.
- User Action: Check the log file for further information.
- CWYEB3572S: The child business component cannot be deleted. Return {0}.
- Explanation: The child business component cannot be deleted.
- User Action: Check the log file for further information.
- CWYEB3573S: A set search specification error for the Siebel business component has occurred. Return {0}.
- Explanation: A set search specification error for the Siebel business component has occurred.
- User Action: Check the log file for further information.
- CWYEB3574S: The record to be deleted cannot be found.
- Explanation: The record to be deleted cannot be found.
- User Action: Check your input data object for incorrect key values. Correct the same and resend the transaction.
- CWYEB3575S: The record for the Siebel business component cannot be deleted. Return {0}.
- Explanation: The record for the Siebel business component cannot be deleted.
- User Action: Check the Siebel server exception in the log file.
- CWYEB3576S: An error occurred while retrieving records from the Siebel server. Return {0}.
- Explanation: An error occurred while retrieving records from the Siebel server.
- User Action: Check the log file for further information.
- CWYEB3577S: The collection returned from EIS is null or empty. The RetrieveAll operation cannot be completed.
- Explanation: The RetrieveAll operation cannot proceed because the collection returned from EIS is null or empty.
- User Action: Take corrective action based on the Siebel Exception.
- CWYEB3578S: The number of instances retrieved from the EIS is {0}. It exceeds the number allowed {1} for the input object {2}. The RetrieveAll operation cannot be completed.
- Explanation: The number of instances retrieved from the EIS exceeds the number allowed. The RetrieveAll operation cannot be completed.
- User Action: Fill in data against other attributes in the business object to add more conditionality. If it still does not help, increase the number of maximum records allowed in the interaction spec.
- CWYEB3579S: An error occurred while creating the container object for the RetrieveAll verb. Return {0}.
- Explanation: An error occurred while creating the container object for the RetrieveAll verb.
- User Action: Check the log file for further information.
- CWYEB3581S: An error occurred when the resource adapter attempted to associate the business component. Return {0}.
- Explanation: An error occurred when the resource adapter attempted to associate the business component.
- User Action: Check the Siebel server exception in the log file.
- CWYEB3583S: The child pick list business component with keys was not found: {0}
- Explanation: The child pick list business component with keys was not found.
- User Action: Check the input data object. Correct the key values as needed and resend the transaction.
- CWYEB3584S: The key values to the output data object could not be set. Return: {0}
- Explanation: The key values to the output data object could not be set.
- User Action: Check the log file. The data object schema should contain a key field.
- CWYEB3585S: An error occurred while checking for the existence of the Siebel business component. Return {0}.
- Explanation: An error occurred while checking for the existence of the Siebel business component.
- User Action: Check the log file for further information and take corrective action as needed.
- CWYEB3591S: Multiple records were returned for the top level business component.
- Explanation: A generic exception was generated.
- User Action: Take corrective action based on the information provided in the log file.
- CWYEB3592S: An exception was generated {0}.