CWYES6001-6999: PeopleSoft Enterprise resource adapter - Managed connection
- CWYES6011
- The adapter could not get a connection to the EIS. The EIS instance may be down or the specified connection property values may be incorrect.
- Severity
- 40 : Stop Error
- Explanation
- The adapter could not get a connection to the EIS. The EIS instance may be down or the specified connection property values may be incorrect.
- Response
- Restart the EIS if it is down and confirm that the specified connection property values are correct.
- CWYES6012
- The call to disconnect the session instance failed.
- Severity
- 30 : Severe error
- Explanation
- The call to disconnect the session instance failed.
- Response
- Check the log file for the reason. Correct the errors logged. By default, the log file is $<insert_SERVER_LOG_ROOT>/trace.log.
- CWYES6101
- The Create operation has failed.
- Severity
- 30 : Severe error
- Explanation
- The Create operation has failed.
- Response
- Check the log file for the reason. Correct the errors logged. By default, the log file is $<insert_SERVER_LOG_ROOT>/trace.log.
- CWYES6103
- The error messages in the PeopleSoft Message Collection are as follows: <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The error messages from the PeopleSoft Message Collection are retrieved if EISException is thrown. If there are no messages in the collection or if it is null, it could be a PeopleTools issue.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft Message Collection.
- CWYES6104
- The child Create operation has failed.
- Severity
- 30 : Severe error
- Explanation
- The child Create operation has failed.
- Response
- Check the log file for the reason. Correct the errors logged. By default, the log file is $<insert_SERVER_LOG_ROOT>/trace.log.
- CWYES6105
- The call to the PeopleTools API 'create' has failed. The Create operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The Create operation cannot proceed because the call to the PeopleTools API 'create' has failed.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft message collection.
- CWYES6106
- The PeopleTools API 'getEffectiveItemNum' returned the insert position -1. The adapter will use InsAtOldestEffDtPos or InsAtCurrentEffDtPos,if set.
- Severity
- 10 : Warning
- Explanation
- The child create transaction will continue if InsAtOldestEffDtPos or InsAtCurrentEffDtPos is set and the PeopleTools API 'get'EffectiveItemNum returns a -1.
- Response
- If either InsAtOldestEffDtPos or InsAtCurrentEffDtPos is not already set to true, set one of them to true.
- CWYES6107
- The PeopleTools API 'getEffectiveItemNum' returned the insert position -1. But the application-specific information for neither of the tags InsAtOldestEffDtPos or InsAtCurrentEffDtPos is set. The child create transaction can not continue.
- Severity
- 30 : Severe error
- Explanation
- The child create transaction will continue if one of the tags, InsAtOldestEffDtPos or InsAtCurrentEffDtPos, is set and the PeopleTools API 'get'EffectiveItemNum returns a -1.
- Response
- Set one of the tags, either InsAtOldestEffDtPos or InsAtCurrentEffDtPos, to true.
- CWYES6108
- The PeopleTools API call to get the dummy row has failed. The child Create operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The child Create operation cannot be completed as the PeopleTools API call to get the dummy row failed.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft Message Collection.
- CWYES6109
- The call to the PeopleTools API 'insertItem' has failed. The child Create operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The child Create operation cannot be completed because the call to the PeopleTools API 'insertItem' failed.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft Message Collection.
- CWYES6110
- The effective dated property <insert_0> is not set. The child Create operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The child Create operation cannot be completed because the effective dated property is not set.
- Response
- If the property is not an effective dated component, remove or set the EffectiveDate tag against the property to false.
- CWYES6111
- A number format exception has been thrown when trying to parse the effective sequence property value. The adapter will set the value to 0.
- Severity
- 10 : Warning
- Explanation
- A number format exception has been thrown when trying to parse the effective sequence property value. The adapter will set the value to 0.
- Response
- No action is required.
- CWYES6112
- The IgnoreEffectiveSequence is set to 'true'. But the application specific information for the neither of the tags InsAtOldestEffDtPos or InsAtCurrentEffDtPos is set.
- Severity
- 10 : Warning
- Explanation
- The child create transaction will continue if one of the tags, InsAtOldestEffDtPos or InsAtCurrentEffDtPos, is set and the IgnoreEffectiveSequence is set to 'true'.
- Response
- Set one of the tags, InsAtOldestEffDtPos or InsAtCurrentEffDtPos, to true.
- CWYES6201
- The Update operation has failed.
- Severity
- 30 : Severe error
- Explanation
- The Update operation has failed.
- Response
- Check the log file for the reason. Correct the errors logged.
- CWYES6202
- The session instance call to get the component interface instance <insert_0> failed. The Update operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The session instance call to get the component interface instance failed. The Update operation cannot be completed.
- Response
- Ensure that the correct component interface name is set in the top-level business object ASI.
- CWYES6203
- The error messages in the PeopleSoft Message Collection are as follows: <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The error messages from the PeopleSoft Message Collection are retrieved if an EISException is thrown. If there are no messages in the collection or if it is null, it could be a PeopleTools issue.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft Message Collection.
- CWYES6204
- The call to the PeopleTools API 'get' has failed. The Update operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The Update operation cannot proceed because the call to the PeopleTools API 'get' has failed.
- Response
- Take corrective action based on the error message logged from the PeopleSoft message collection.
- CWYES6205
- The call to GetMatchingItem has failed. The child Update operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The child Update operation cannot be completed because the call to GetMatchingItem failed.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft Message Collection.
- CWYES6206
- The child Update operation has failed.
- Severity
- 30 : Severe error
- Explanation
- The child Update operation has failed.
- Response
- Check the log file for the reason. Correct the errors logged.
- CWYES6301
- The Retrieve operation has failed.
- Severity
- 30 : Severe error
- Explanation
- The Retrieve operation has failed.
- Response
- Check the log file for the reason. Correct the errors logged.
- CWYES6302
- The session instance call to get the component interface instance <insert_0> failed. The Retrieve operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The session instance call to get the component interface instance failed. The Retrieve operation cannot be completed.
- Response
- Ensure that the correct component interface name is set in the top-level business object ASI.
- CWYES6303
- The error messages in the PeopleSoft Message Collection are as follows: <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The error messages from the PeopleSoft Message Collection are retrieved if an EISException is thrown. If there are no messages in the collection or if it is null, it could be a PeopleTools issue.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft Message Collection.
- CWYES6304
- The call to the PeopleTools API 'get' has failed. The Retrieve operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The Retrieve operation cannot proceed because the call to the PeopleTools API 'get' has failed.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft message collection.
- CWYES6401
- The RetrieveAll operation has failed.
- Severity
- 30 : Severe error
- Explanation
- The RetrieveAll operation has failed.
- Response
- Check the log file for the reason. Correct the errors logged.
- CWYES6402
- The session instance call to get the component interface instance <insert_0> failed. The RetrieveAll operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The session instance call to get the component interface instance failed. The RetrieveAll operation cannot be completed.
- Response
- Check if the correct component interface name is set in the top-level business object ASI.
- CWYES6403
- The error messages in the PeopleSoft Message Collection are as follows: <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The error messages from the PeopleSoft Message Collection are retrieved if an EISException is thrown. If there are no messages in the collection or if it is null, the problem might be related to PeopleTools.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft Message Collection.
- CWYES6404
- The collection returned from EIS is null or empty. The RetrieveAll operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The RetrieveAll operation cannot proceed because the collection returned from the EIS is null or empty.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft message collection.
- CWYES6405
- The number of instances retrieved from the EIS is <insert_0>. It exceeds the number allowed <insert_1> for the input object <insert_2>. The RetrieveAll operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The number of instances retrieved from the EIS exceeds the number allowed. The RetrieveAll operation cannot be completed.
- Response
- Fill in data against other find keys 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.
- CWYES6501
- The soft delete operation has failed.
- Severity
- 30 : Severe error
- Explanation
- The soft delete operation has failed.
- Response
- Check the log file for the reason. Correct the errors logged.
- CWYES6502
- The session instance call to get the component interface instance <insert_0> failed. The soft delete operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The session instance call to get the component interface instance failed. The soft delete operation cannot be completed.
- Response
- Ensure that the correct component interface name is set in the top-level business object ASI.
- CWYES6503
- The error messages in the PeopleSoft Message Collection are as follows: <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The error messages from the PeopleSoft Message Collection are retrieved if an EISException is thrown. If there are no messages in the collection or if it is null, the problem could be related to PeopleTools.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft Message Collection.
- CWYES6504
- The call to the PeopleTools API 'get' has failed. The soft delete operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The soft delete operation cannot proceed because the call to the PeopleTools API 'get' has failed.
- Response
- Take corrective action based on the error message logged from the PeopleSoft message collection.
- CWYES6505
- The matching item could not be found for the input child object <insert_0>. The child delete operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The child delete operation cannot be completed because the matching item could not be retrieved for the corresponding child object.
- Response
- Confirm that the item exists in the EIS.
- CWYES6506
- The child delete operation has failed.
- Severity
- 30 : Severe error
- Explanation
- The child delete operation has failed.
- Response
- Check the log file for the reason. Correct the errors logged.
- CWYES6601
- The Exists operation has failed.
- Severity
- 30 : Severe error
- Explanation
- The Exists operation has failed.
- Response
- Check the log file for the reason. Correct the errors logged.
- CWYES6602
- The session instance call to get the component interface instance <insert_0> failed. The Exists operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The session instance call to get the component interface instance failed. The Exists operation cannot be completed.
- Response
- Ensure that the correct component interface name is set in the top-level business object ASI.
- CWYES6603
- The error messages in the PeopleSoft Message Collection are as follows: <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The error messages from the PeopleSoft Message Collection are retrieved, if an EISException is thrown. If there are no messages in the collection or if it is null, the problem might be related to PeopleTools.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft Message Collection.
- CWYES6604
- The call to the PeopleTools API 'get' has failed. The Exists operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The Exists operation cannot proceed because the call to the PeopleTools API 'get' has failed.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft message collection.
- CWYES6701
- The Retrieve operation has failed for the PeopleSoftNoOperationCommand instance.
- Severity
- 30 : Severe error
- Explanation
- The Retrieve operation has failed for the PeopleSoftNoOperationCommand instance.
- Response
- Check the log file for the reason. Correct the errors logged.
- CWYES6702
- The session instance call to get the component interface instance <insert_0> failed. The top-level component could not be retrieved.
- Severity
- 30 : Severe error
- Explanation
- The session instance call to get the component interface instance failed. The top-level component could not be retrieved.
- Response
- Ensure that the correct component interface name is set in the top-level business object ASI.
- CWYES6703
- The error messages in the PeopleSoft Message Collection are as follows: <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The error messages from the PeopleSoft Message Collection are retrieved if an EISException is thrown. If there are no messages in the collection or if it is null, the problem might be related to PeopleTools.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft Message Collection.
- CWYES6704
- The call to the PeopleTools API 'get' has failed. The top-level object Retrieve operation cannot be completed.
- Severity
- 30 : Severe error
- Explanation
- The top-level object operation cannot proceed because the call to the PeopleTools API 'get' has failed.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft message collection.
- CWYES6705
- The call to GetMatchingItem has failed. The child item could not be retrieved.
- Severity
- 30 : Severe error
- Explanation
- The child item could not be retrieved because the call to GetMatchingItem failed.
- Response
- Take corrective action based on the error message retrieved from the PeopleSoft Message Collection.
- CWYES6706
- The child item Retrieve operation has failed.
- Severity
- 30 : Severe error
- Explanation
- The child item Retrieve operation has failed.
- Response
- Check the log file for the reason. Correct the errors logged.
- CWYES6801
- The connect call on the session instance failed. The polling of events from the event store cannot be done.
- Severity
- 40 : Stop Error
- Explanation
- The polling of events from the event store cannot be done as the session instance could not be connected.
- Response
- Ensure that the property values are correct in the ActivationSpec.
- CWYES6802
- The PeopleTools API call createSession failed. The session instance is null.
- Severity
- 40 : Stop Error
- Explanation
- The PeopleTools API call createSession failed. The session instance is null.
- Response
- Ensure that the property values are correct in the ActivationSpec
- CWYES6803
- A generic exception has been thrown. The polling of events from event store cannot be done.
- Severity
- 40 : Stop Error
- Explanation
- A generic exception has been thrown. The polling of events from event store cannot be done.
- Response
- Check the ActivationSpec for the correctness of the property values.
- CWYES6804
- The session instance could not get the instance of the event component interface <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The session instance could not get the instance of the event component interface <insert_0>.
- Response
- Check the ActivationSpec for the correctness of the property value, eventCIName. Also confirm that the corresponding Java API classes for the component interface have been added to the adapter class path.
- CWYES6805
- The adapter was unable to parse the date out of the event time <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- A ParseException was thrown when the adapter was parsing the date out of the event time.
- Response
- Confirm that the event time is set properly in the events being published to the event table.
- CWYES6806
- The adapter was unable to change the status of the future dated event to 0.
- Severity
- 30 : Severe error
- Explanation
- The adapter was unable to change the status of the future dated event to 0.
- Response
- Check to see if there is any peoplecode that is preventing the change.
- CWYES6807
- The get call to retrieve the event with the event ID <insert_0> has failed.
- Severity
- 30 : Severe error
- Explanation
- The get call to retrieve the event has failed.
- Response
- No action is required.
- CWYES6808
- The adapter was unable to update the status of the event to <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The adapter was unable to update the status of the event.
- Response
- Check to see if there is any peoplecode that is preventing the change.
- CWYES6809
- The call to get the object name, verb, or keys has failed for the event with the ID <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The call to get the object name, verb, or keys has failed for an event.
- Response
- Ensure that the object name, verb, and keys are properly set in the event table for the ID.
- CWYES6810
- The corresponding component could not be retrieved for the event with the ID <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The corresponding component could not be retrieved for an event.
- Response
- Ensure that the object name, verb, and keys are properly set in the event table record.
- CWYES6811
- The session is no longer valid.
- Severity
- 40 : Stop Error
- Explanation
- The session is no longer valid.
- Response
- Check if the enterprise information system (EIS) is operational.
- CWYES6812
- The language code must be three characters.
- Severity
- 10 : Warning
- Explanation
- When connecting to the enterprise information system (EIS), you must set a three character language code, for example, ENG.
- Response
- Correct the language code value.
- CWYES6901
- The adapter could not create the event.
- Severity
- 30 : Severe error
- Explanation
- The adapter could not create the event.
- Response
- Ensure that the event information is in the correct format.