- CWLAE0000E: Relationship definition "{0}" was not found.
- Explanation: Relationship "{0}" is referenced in some files, e.g. in relationship instance file, but its definition cannot be found.
- User Action: Check whether the relationship name is correctly spelled. If it's correct, check whether the relationship file exists.
- CWLAE0001E: Role definition "{0}" was not found.
- Explanation: This role is referenced in a file, e.g. relationship instance file. In the file references it, it's thought of as in a relationship definition. But in fact in that relationship there is no such a role at all.
- User Action: Check whether the role name is spelled correctly. If it's corrent, check whether the role file exists.
- CWLAE0005I: RelationshipService encountered the exception:
- Explanation: An exception was encountered when the relationship service code was executing.
- User Action: This message present the stack trace when an exception is encountered. Users need to pay attention to the content of the stack trace. It may help users to determine the problem.
- CWLAE0100I: No participant was found for relationship "{0}", role "{1}", values: {2}.
- Explanation: When trying to retrieve a participant from the persistent store by the value, with the expectation that it exists, it's not found at all.
- User Action: The participant should have been created in previous run of relationship service. Check the operation of relationship service.
- CWLAE0101I: No participant was found for relationship "{0}", role "{1}", instance ID {2}.
- Explanation: When trying to retrieve a participant from the persistent store by the instance id, with the expectation that is exists, it's not found at all.
- User Action: The participant should have been created in previous run of relationship service. Check the operation of relationship service.
- CWLAE0102W: Attribute "{0}" of business object "{1}" is an empty string.
- Explanation: An business object is passed to relationship service, for which the attribute shouldn't be an empty string, but the case is that the attribute is empty string.
- User Action: This is a warning message. Empty string is thought of as meaningless. Check the data passed into relationship service.
- CWLAE0103W: A participant was created for relationship "{0}", role "{1}", values {2}. Its instance ID is {3}, but the expected ID is {4}.
- Explanation: A participant is created, for which the expected instance id is not the same as the actual instance id. This means that there may be mis-correlated participants.
- User Action: Check the database table.
- CWLAE0400W: Orphan role {0} was found. It will not be loaded.
- Explanation: The relationship that the role {0} was referring to was not found, so the role cannot be added to the parent relationship.
- User Action: Check the role and verify that its relationship (and TNS) is included in a different file.
- CWLAE0401I: Relationship was aggregated to the cache: {0}
- Explanation: This relationship is put into internal cache of relationship service.
- User Action: This is an infromational message. Users do not need to take any action.
- CWLAE0402I: Role {0} was aggregated to Relationship {1}
- Explanation: This role is put into the relationship.
- User Action: This is an infromational message. Users do not need to take any action.
- CWLAE0403W: Duplicate role {0} was found in Relationship: {1}.
- Explanation: A role was found in an individual file that existed already in the corresponding relationship.
- User Action: Verify the role in the separate file and delete it if it is not needed.
- CWLAE0404I: All relationships and roles (.rel and .rol files) in this application are beginning to be loaded.
- Explanation: This is an informational message. Relationship service is loading all relationships and roles it can find the scope of this appliction.
- User Action: No user action is needed.
- CWLAE0405W: The relationship from URL {0} could not be loaded. Error: {1}
- Explanation: It seems that the file is a relationship definition file, but relationship service fail to load a well-formed relationship from it.
- User Action: Check the file content to see whether it's a well-formed relationship definition. If it's not intended to define a relationship at all, ignore this message. If it's intended to define a relationship, check its format.
- CWLAE0406I: Tried to load relationship "{0}" from URL {1}, but this relationship has already been loaded. This one will be ignored.
- Explanation: After loaded a relationship from this file, relationship service runtime find that this relationship has ever been loaded from another file. The newly loaded relationship will be discarded.
- User Action: Remove the duplicated relationship file from the scope of the application.
- CWLAE0407W: Role from URL {0} could not be loaded. Error: {1}
- Explanation: It seems that this file is a role definition file, but relationship service fail to load a role from it.
- User Action: Check the file content to see whether this is well-formed role definition file. If it's not intended to define a role at all, ignore this message. If it's intended to define a role, check its format.
- CWLAE0408W: Relationship instances could not be loaded from URL {0}. Error: {1}
- Explanation: It seems that this file is a relationship instance file, but relationship service fail to load its content.
- User Action: Check the file content to see whether this is a well-formed relationship instance file. If it's not intended to present relationship instances, ignore this message. If it's intended to present relationship instances, check its format.
- CWLAE0409W: Role "{0}" (URL {1}) refers to a non-existent relationship "{2}". This role will be ignored.
- Explanation: This role's <relationship> element refers to a relationship, but that relationship is not found at all in the scope of this application.
- User Action: check whether the relationship file exists in the scope of this application.
- CWLAE0410I: Role "{0}" (URL {1}) refers to relationship "{2}", but in this relationship there is already a role with this name. This role will be ignored.
- Explanation: There're two role files defining the same role.
- User Action: Remove the redundant role file.
- CWLAE0411I: Loading of all relationships and roles in this application is done.
- Explanation: This is an informational message. Relationship service runtime loaded all relationship, role, and relationship instance files in the scope of this application.
- User Action: No user action is needed.
- CWLAE0412W: Relationship instance object from URL {0} refers to a non-existent relationship "{1}". It will be ignored.
- Explanation: Relationship instance refers to a relationship, but that relationship is not found at all in the scope of the application.
- User Action: check whether the relationship file exists in the scope of the application.
- CWLAE0413W: Relationship instance object from URL {0} refers to relationship "{1}", but an instance ID already exists.
- Explanation:
- User Action:
- CWLAE0414I: Runtime schemas for all loaded relationships and roles in this application are being created.
- Explanation: This is an informational message. Relationship service runtime begins to create runtime schemas for loaded relationships and roles.
- User Action: No user action is needed.
- CWLAE0415I: The creation of runtime schemas for all loaded relationships and roles in this application is ending.
- Explanation: This is an informational message. Relationship service runtime completes creating runtime schemas for loaded relationships and roles.
- User Action: No user action is needed.
- CWLAE0416W: Instance data for relationship "{0}" failed to be populated, error: {1}.
- Explanation: Error occurs while relationship service runtime is populating relationship instance into persistent store.
- User Action: Check the error.
- CWLAE0417W: Relationship "{0}" not found for application "{1}"
- Explanation: The relationship definition is not included in the application
- User Action: Specify the relationship name correctly
- CWLAE0418W: Role "{0}" not found for application "{1}"
- Explanation: The role definition is not inclued in the application
- User Action: Specify the role name correctly
- CWLAE0451W: The list that RelationshipInstance represents is null.
- Explanation: There is no data contained in ri files.
- User Action: Please ensure that ri files contain non-empty data.
- CWLAE0452W: The URL of file is null.
- Explanation: Invalid URL for the ri file.
- User Action: Please ensure the file URL is valid.
- CWLAE0453W: The relationshipinstance file is invalid.
- Explanation: Invalid relInstance data contained in the ri file.
- User Action: Please check that the format of ri file is valid.
- CWLAE0454W: RelationshipInstance was not found in URL "{0}".
- Explanation: There is no relInstance contained in the file URL.
- User Action: Please ensure there are non-empty relInstance data contained in the file URL.
- CWLAE0455W: Inconsistent instance ID in one relationship instance.
- Explanation: It is probably caused by existed role instance.
- User Action: Please ensure that there is no duplicate roleInstances for the same role.
- CWLAE0456E: Relationship Instance Business Graph can not contain instances for more than one relationship
- Explanation: Relationship Instance Business Graph can not contain instances for more than one relationship
- User Action: Please make sure the graph contains instances for a single relationship
- CWLAE0457E: Application directory for the relationship "{0}" is null
- Explanation: Application directory for the relationship is null
- User Action: Please make sure the relationship is installed properly