CWYED1000F: The adapter could not get a connector instance.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED1001E: The adapter could not get a user session.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED1002E: The adapter could not get a connection to the EnterpriseOne server. The instance might be down or the specified connection property values might be incorrect.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED1003E: The call to sign off a user session failed.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED1004E: The adapter could not introspect the managed connection factory properties.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED1005E: The adapter could not get an event service instance.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED1006E: The adapter could not get a synchronous event session.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED1007E: The call to close a synchronous event session failed.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED3000E: The call to begin an EnterpriseOne transaction failed.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED3001E: The call to commit an EnterpriseOne transaction failed.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED3002E: The call to roll back an EnterpriseOne transaction failed.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED3003E: The adapter could not load the EnterpriseOne Spec Source.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED3004E: The business function container \"{1}\", does not have a business function \"{0}\", defined as a child.
Explanation: The business function container does not contain the referenced business function.
User Action: Check the business function container and verify that the operation application-specific information is valid \"BSFNName\" for all the operations. Make sure all the business function names are valid.
CWYED3005E: The adapter could not create an executable method for the business function \"{0}\".
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED3006E: The value \"{2}\" could not be set for the \"{0}\" property of the \"{1}\" business function business object.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED3007E: The EnterpriseOne business function \"{0}\" could not be processed.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED3008E: An error occurred while processing the following business object: \"{0}\".
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED3009I: The \"{0}\" business object has been processed.
Explanation: The processing of a business object succeeded.
User Action: No action is required.
CWYED3010E: A required parameter, \"{0}\", is missing for business function \"{1}\".
Explanation: The business function could not be processed because a required parameter is missing.
User Action: Check the log and trace files and correct any errors.
CWYED3011E: \"{0}\" method execution returned with warnings.
Explanation: The processing of a business function executable method retuned with warnings.
User Action: Check the log and trace files and correct any errors.
CWYED3012E: The value \"{2}\" could not be set for the parameter \"{1}\" of the business function \"{0}\".
Explanation: The value \"{2}\" is invalid for the parameter \"{1}\" of the business function \"{0}\".
User Action: Check the log and trace files and correct any errors.
CWYED3013E: The connection failure error is thrown out.
Explanation: Because adapter can not successful connect JDE server in the configured retry times.
User Action: Check the net status, connection properties and whether the JDE server is up.
CWYED5000S: An XML List response message has an error code.
Explanation: XML List response has an error code, \"{0}\", and a message, \"{1}\".
User Action: Check the log and trace files and correct any errors.
CWYED5001S: The XML List could not be created from the \"{0}\" data object because the data object is not of the required XML List type: \"{1}\".
Explanation: The XML List could not be created from the data object because the object is not of the required type.
User Action: Check the log and trace files and correct any errors.
CWYED5002S: The XML List return object type, \"{0}\", is not valid and the XML List cannot be created.
Explanation: The XML List could not be created from the data object because the object is not of the required type.
User Action: Check the log and trace files and correct any errors.
CWYED5003S: An XML List serialization problem has occurred.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED5004S: The XML List could not be read.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED5005S: The following problem occurred while processing the XML List message: \"{0}\".
Explanation: Data cannot be extracted from the XML List message.
User Action: Check the log and trace files and correct any errors.
CWYED5006W: The XML List request message cannot be generated from Query property \"{0}\".
Explanation: The query property is not found on the return type.
User Action: Check the log and trace files and correct any errors.
CWYED5007W: The XML List request message cannot be generated from Query property \"{0}\".
Explanation: Either the application-specific information for the property is not defined, or the value (or values) for the property or multiplicity is not specified.
User Action: Check the log and trace files and correct any errors.
CWYED5008W: The first query clause, \"{0}\", should be set to WHERE.
Explanation: The first query clause is not a WHERE clause. Possibly the WHERE clause was skipped from the message.
User Action: Check the log and trace files and correct any errors.
CWYED6001S: The call to receive real-time events was not completed.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED6002S: The call to receive real-time events for once and only once event delivery could not be completed.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED6003S: The call to materialize the JDE structured record could not be completed.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED6004S: The business object for JDE event type \"{0}\" could not be found.
Explanation:
User Action: Check the business objects and make sure you have the business object for event type \"{0}\".
CWYED6005S: The failed event \"{0}\" from the absolute file path \"{1}\" could not be found.
Explanation:
User Action: Ensure that the failed event \"{0}\" is in the failed event directory.
CWYED6006S: The failed event \"{0}\" from the absolute file path \"{1}\" could not be found.
Explanation:
User Action: Ensure that the failed event \"{0}\" is correct in the failed event directory.
CWYED6007S: In failed event \"{0}\", one of necessary properties (Category/Type/SequenceNumber/XMLPayload) either does not exist or is empty.
Explanation:
User Action: Ensure that the failed event \"{0}\" is correct in the failed event directory.
CWYED6008S: In failed event \"{0}\", the value of SequenceNumber cannot be parsed to long.
Explanation:
User Action: Ensure that the value of SequenceNumber in the failed event \"{0}\" is correct in the failed event directory.
CWYED6009S: The failed event file \"{0}\" from the absolute file path \"{1}\" is unreadable.
Explanation:
User Action: Ensure that you have the enough authority to access the failed event file \"{0}\".
CWYED6010S: The failed event \"{0}\" cannot be written to directory \"{1}\".
Explanation:
User Action: Either the disk is full or there is an authority problem.
CWYED6011S: The format of event ID \"{0}\" is incorrect. The correct format should be EventCategory_EventType_SequenceNumber, for example: RTE_RTCOOUT_1.
Explanation:
User Action: Correct the format of the event ID in the event persistence table.
CWYED7000E: The metadata at the business object level could not be retrieved for the business object \"{0}\".
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED7001E: The metadata of the operation \"{0}\" could not be retrieved from the business object \"{1}\".
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED7002E: The metadata of the property \"{0}\" could not be retrieved from the business object \"{1}\".
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED7003E: The property representing the root business object was not found in the \"{0}\" business graph.
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED9000E: Bidirectional Transformation Error: An error occurred while creating the bidirectional context for the \"{0}\" property.
Explanation: Bidirectional Transformation Error: The adapter cannot create bidirectional context for property.
User Action: Check the log and trace files and correct any errors.
CWYED9001E: Bidirectional Transformation Error: An error occurred while transforming business object \"{0}\".
Explanation:
User Action: Check the log and trace files and correct any errors.
CWYED9002E: Bidirectional Transformation Error: An error occurred while transforming the metadata property \"{0}\" for the business object.
Explanation: Bidirectional Transformation Error: The adapter cannot transform a metadata property for business object.
User Action: Check the log and trace files and correct any errors.
CWYED9003E: Bidirectional Transformation Error: An error occurred while transforming the metadata property for attribute \"{0}\" for the business object.
Explanation: Bidirectional Transformation Error: The adapter cannot transform a metadata property for an attribute of the business object.
User Action: Check the log and trace files and correct any errors.
CWYED9004E: Bidirectional Transformation Error: An error occurred while transforming the metadata configuration property \"{0}\".
Explanation: Bidirectional Transformation Error: The adapter cannot transform a metadata configuration property.
User Action: Check the log and trace files and correct any errors.