Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11g Release 1 (11.1.1.5.0)

Part Number E10113-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

21 BPM-09708 to BPM-40011

NOTE: Some errors are shared between SOA and BPM, and their prefix may be "BPM" instead of the correct prefix "ORABPEL". However, the error number is always accurate. If you cannot locate a particular error in this file -- if the prefix does not match with the error number, then consider the error number while searching for a solution.

BPM-09708: Error while querying workflow task {0}
Cause: Error while querying workflow task {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-09713: Invalid logical operator in predicate
Cause: An invalid logical operator was used in the predicate.
Action: Specify a valid logical operator (AND or OR) for the predicate.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-09714: Invalid predicate operator
Cause: Invalid predicate operator {0}
Action: Specify a valid logical operator for the predicate.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-09715: Invalid predicate operator for list values
Cause: Invalid predicate opertor for list values. List values are only supported for IN and NOT_IN operator
Action: Use appropriate operator in the predicate for list values.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-09716: Invalid value type for predicate
Cause: Invalid value type {0} for predicate column type {1}
Action: Provide a valid value type for the predicate specified. Refer to TableConstants for data types

Level: 1

Type: ERROR

Impact: Programmatic

BPM-09717: Predicate values are null
Cause: Predicate values are null for operator {0}
Action: Provide a valid predicate value for the predicate.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-09719: Trying to update a deleted task {0}
Cause: The task {0} was already deleted.
Action: Execute the query to fetch new tasks.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-09732: Persistency service internal error
Cause: Persistency service internal error
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10000: Dynamic Exception Test Case.
Cause: Dynamic Exception Test Case thrown: {0}
Action: This error happens in dynamic exception test case sceanrios. Refer to the soainfra log files for details and contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10101: Error while updating task
Cause: Error while updating task {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10107: Error in withdrawing task
Cause: Error while withdrawing task {0}.
Action: Check the error stack and fix the cause of the error. Contact Oracle Support Services if the error persists.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10129: Notification for task could not be processed
Cause: Notification for task {2} could not be processed.
Action: Make sure that the notification configuration is correct and the messages are specified correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10197: Error in computing workflow auto release duration
Cause: Error in computing workflow auto release duration for task "{0}".
Action: Make sure that the auto release configuration is correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10199: Error in computing the next workflow reminder time
Cause: Error in computing the next workflow reminder time for task "{0}".
Action: Make sure that the notification reminder configuration is correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10200: Error in workflow reminder configuration
Cause: Error in workflow reminder configuration for task "{0}". Reminders are configured in the routing slip XML file.
Action: Verify that the routing slip file is valid and conforms to its schema. The common errors are invalid RECCURENCE integer value, invalid RELATIVE value, invalid DURATION value.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10206: Error in retrieving task metadata
Cause: Error in retrieving task metadata because the task is no longer valid.
Action: Only valid tasks can by looked up.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10207: Error in retrieving task metadata
Cause: Error in retrieving task metadata because because business process "{1}" version "{2}" that created the task is either undeployed or turned off in the domain "{0}".
Action: If the process is undeployed, the task is no longer valid. If the process was turned off, the task metadata can be retrieved when the process state is turned on.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10301: Email account does not exist
Cause: Email Account {0} does not exist
Action: Check Workflow Notification Configuration. Verify that email account is configured

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10302: Email account already exists
Cause: Email account {0} already exists
Action: Check Workflow Notification Configuration. Ensure that each account has unique name

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10303: Fax cover page details does not exist
Cause: Fax cover page details for cover page {0} does not exist
Action: Check Workflow Notification Configuration. Verify that fax cover page exists

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10304: Fax cover page details already exist
Cause: Fax cover page details for cover page {0} already exists
Action: Check Workflow Notification Configuration. Ensure that a page detail is not entered twice

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10305: Illegal Argument
Cause: name cannot be null
Action: Check Workflow Notification Configuration. Configuration name cannot be null

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10306: Illegal Argument
Cause: Old name or new name cannot be null
Action: Check Workflow Notification Configuration. Configuration name cannot be null

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10307: Illegal Argument
Cause: name, file location or mimetype cannot be null
Action: Check Workflow Notification Configuration. name, file location or mimetype cannot be null

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10310: xml parsing error in configuration file
Cause: Error in parsing notification service configuration file {}
Action: Internal Error. Check Workflow Notification Configuration.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10311: Email protocol not supported
Cause: Email protocol {0} is not supported
Action: Check Workflow Notification Configuration. Change Email protocol.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10312: Invalid Post Read Operation
Cause: Invalid Post Read Operation
Action: Protocol specified does not support Post Read Operation. Modify Workflow Notification Configuration.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10313: No Outgoing e-mail settings
Cause: E-mail account {0} does not have outgoing e-mail settings
Action: Check Workflow Notification Configuration. Configure outgoing e-mail settings

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10314: No General e-mail settings
Cause: E-mail account {0} does not have general e-mail settings
Action: Check Workflow Notification Configuration. Configure general e-mail settings

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10315: No Incoming e-mail settings
Cause: E-mail account {0} does not have incoming e-mail settings
Action: Check Workflow Notification Configuration. Configure Incoming e-mail settings

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10316: E-mail Receiver already associated
Cause: An e-mail receiver is already associated with {0} e-mail account
Action: Internal Error. Ensure that only one receiver is registered for an e-mail account.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10317: E-mail folder does not exist
Cause: E-mail folder {0} does not exist
Action: Check Workflow Notification Configuration. Verify folder name in Incoming e-mail settings

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10318: Cannot connect to iAS Wireless notification webservice
Cause: Cannot connect to iAS wireless notification webservice running at {0}
Action: Check Workflow Notification Configuration. Configure IAS Wireless settings

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10319: iAS Wireless notification error
Cause: iAS Wireless notification error
Action: Check IAS Wireless settings in Notification Configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10320: iAS Wireless settings not configured
Cause: iAS Wireless settings not configured
Action: Check IAS Wireless settings in Notification Configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10321: Notification Channel not supported
Cause: Notification Channel {0} is not supported
Action: IAS Wireless does not support requested channel.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10322: Illegal Argument
Cause: Folder Name cannot be null
Action: Check Workflow Notification Configuration. Folder Name for Post Read Operation cannot be null.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10323: Internal Error
Cause: Cannot create {0} object
Action: Refer to the log file that is configured for oracle.soa.services.notification for more details on this error and contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10324: Cannot read fax cover page file
Cause: Cannot read fax cover page from file {0}
Action: Check Workflow Notification Configuration. Ensure that the FAX cover page exists as specified in configuration.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10325: Mime-Type not supported
Cause: mime-type {0} is not supported for channel {1}
Action: Internal Error. Ensure that payload content's mime type is one of supported types.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10326: Illegal Argument
Cause: From account is not set in e-mail payload
Action: Check Workflow Notification Configuration. From account is not set in payload.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10327: From Account is not configured
Cause: From account {0} is not configured
Action: Check Workflow Notification Configuration.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10328: Error in sending e-mail message
Cause: Error in sending e-mail message
Action: Check Workflow Notification Configuration. Ensure that the Email Server could be connected.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10329: user-id not set
Cause: user-id field is not set in the user payload
Action: Internal Error. Payload does not contain user id

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10330: group-id is not set
Cause: group-id field is not set in the group payload
Action: Internal Error. Payload does not contain group id

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10331: Could not send notification to user
Cause: Could not send notification to user {0}
Action: Check Workflow Notification Configuration. Ensure that underlying channels are configured.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10332: Error in post-read operation
Cause: Error while doing post-read operation on e-mail account {0}
Action: Check Workflow Notification Configuration. Check folder name and post read operation for incoming setting.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10333: Error in reading e-mail message
Cause: Error in reading e-mail message from account {0}
Action: Check Workflow Notification Configuration. Ensure that the Email Server could be connected.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10334: Error in closing e-mail folder
Cause: Error in closing e-mail folder {0}
Action: Check Workflow Notification Configuration. Verify folder name in incoming setting.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10335: Error in notification service initialization
Cause: Error in notification service initialization
Action: Internal Error. Ensure that the Notification Configuration file is valid and could be loaded.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10336: Invalid recipient address
Cause: Recipient address specified for {0} notification is invalid : {1}
Action: Check Workflow Notification Configuration. Ensure that Email/IM recipient address is valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10337: Invalid entry in workflow-notification-config.xml
Cause: Invalid configuration specified for {0}
Action: Please ensure that notification component is configured correctly

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10338: Incoming message could not be processed
Cause: Incoming message could not be processed
Action: Ensure that the incoming response message is not corrupted.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10339: Error while sending auto reply
Cause: Could not send {0} auto reply
Action: Internal Error. Ensure that the message being replied to is not corrupted.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10340: Error while Receiving response
Cause: Could not process received message
Action: Ensure that incoming accounts in human workflow Mailer and Email Driver match and are configured correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10341: Error while Sending test notification
Cause: Could not send test notification
Action: Ensure that human workflow mailer and underlying driver are configured correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10342: Could not send notification
Cause: Error while sending {0} notification
Action: Check configuration of underlying Channel specific driver.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10343: Error while creating notification content
Cause: Could not create notification content
Action: Ensure that the files being used for attachment exist and not corrupted.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10344: Could not send notification
Cause: Could not send {0} notification, since notification mode is set to {1}
Action: Ensure that Notification Mode in workflow-notification-config is set to either EMAIL or ALL to send email notifications. For rest of the channels it should be set to ALL

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10345: Error in Notification Service startup
Cause: Could not start notification service
Action: Failed to start notification service. This is a system error.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10346: Error in Notification Service shutdown
Cause: Could not shutdown notification service correctly
Action: Errors while notification service shutdown. This is a system error.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10347: Cannot send Notification to specified address
Cause: Cannot send {0} notification to {1} address. The address is being marked as 'invalid' and no further notification would be sent to this address.
Action: Make sure that : the address specified is correct; the Email/Gateway server is up and running. Once the problem is corrected, please remove the address from invalid address list using EM.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10348: Incoming message content is invalid
Cause: Incoming message could not be processed due to invalid content
Action: Please ensure that the response message is not corrupted; Actionable notifications should be responded from the same email account to which it was sent.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10349: No NID Placeholder
Cause: Incoming message content does not contain Notification ID placeholders
Action: Please ensure that the response message is not corrupted

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10350: Incoming message could not be processed
Cause: Incoming message {0} could not be processed
Action: Please ensure that Human-Workflow Mailer is correctly configured also ensure that the response message is not corrupted

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10351: Underlying SDPMESSAGING layer could not send notification.
Cause: Underlying SDPMESSAGING layer could not send {0} Notification(MessageId:{1}) to {2}.
Action: Possible causes : SDPMessaging Driver not configured; Invalid 'To' Address; Email server/Messaging gateway is down; using IP address as part of email id insted of domain name;

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10352: Actionable Email has been responded from a different account.
Cause: Actionable Email had been sent to {0}, but received response from {1}.
Action: Actionable notifications should be responded from the same email account to which it was sent.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10353: Could not register/un register/fetch spam sources
Cause: Could not register/un register/fetch spam sources: {0}
Action: Possible cause : Invalid address is being registered/unregistered

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10500: Illegal Action name
Cause: Illegal Action name "{0}"
Action: Unsupported action by name "{0}"

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10501: Illegal argument
Cause: Illegal argument
Action: This is because an unexpected value, possibly null, was passed as an argument. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10502: Could not get Application role grantees
Cause: Failed to get Grantees to Application role "{0}" for application identified by "{1}"
Action: Check if the application role exists and has grantees in the repository associated with the application. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10503: Could not get granted roles to Application role
Cause: Failed to get Granted roles to Application role "{0}" for application identified by "{1}"
Action: Check if the application role exists and has granted roles in the repository associated with the application. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10504: Identity "{0}" membership in group "{1}" in configuration "{2}" could not be checked.
Cause: Error in checking membership of identity "{0}" in group "{1}" in configuration "{2}".
Action: Please make sure that both the identity name and group name are valid and exist in the repository. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10505: Service "{0}" in configuration "{1}" could not be initialized.
Cause: Error in initializing service "{0}" in configuration "{1}".
Action: Please make sure that identity service configuration is well formed and correct. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10506: Cannot get roles
Cause: Cannot get roles for identity "{0}" through configuration "{1}"
Action: The underlying APIs threw an exception. Check if the repository is configured properly and available. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10507: Only SSO authentication allowed.
Cause: Only SSO based authentication is allowed.
Action: Refer workflow configurations to change this policy. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10508: Error invoking remote service method.
Cause: Error occurred while invoking the remote position service method "{0}" for id "{1}"
Action: Ensure that a remote position service provider is configured correctly, the service is accessible and is active. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10509: User not found
Cause: User "{0}" is not found in configuration "{1}"
Action: Check if the user exists in the repository specified by the configurations. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10510: Application role not found
Cause: Application role "{0}" could not be found for application identified by "{1}"
Action: Check if the application role exists in the repository associated with the application. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10511: Group not found
Cause: Group "{0}" is not found in configuration "{1}"
Action: Check if the group exists in the repository specified by the configurations. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10512: Cannot get application role "{0}" for application identified by "{1}"
Cause: Cannot get role "{0}" from configuration "{1}"
Action: Check if the application role exists in the repository associated with the application. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10513: Cannot get application roles from application identified by "{0}"
Cause: An error occured while getting application roles from application identified by "{0}"
Action: The underlying APIs threw an exception. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10514: Cannot get group
Cause: Cannot get group "{0}" for configuration "{1}"
Action: The underlying APIs threw an exception. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10515: Cannot get groups
Cause: An error occured while getting groups from configuration "{0}"
Action: The underlying APIs threw an exception. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10516: Cannot find user
Cause: An error occured while getting user "{0}" from configuration "{1}"
Action: Check if the user exists in the repository specified by the configurations. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10517: Cannot get users
Cause: An error occured while getting users from configuration "{0}"
Action: The underlying APIs threw an exception. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10518: Failed to load Identity Service Configuration
Cause: An error occured while loading configurations from "{0}"
Action: Ensure that the identity service configurations are well formed and correct. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10520: Invalid application role name
Cause: Invalid application role name "{0}"
Action: Specify a valid application role name. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10521: Invalid group name
Cause: Invalid group name "{0}"
Action: Specify a valid role name. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10522: Manager with title "{0}" not found.
Cause: No manager with title "{0}" in management chain for user "{1}" in configuration "{2}"
Action: Given title "{0}" was not found among management chain for specified user "{1}" in configuration "{2}"

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10523: Hierarchy Provider "{0}" could not be loaded correctly.
Cause: Error occured while loading configured hierarhcy provider "{0}", in the identity service configuration.
Action: Check the log file for erros, check hierarchy service provider "{0}" configurations and make sure provider service is accessible and functional.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10528: Identity Service Authentication failure
Cause: Identity Service Authentication failure
Action: Either the user name or password are incorrect. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10536: Identity service provider not found
Cause: Identity service provider not found
Action: Ensure that a provider corresponding to the operation being performed is configured. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10537: user locale not found
Cause: user locale not found
Action: Ensure that the user locale is passed while calling the operation. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10540: Cannot find specified user in management chain
Cause: Cannot find specified user "{0}" in management chain for user "{1}" in configuration "{2}"
Action: User "{0}" is not in management chain for user "{1}" in configuration "{2}".

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10541: Cannot find context "{0}" in JPS configuration
Cause: Cannot find context "{0}" in JPS configuration
Action: Ensure that the JPS configuration file is well formed and has the specified context. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10542: Cannot set context "{0}".
Cause: Cannot set context "{0}".
Action: Ensure that the JPS configuration file is well formed and has the specified context. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10543: Unsupported filter
Cause: Specified search filter is unsupported or contains error.
Action: Correct the search filter. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10546: Unsupported attribute
Cause: Attribute "{0}" is not supported
Action: Ensure that the attribute is not null. Refer to the documentation for supported attributes. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10551: Custom Identity Service class cannot be loaded
Cause: Identity Service cannot load "{0}" class
Action: Check whether the file "{0}" in the classpath. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10555: Identity Service Configuration error
Cause: Identity Service Configuration has error
Action: Please refer to the identity service configuration guidlines and correct the Identity Service configurations. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10557: Error in identity service XPath extension function ora:getManager
Cause: Error in executing identity service XPath extension function ora:getManager for user name "{0}" in configuration "{1}".
Action: Please make sure that the user name is valid and exists in the repository and is associated with a manager. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10558: Error in identity service XPath extension function ora:getUserProperty
Cause: Error in executing identity service XPath extension function ora:getUserProperty for property "{0}" for user name "{1}" for configuration "{2}".
Action: Please make sure that the user name is valid and exists in the repository. Also ensure that the property has been defined for the user. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10559: Error in identity service XPath extension function ora:getGroupProperty
Cause: Error in executing identity service XPath extension function ora:getGroupProperty for property "{0}" for group name "{1}" for configuration "{2}".
Action: Please make sure that the group name is valid and exists in the repository. Also ensure that the property has been defined for the group. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10560: Error in identity service XPath extension function ora:lookupUser
Cause: Error in executing identity service XPath extension function ora:lookupUser for user name "{0}" in configuration "{1}".
Action: Please make sure that the user name is valid and exists in the repository. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10561: Error in identity service XPath extension function ora:lookupGroup
Cause: Error in executing identity service XPath extension function ora:lookupGroup for group name "{0}" in configuration "{1}".
Action: Please make sure that the group name is valid and exists in the repository. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10562: Error in identity service XPath extension function ora:isUserInRole
Cause: Error in executing identity service XPath extension function ora:isUserInRole for user "{0}" and group "{1}" in configuration "{2}".
Action: Please make sure that both the user name and group name are valid and exist in the repository. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10563: Error in identity service XPath extension function ora:getReportees
Cause: Error in executing identity service XPath extension function ora:getReportees for user name "{0}" for configuration "{1}".
Action: Please make sure that the user name is valid and exists in the repository. Also ensure that reportees to this user exist. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10564: Error in identity service XPath extension function ora:getUsersInGroup
Cause: Error in executing identity service XPath extension function ora:getUsersInGroup for group name "{0}" in configuration "{1}".
Action: Please make sure that the group name is valid and exists in the repository. Also ensure that users have been enlisted as participants to this group. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10565: Error in identity service XPath extension function ora:getUserRoles
Cause: Error in executing identity service XPath extension function ora:getUserRoles for user name "{0}" in configuration "{1}".
Action: Please make sure that the user name is valid and exists in the repository. Also ensure that roles have been granted to this user. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10566: Error in identity service XPath extension function ora:getDefaultRealmName
Cause: Error in executing identity service XPath extension function ora:getDefaultRealmName.
Action: Ensure that a default configuration exists. Irrespective of the number of configurations, one must be defined as default. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10567: Error in identity service XPath extension function ora:getSupportedRealms
Cause: Error in executing identity service XPath extension function ora:getDefaultRealmName.
Action: Ensure that the configurations are correct. Please check the exception stack trace for the reasons. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10575: Provider is not defined in configuration.
Cause: Provider "{0}" is not defined in configuration "{1}".
Action: Configure provider in configuration file. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10576: Configuration already exists
Cause: Configuration "{0}" already exists.
Action: Two or more configurations have the same name. Specify a different name for the configurations. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10577: Default configuration is not defined
Cause: Default configuration is not defined in configuration file "{0}".
Action: Specify default configuration in the file "{0}". Irrespective of the number of configurations, one should always be marked as default. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10578: More than one default configurations are defined
Cause: More than default configurations are defined in configuration file "{0}".
Action: There can be only one dafault. Specify only one default configuration in configuration file "{0}". Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10579: Name is not defined for one of configurations
Cause: Name is not specified for one of configurations in configuration file "{0}".
Action: Specify name for each configuration if few configurations are defined in configuration file "{0}". Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10580: Identity Service Extension name is already defined earlier in the identity service configuration
Cause: Identity Service Extension name "{0}" is already defined earlier in the identity service configuration.
Action: Make sure the extension name is unique and defined only once in the identity service configuration file. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10581: Service Provider {0} invocation error
Cause: Service Provider name "{0}" could not invoke method {1}.
Action: This errors occurs when service provider {0} is not avalable or not configured in the identity configuration file.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10584: Identity Service wsif error.
Cause: {0} has wsif error in method {1} for soap message: "{2}".
Action: Ensure that the soap message is properly formed and has all necessary attributes and elements. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10585: Service error.
Cause: Internal Error; Service error occurs in {0} in method {1}.
Action: Refer to the log file that is configured for oracle.soa.services.identity for more details on this error and contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10586: Could not get grantees for "{0}" in configuration "{1}".
Cause: Error in getting grantees for "{0}" in configuration "{1}".
Action: Ensure that a group with the given name exists and has grantees. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10587: Error in getting owners for "{0}" in configuration "{1}".
Cause: Error occured in getting owners for "{0}" in configuration "{1}".
Action: Ensure that the group name is valid and has associated owners. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10588: Error in getting owned groups for "{0}" in configuration "{1}".
Cause: Error occured in getting owned groups for "{0}" in configuration "{1}".
Action: Ensure that the identity name is valid and owns groups. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10589: Manager "{0}" not found for user "{1}" in configuration "{2}".
Cause: Manager with name "{0}" was not found for user "{1}" in configuration "{2}".
Action: Ensure that a user with the given name exists and is a manager for the given user. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10590: Manager name could not be resolved for "{0}" in configuration "{1}".
Cause: Error in resolving manager name for user "{0}" in configuration "{1}".
Action: Ensure that a user with the given name exists and has a manager. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10591: Could not get reportees for "{0}" in configuration "{1}".
Cause: Error in getting reportees for "{0}" in configuration "{1}".
Action: Ensure that a user with the given name exists and has reportees. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10592: Identity Service soap error.
Cause: {0} encountered soap error in method {1} for with fault "{2}".
Action: Ensure that the soap message is properly formed and has all necessary attributes and elements. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10593: Cannot find application "{0}".
Cause: Cannot find specified application name "{0}" in policy store.
Action: Check if the specified application "{0}" exists in policy store. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10597: Attempt to execute privileged action.
Cause: An attempt to execute a privileged action was made.
Action: Ensure that the codebase being used has the necessary permissions and privileges. If not, grant the same in the application's policy file. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10598: Identity "{0}" in configuration "{1}" is not of a supported type.
Cause: Unsupported identity type for identity "{0}" in configuration "{1}".
Action: Ensure that a identity with the given name exists and is of a supported type. Refer to the documnentation for all supported identity types. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10599: Role name "{0}" in configuration "{1}" could not be resolved.
Cause: Error in resolving role name "{0}" in configuration "{1}".
Action: Ensure that a role with the given name exists. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10600: Reports Error.
Cause: A problem occurred while processing reports data. {0}
Action: Please examine the log file to determine the problem.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10601: JMS connection factory lookup failed
Cause: The JMS connection factory lookup failed. The related reporting data will not be published Please ensure the JNDI name {0) is valid.
Action: Please verify the JMS configuration.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10602: JMS connection setup failed
Cause: A problem occurred while setting up a connection to the JMS Destination {0} using the connection factory {1}.
Action: Please verify the JMS configuration as well as the error to determine the problem.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10603: JMS publish failed
Cause: An error occurred while publishing reporting data to the JMS destination "{0}".
Action: Please verify the JMS destination is valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10604: JMS destination lookup failed
Cause: The JMS destination lookup failed. The related reporting data will not be published Please ensure the JNDI name {0) is valid.
Action: Please configure the JMS Destination or correct its JNDI name.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10605: Data Publisher failed.
Cause: The Reporting Data Publisher {0} of type {1} failed.
Action: Please examine the log file for more details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10606: Invalid Variable Target.
Cause: The variable target {0} used in sensor {1} is invalid.
Action: Please make sure the variable target is correct by validating the variable name as well as the part and xpath query if any was provided.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10607: Sensor Initialization Error.
Cause: An error occurred while initializing the {0} sensor.
Action: Please correct the problem and reinitialize the business process.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10608: Sensor Data Capture Error.
Cause: An error occurred while gathering data for the {0} sensor. The related reporting data might not have been published.
Action: Please examine the log file and correct the problem.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10609: Invalid Adapter Namespace.
Cause: An error occurred while gathering reporting data for the {0} adapter sensor. The {1} namespace is not a recognized adapter namespace.
Action: Please provide a valid header variable that is defined in the appropriate namespace.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10610: Invalid Adapter Header Variable.
Cause: An error occurred while gathering reporting data for the {0} adapter sensor. The header variable {1} could not be found in the BPEL process definition.
Action: Please ensure the header variable provided in the sensor definition file exists in the BPEL process.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10611: JMS connection cleanup failed
Cause: A problem occurred while releasing the JNDI resources used to publish to the destination {0}.
Action: Please verify the JMS configuration as well as the error to determine the problem.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10612: Data Router failed.
Cause: The Reporting Data Publisher {0} of type {1} failed.
Action: Please examine the log file for more details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10613: Creation of Sensor Registry failed.
Cause: Creation of the Sensor Registry failed.
Action: Please examine the log file for more details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10614: Creation of Reports Schema Publisher failed.
Cause: Creation of the Reports Schema Publisherfailed.
Action: Please examine the log file for more details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10615: Load of sensors into Sensor Registry failed.
Cause: The Sensor Registry failed to load sensors for process {0}-{1}.
Action: Please check the sensor definitions and examine the log file for more details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10616: Import of sensors failed.
Cause: The Sensor Registry failed to import sensors for process {0}-{1}.
Action: Please check the sensor definitions and examine the log file for more details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10617: Import of sensor actons failed.
Cause: The Sensor Registry failed to import sensor actions for process {0}-{1}.
Action: Please check the sensor action definitions and examine the log file for more details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10618: Import of SLA's failed.
Cause: The Sensor Registry failed to import SLA's for process {0}-{1}.
Action: Please check the SLA properties in the deployment descriptor and examine the log file for more details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10619: Sensor validation failed.
Cause: The Sensor Registry failed to validate the sensor {2} for process {0}-{1}.
Action: Please revisit the definition of the sensor and examine the log file for more details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10620: Sensor Action validation failed.
Cause: The Sensor Registry failed to validate the sensor action {2} for process {0}-{1}.
Action: Please revisit the definition of the sensor action and examine the log file for more details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10621: Data publisher creation failed.
Cause: The Sensor Agency encountered an error while trying to instantiate {0}.
Action: Please ensure the specified Data Publisher class and all of its dependencies exist in the system or process classpath.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10622: Sensors not supported.
Cause: Sensors are not supported on this application server platform.
Action: If sensor functionality is required, please switch to a supported platform.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10623: Sensors not supported.
Cause: Sensors are not supported on this database platform.
Action: If sensor functionality is required, please switch to a supported platform.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10700: Infrastructure services not enabled
Cause: The infrastructure feature for the domain has not been enabled.
Action: This is an irrecoverable error with installation.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10701: Server connection failure
Cause: Failed to connect to the PCBPEL server.
Action: Please check that the PCBPEL server is running.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10702: PCBPEL Server domain authentication enabled.
Cause: PCBPEL Server domain authentication has been enabled, need to turn it off.
Action: Please check if PCBPEL server has domain authentication enabled. Please look for property "domain-auth-enabled" in the file collaxa-config.xml and turn it off.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10703: BPEL Archive could not be found at the specified location.
Cause: BPEL Archive name or location is incorrect.
Action: Please check the name of the BPEL archive and its location.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10704: jndi.properties could not be found in the classpath.
Cause: jndi.properties could not be found in the classpath.
Action: Please ensure that jndi.properties is in the classpath.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10705: Authentication failure.
Cause: The user name password combination is not authenticated for deployment.{0}
Action: Please ensure that the password is correct and user has deployment previleges.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10706: Server Internal Error.
Cause: Server error.{0}
Action: Please report this error to the administrator.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10707: Connection to server refused
Cause: Server connection refused.
Action: Please ensure that the server is up and running.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10708: Problem with Network Connection to server
Cause: The network connection to the server is slow. The request has already been sent to the server. Please check the console to see if the process is already deployed.
Action: The request was sent to the server. The response from server is taking longer than expected. Please check the console to see if the process is already deployed.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-10709: Error while deploying payload jsp
Cause: Deploying payload jsp on paltform {0} not supported
Action: Please ensure that server platform is supported

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30001: Error in reading routing slip
Cause: Error while reading routing slip {0}. This routing slip is used by workflow {1}
Action: Make sure that the routing slip is available at the specified URL.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30002: Error in evaluating routing slip
Cause: Error while evaluating the routing slip {0}. This routing slip is used by workflow {1}
Action: Check the underlying exception and correct the error in the routing slip.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30003: Invalid routing slip
Cause: The routing slip at {0} does not conform to the routing slip XML schema definition. The errors are {1}
Action: Make sure that the routing slip conforms to the routing slip XML schema definition.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30004: Error in validating routing slip
Cause: The routing slip at {0} could not be validated against the routing slip XML schema definition
Action: Make sure that the routing slip is available at the specified URL.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30005: Error in setting task attributes
Cause: The task attribute {2} could not be set for the task {0}. The task belongs to the workflow {1}
Action: This error is likely because of invalid user/group being set as {2}. Make sure that the user/group is valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30006: Error in getting manager of user
Cause: The manager of user {2} could not be retrieved for the task {0}. The task belongs to the workflow {1}
Action: Make sure that user {2} is valid and that the manager for user {2} is defined in the user directory.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30007: Error in creating task from WSIF Java Web Services message
Cause: The task object could not be created from the message passed to Web Services
Action: Check the Web Service input for correctness. The input could also be validated against XML schema definition that describes the operation input.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30008: Error in creating parameters from WSIF Java Web Services message
Cause: The {0} could not be created because expected element {1} is not be found in the element {2} in the parameter passed to Web Services
Action: Check the Web Service input for correctness. The input could also be validated against XML schema definition that describes the operation input.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30009: Parameters in Web Services message is invalid
Cause: The parameter {0} is invalid as expected type is {1}, but received value {2} in the parameter passed to WSIF Java Web Services
Action: Check the Web Service input for correctness. The input could also be validated against XML schema definition that describes the operation input.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30010: Error in creating reply message for Web Services
Cause: Error in creating reply message for Web Services
Action: The Web Service input could be invalid causing this exception. Check the Web Service input for correctness. The input could also be validated against XML schema definition that describes the operation input. It being valid, this is a system error.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30011: Invalid workflow configuration
Cause: The workflow configuration at {0} could not be read. The workflow configuration is associated with workflow {1}
Action: Make sure that the workflow configuration is available at the specified URL and that it is a valid XML document.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30012: Invalid workflow configuration
Cause: The workflow configuration at {0} does not conform to the workflow configuration XML schema definition. The workflow configuration is associated with workflow {1}. The errors are {2}
Action: Make sure that the workflow configuration conforms to the workflow configuration XML schema definition.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30013: Error in validating workflow configuration
Cause: The workflow configuration at {0} could not be validated against the workflow configuration XML schema definition. The workflow configuration is associated with workflow {1}
Action: Make sure that the workflow configuration is available at the specified URL. If available check the underlying exception and correct the error.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30014: Error in retrieving previous approvers of task
Cause: The previous approvers of task {0} could not be retrieved. The task is associated with workflow {1}
Action: Make sure that the task for which the previous approvers are retreived is valid. It being valid, this is a system error.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30015: Error in posting message to BPEL process instance
Cause: Error in posting message to BPEL process instance {1} for callback operation {2}. The task is associated with workflow {0}
Action: This could be caused if the BPEL instance is terminated. It is is not, this is possibly a system error.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30016: Error in invoking routing slip callbacks
Cause: Error in invoking routing slip Java callback {3} for task {1}. The task is associated with workflow {0}
Action: Make sure that the routing slip callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30017: Invalid task definition
Cause: The task definition at {0} could not be read. The task definition is associated with workflow {1}
Action: Make sure that the task definition is available at the specified URL and that it is a valid XML document.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30018: Invalid task definition
Cause: The task definition at {0} does not conform to the task definition XML schema definition. The task definition is associated with workflow {1}. The errors are {2}
Action: Make sure that the task definition conforms to the task definition XML schema definition.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30019: Error in validating task definition
Cause: The task definition at {0} could not be validated against the task definition XML schema definition. The task definition is associated with workflow {1}
Action: Make sure that the task definition is available at the specified URL and that it is a valid XML document.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30020: Invalid workflow task display configuration
Cause: The workflow task display configuration at {0} could not be read. The workflow task display configuration is associated with workflow {1}
Action: Make sure that the workflow task display configuration is available at the specified URL and that it is a valid XML document.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30021: Invalid workflow task display configuration
Cause: The workflow task display configuration at {0} does not conform to the workflow task display configuration XML schema definition. The workflow task display configuration is associated with workflow {1}. The errors are {2}
Action: Make sure that the workflow task display configuration conforms to the workflow task display configuration XML schema definition.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30022: Error in validating workflow task display configuration
Cause: The workflow task display configuration at {0} could not be validated against the workflow task display configuration XML schema definition. The workflow task display configuration is associated with workflow {1}
Action: Make sure that the workflow task display configuration is available at {1} and that it conforms to the workflow task display configuration XML schema definition.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30023: Internal workflow error
Cause: An internal workflow error occured
Action: Refer to the log file that is configured for oracle.soa.services.workflow.* for more details on this error and contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30024: The task is already modified
Cause: The task was modified before the current action could be performed.
Action: Refresh the task and perform the action again if the action is still relevant on the refreshed task.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30025: Error unmarshalling from org.w3c.dom.Element to JAXB.
Cause: Internal Error : Attempt to unmarshall element {0} using JAXB context {1} resulted in error: {2}
Action: Refer to the log file that is configured for oracle.soa.services.workflow.* for more details on this error and contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30026: Error creating soap message.
Cause: Error in creating soap message during Web service invocation of operation {1} in {0}
Action: Refer to the log file that is configured for oracle.soa.services.workflow.* for more details on this error and contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30028: Invalid configuration file workflow-config.xml
Cause: The configuration file workflow-config.xml not be read.
Action: Make sure that the configuration file workflow-config.xml is available and is a valid XML document.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30029: Error in invoking task service
Cause: An client side error occured in invoking the task service.
Action: Verify that the connection information of the server is correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30030: Error in invoking task service
Cause: An client side error occured in invoking the task service operation {0}.
Action: Verify that the connection information of the server is correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30031: Failed to query flexfield mappings
Cause: Task metadata service was unable to query flexfield mappings for task definition: {0}
Action: Check the underlying error. Verify that the workflow datasource is correctly configured, and that database server is available.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30032: Invalid task definition lookup
Cause: There is no task definition associated with the task definition ID {0}
Action: Verify the that the task definition ID is vaild.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30033: Invalid task metadata service invocation
Cause: Task metadata service operation was invoked with empty task definition ID.
Action: Make sure that the operation is invoked with a valid task definition ID

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30034: Invalid task display region parameter value
Cause: The task display region parameter value {0} is invalid when applied to task {1}.
Action: Make sure that the task display region parameter value is correct if it is an XPath expression

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30035: Push back not supported
Cause: Push back is not supported for the task {0} as there are no more users to push back the task to.
Action: This is an invalid operation on the task.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30036: Invalid action on workflow task or user does not have privilege to perform this action
Cause: Action {0} on task {1} cannot be performed by {2}
Action: Make sure that the action is valid with respect to the current state of the task or ensure that the user has privilege to perform this action on the workflow task

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30037: Error in invoking task metadata service
Cause: An client side error occured in invoking the task metadata service.
Action: Verify that the connection information of the server is correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30038: Error in evaluating task service XPath extension function
Cause: Error in evaluating task service XPath extension function {1} against task {1}
Action: It is possible that the extension function is not valid against the particular task. Check the error to correct the problem.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30039: Error in routing slip
Cause: The type of the first participant in the routing slip is expected to be Participant, but it is {1}. The routing slip is associated with task {0}
Action: Check the routing slip and correct the error.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30040: Error in routing slip
Cause: Adhoc routing can be performed only when the isAdhocSupported flag is set to true in the routing slip participants or the current participant is adhoc, but it is {1}. The routing slip is associated with task {0}
Action: Adhoc routing is an invalid action at the current state of the task.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30043: Error in evaluating workflow service XPath extension function
Cause: Error in evaluating task service XPath extension function {1}
Action: Check the error stack and fix the cause of the error.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30044: Error in workflow service Web service operation invocation
Cause: Error in workflow service Web service operation invocation. The error is {0}.
Action: Verify that the SOAP connection information for the server is correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30045: Error in invoking workflow state machine decision service.
Cause: Error occured when invoking workflow routing state machine decisions service {0}. The error is {1}.
Action: Check the error underlying error. Verfiy that the composite and workflow componentType are correctly configured, and that the correct decisionServiceComponentName is specified in the workflow definition.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30046: Error in routing slip
Cause: The expiration specified in the routing slip could not be evaluated. The error is {0}. The routing slip is associated with the task definition {1}
Action: Make sure that the expiration duration is specified correctly. The value should conform to XML duration specifications

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30047: Error in routing slip
Cause: Error in evaluating parameter {0} in the routing slip. The error is {1}. The routing slip is associated with the task definition {2}
Action: Make sure that the parameter {0} is specified correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30048: Error in routing slip
Cause: An error occured during evaluating escalation policy in the routing slip. The error is {0}. The routing slip is associated with the task definition {1}
Action: Make sure that the escalation policy is specified correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30049: Error in routing slip
Cause: The task is assigned to an invalid user {0} in realm {1}. The routing slip is associated with the task definition {2}
Action: Verify that the user is specified correctly in the routing slip in the task definition

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30050: Error in routing slip
Cause: The task is assigned to an invalid group {0} in realm {1}. The routing slip is associated with the task definition {2}
Action: Verify that the group is specified correctly in the routing slip in the task definition

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30051: Error in routing slip
Cause: An error occured during evaluating renewal policy in the routing slip. The error is {0}. The routing slip is associated with the task definition {1}
Action: Make sure that the renewal policy is specified correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30052: Error in routing slip
Cause: An error occured in evaluating the assignees of the task from the routing slip for participant {0}. The error is {1}. The routing slip is associated with the task definition {2}
Action: Check the routing slip in the task definition and correct the error.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30053: System error in evaluating routing slip
Cause: A system error occured in evaluating the routing slip. The error is {0}. The routing slip is associated with the task definition {1}
Action: Refer to the log file that is configured for oracle.soa.services.workflow.task for more details on this error and contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30054: Error in evaluating assignment service in routing slip
Cause: Cannot instantiate assignment service {0}. The error is {1}. The assignment service is used in the routing slip that is associated with the task definition {2}
Action: Check the routing slip and correct the error. Make sure that the assignment service is available in the classpath of the soa-infra application.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30055: Error in evaluating assignment service in routing slip
Cause: Cannot create property bag for assignment service. The error is {0}. The assignment service is used in the routing slip that is associated with the task definition {1}
Action: Check the routing slip and correct the error in specifying the properties for the assignment service.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30056: Error in escalating the task on expiration
Cause: The task has expired and the system could not compute the management chain from user {0} upto levels {1} upto title {2} to identify the next user to escalate the task to
Action: Make sure that the escalation policy is specified correctly. Also verify that the users are seeded correctly to compute the management chain.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30057: Error in evaluating management chain participant
Cause: Could not compute the management chain from user {0} upto levels {1} upto title {2}. The management chian is used in the routing slip that is associated with the task definition {3}
Action: Verify that the users are seeded correctly to compute the management chain.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30058: Error in state machine rules return parameter
Cause: The forwarding rule specifies goto, but does not specify the logical name of the participant to goto. The task is associated with the task definition {0}
Action: Check the state machine rule definitions. Ensure that the rules are setting a participant logical name in the GOTO action.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30059: Error in forwarding rules return parameter
Cause: The forwarding rule specifies goto, but the logical name of the participant {0} to goto is not a valid name. The task is associated with the task definition {0}
Action: Check the state machine rule definitions. Ensure that the rules aare stting a valid logical participant name in the GOTO action.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30060: Error in task assignment rules evaluation
Cause: Error in task assignment rules evaluation for user {0}. The error is {1}
Action: Make sure that the rules specified for user {0} are valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30061: Cyclic assignment during task assignment rules evaluation
Cause: During task assignment rules evaluation, there is a cyclic assignment involving user {0}.
Action: Correct the assignment rules to avoid this error.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30062: Error in task assignment rules evaluation
Cause: Error in task assignment rules evaluation for group {0}. The error is {1}
Action: Make sure that the rules specified for group {0} are valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30063: Cyclic assignment during task assignment rules evaluation
Cause: During task assignment rules evaluation, there is a cyclic assignment involving group {0}.
Action: Correct the assignment rules to avoid this error.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30064: Error in routing slip
Cause: The task is assigned to an invalid application role {0} in application context {1}. The routing slip is associated with the task definition {2}
Action: Verify that the application role is specified correctly in the routing slip in the task definition

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30065: Error in task definition
Cause: Error in evaluating parameter {0} in the task definition. The error is {1}. The task definition {2}
Action: Make sure that the parameter {0} is specified correctly in the task definition.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30066: Invalid arguments to requestInfoForTask operation
Cause: Invalid arguments to requestInfoForTask operation. The reapproval assignees parameter must contain one or more valid user, group or role.
Action: Correct the error in the client usage.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30067: Invalid access to task
Cause: The user does not have access to the task.
Action: Check that the task is being accessed in an authenticated context and that you are involved in this task in some manner.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30068: Invalid task definition ID or namespace
Cause: There is no task definition with the provided ID {0}. This ID is either the ID of the task definition or the namespace of the task definition
Action: Verify the that the task definition ID is vaild.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30069: Task definition not found using namespace
Cause: There is no active SCA composite with the referenced task definition. The provided task definition namespace is {0}
Action: Verify the that the composite containing the task definition is active.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30070: Assignee Time Distribution Statistic Service Internal error.
Cause: An internal error occurred in the Assignee Time Distribution Statistic Service. Task assignment statistic is not recorded for {0} for the operation {1}. This may lead to loss of some Task assignment statistic data
Action: Check the underlying exception and correct the error. Contact Oracle Support Services if the error persists.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30071: No workflow admin user seeded
Cause: There must be atleast one workflow admin user seeded in the system.
Action: Seed an workflow admin user or grant the workflow admin role to an existing user.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30072: Task owner user not seeded
Cause: Task owner {0} is not found in realm {1}. This task is associated with task definition {2}
Action: Either set a seeded owner or seed this owner who is not found.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30073: Task owner group not seeded
Cause: Task owner {0} is not found in realm {1}. This task is associated with task definition {2}
Action: Either set a seeded owner or seed this owner who is not found.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30074: There is no user to escalate the task to
Cause: There is no user to escalate the task to. The task is assigned to user {0}. This task is associated with task definition {1}
Action: Ensure that this user has a manager to escalate the task to.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30075: Invalid task attachment name
Cause: The task attachment {0} does not exist
Action: Ensure that the task attachment name is valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30076: ToDo task cannot be created as a sub task for a task that is not in the assigned state
Cause: Parent task {0} is not assigned. ToDo task cannot be created as a sub task for a task that is not in the assigned state.
Action: Ensure that the ToDo task is created for an assigned task.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30077: Error in invoking Notification callbacks
Cause: Error in invoking routing slip Java callback {3} for task {1}. The task is associated with workflow {0}
Action: Make sure that the Notification callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30078: Error in evaluating the restricted assignment service in routing slip
Cause: Cannot instantiate restricted assignment service {0}. The error is {1}. The restricted assignment service is used in the routing slip that is associated with the task definition {2}
Action: Check the routing slip and correct the error. Make sure that the restricted assignment service is available in the classpath of the soa-infra application.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30079: Attempt to reassign/route to an invalid assignee.
Cause: The assignee {0} in realm {1} for task definition {2} is not permitted as per the restricted assignment callback configured by the administrator.}
Action: Check the routing slip and correct the error. Make sure that restricted assignees are not used in the task definition.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30080: Task owner role not seeded
Cause: Task owner {0} is not found in application {1} and realm {2}. This task is associated with task definition {3}
Action: Either set a seeded owner or seed this owner who is not found.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30081: Workflow Service Engine callback to SOA mesh failed.
Cause: Callback operation {0} from {1} to {2} failed with error: {3}
Action: Check the underlying exception. Ensure that the SOA composite is configured correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30082: WorkflowServiceEngine request to another component failed.
Cause: Request operation {0} from {1} to {2} failed with Business Fault: {3}
Action: Check the underlying fault. Check target SOA component for cause.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30083: WorkflowServiceEngine request to SOA mesh failed.
Cause: Request operation {0} from {1} to {2} failed with error: {3}
Action: Check the underlying exception. Ensure that the SOA composite is configured correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30085: Missing task metadata identifiers in task object.
Cause: Task metadata corresponding to a task is identified by either the taskDefinitionId or taskDefinitionURI (deprecated in 11). Atleast one of those task elements should be set.
Action: Set either the taskDefinitionId or taskDefinitionURI in the task instance.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30086: No duration specified.
Cause: Invalid task duration: {0}.
Action: Specify a valid duration.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30087: Operation not supported in disconnected mode.
Cause: The attempted operation cannot be performed whilst disconnected from the server.
Action: Connect to the server before attempting the operation.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30088: No task definitions found matching specified namespace and version.
Cause: No task definitions found with task definition namespace {0} and composite version {1}.
Action: Check that the specified task definition namespace and composite version are correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30089: No active composite found corresponding to specified namespace.
Cause: No active composite found containing a task component with definition namespace of {0}.
Action: Specify a composite version to query by, or make a composite version active.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30090: Can not compute management chain list.
Cause: The management chain can not be completely computed because the starting point in the management chain is not a single user. Management chain can not be computed from group(s), application role(s) and/or list of users. This exception is related to task definition {0}.
Action: Correct the errors in workflow process modeling or the rule that returned the management chain list parameters.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30091: Can not restart the task
Cause: Can not restart the task {0} in {1} state either because it is not a root task or the state is invalid for restart
Action: Check the error stack and fix the cause of the error. Contact Oracle Support Services if error the error persists.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30092: Error in invoking attachment callback
Cause: Error in invoking attachment callback {2} for task {1}. The task is associated with workflow {0}
Action: Make sure that the attachment callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30093: Error in invoking comment callback
Cause: Error in invoking comment callback {2} for task {1}. The task is associated with workflow {0}
Action: Make sure that the comment callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30094: Bulk update is not allowed for this Task.
Cause: This task expects the user to view task details before acting on it.
Action: Make sure that the task is approved/rejected from task details page. Also ensure that TaskService API which takes task Object as input is used instead of the API which takes taskID as input.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30095: User comments are expected for this Task.
Cause: This task expects the user to provide comments while acting on it.
Action: Make sure that the comments are provided while acting on this task.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30096: Can not reevaluate the task.
Cause: This task {0} does not belongs to a sequential or parallel participant.
Action: Check the error stack and fix the cause of the error. Contact Oracle Support Services if the error persists.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30097: Routing slip can not be reevaluated.
Cause: Current routing slip participant for the task {0} is not generated by a list builder.
Action: This task can not be reevaluated. Make sure the participant is generated using List builder.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30098: Error in task action validation
Cause: Error in validation task action {2} for task {1}.The task definition is associated with workflow {0}. The error(s) is/are: {3}
Action: Make sure the validation errors are corrected before invoking the task action.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30099: Error in invoking task validation callbacks
Cause: Error in invoking task validation Java callback {2} for task {1}. The task is associated with workflow {0}
Action: Make sure that the task validation callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30100: Error in setting Task Sequence Changes
Cause: Task has been modified. Mismatch on saving ad hoc changes for task with correlation Id {0}
Action: Refresh list to get current list of assignees and redo the changes.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30101: Invalid attribute label for flexfield mapping defined in task definition.
Cause: No attribute label named {0} for flexfield attribute {1} exists.
Action: Create an appropriate attribute label, or specify a different label in the task definition.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30102: Error in routing slip
Cause: The task is assigned to an invalid position {0} in application context {1}. The routing slip is associated with the task definition {2}
Action: Verify that the position is specified correctly in the routing slip in the task definition

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30103: Ruleset didn't return any results.
Cause: Ruleset {0} didn't return any results.
Action: Model the ruleset so that it returns a list builder specification.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30104: Ruleset returned different types of list builders.
Cause: Ruleset {0} returned different types of list builders.
Action: Ruleset results should all be of the same list builder type. Correct the ruleset.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30105: Ruleset returned unexpected list builder type.
Cause: Ruleset {0} returned list builder of type {2} when list builder of type {1} was expected.
Action: Correct the ruleset.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30106: Error setting starting point implicitly.
Cause: Starting Point not specified and Task Creator is same as UptoApprover: {0}
Action: Set the starting point explicitly to some one below the Upto Approver.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30107: Error fetching manager list using Hierarchy Provider.
Cause: Failed to walk up the hierarchy for principal: {0}
Action: Check Starting Point/Task Creator and Upto Approver values and Hierarchy Provider setup.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30108: Error NULL Hierarchy Principal provided.
Cause: Failed to fetch jobLevel for principal: NULL
Action: Check Hierarchy Provider setup.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30109: Error fetching jobLevel using Hierarchy Provider.
Cause: Failed to fetch jobLevel for principal: {0}
Action: Check Hierarchy Provider setup.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30110: Error walking up Hierarchy.
Cause: Failed to fetch upto approver for principal: {0}
Action: Check UptoApprover value in List Builder Specifications.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30111: Invalid user.
Cause: The task is assigned to an invalid user {0} in realm {1}.
Action: Assign to a valid user.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30112: Invalid group.
Cause: The task is assigned to an invalid group {0} in realm {1}
Action: Assign to a valid group.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30113: Invalid application role.
Cause: The task is assigned to an invalid application role {0} in application context {1}.
Action: Assign to a valid application role.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30114: Invalid position.
Cause: The task is assigned to an invalid application role {0} in application context {1}.
Action: Assign to a valid position.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30115: Error in invoking document callback
Cause: Error in invoking document callback {2} for task {1}. The task is associated with workflow {0}
Action: Make sure that the document callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30116: Invalid value of Levels.
Cause: The levels constraint for the Supervisory List Builder is not a postive integer: {0}
Action: Assign to a positive number for the levels parameter in the Supervisory List Builder Specification.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30117: Invalid value of Levels.
Cause: Both AtLeast and AtMost constraints for Job Level List Builder are not postive integers:, At Least {0}, At Most: {1}
Action: Assign positive integer values to one or both as required.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30118: Invalid value of Levels.
Cause: Both AtLeast and AtMost constraints for Position List Builder are not postive integers:, At Least {0}, At Most: {1}
Action: Assign positive integer values to one or both as required.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30119: Partial task update is not allowed
Cause: The task being updated is a partial task that was retrieved using query APIs. Such partial tasks cannot be directly used for update.
Action: Obtain the complete tasks using getTaskDetailsById before updating it.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30120: Invalid task document name
Cause: The task document {0} does not exist
Action: Ensure that the task document name is valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30121: Error in invoking document callback
Cause: Error in invoking document callback {2} for task {1}. The task is associated with workflow {0}
Action: Make sure that the document callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30122: Error while querying task document
Cause: Error while querying task document {0} for task {1} with version{2}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30123: Error while deploying task metadata.
Cause: The task namespace {0} is already used as a template namespace.
Action: Check if the project you are deploying now is a template project. Please avoid deploying template projects.Please use a different namespace for the task definition to fix the problem or set the suffixNamespace flag to true.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30124: Error while deploying task metadata.
Cause: the template namespace {0} is already in use as a task namespace
Action: Check if a template project with namespace {0} was deployed earlier. Please avoid deploying template projects. Please use a different namespace for the current task definition to fix the problem.The task flow associated with the template project will not work with this project anymore if the namespace is changed.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30125: Attachment already exists.
Cause: Process attachment names are unique. Please delete the existing attachment with the same name and then try to add it.
Action: To add the attachment with the same name, delete the existing attachment and upload again

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30126: Position provider invalid or cont available.
Cause: Position provider could not be loaded, position list builder could not be used.
Action: Unable to load the position provider, please check the position provider configuration and make sure it is valid. Position list builder uses provider to get the hierarchy.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30251: Error while querying workflow task display
Cause: Error while querying workflow task display based on task metadata and application name
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30252: Error while inserting workflow task display
Cause: Error while inserting workflow task display
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30253: Error while updating workflow task display
Cause: Error while updating workflow task display.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30254: Error while deleting workflow task display
Cause: Error while deleting workflow task display.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30257: Error while Querying workflow task metadata
Cause: Error while Querying workflow task metadata
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30258: Error while inserting workflow task metadata
Cause: Error while inserting workflow task metadata
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30259: Error while updating workflow task metadata
Cause: Error while updating workflow task metadata {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30260: Error while deleting workflow task metadata
Cause: Error while deleting workflow task metadata {0}
Action: Check the underlying exception and the database connection information.If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30261: The task namespace {0} is already in use by the task component {1}.
Cause: Task component target namespaces must be unique.
Action: Specify a different target namespace for this task component.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30265: Error while querying users which are on vacation
Cause: Error while querying users which are on vacation
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30266: Error while querying user vacation information
Cause: Error while querying user {0} vacation information
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30267: Error while inserting user vacation information
Cause: Error while inserting user {0} vacation information
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30268: Error while updating user vacation information
Cause: Error while updating user {0} vacation information
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30269: Error while deleting user vacation information
Cause: Error while deleting user {0} vacation information
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30274: Error while querying workflow message attributes
Cause: Error while querying workflow message attributes for task {0} with version {1}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30275: Error while querying workflow task history
Cause: Error while querying workflow task history for task {0} with version{1}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30276: Error while querying workflow task history
Cause: Error while querying workflow task history for task {0} with version{1}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30277: Error while querying task attachment
Cause: Error while querying task attachment {0} for task {1} with version{2}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30278: Error while inserting task
Cause: Error while inserting task {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30279: Error while locking the task during update
Cause: Error while locking the task {0} during update
Action: The task is being updated by another user, merge and update the task later

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30280: Error while inserting task payload
Cause: Error while inserting task payload {0} for task {1}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30281: Error while updating task payload
Cause: Error while updating task payload {0} for task {1}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30282: Error while deleting data
Cause: Error while deleting data from table {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30283: Error while querying task user comments
Cause: Error while querying task user comments for task {0} with version{1}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30284: Error while querying task composite created time
Cause: Error while querying task composite created time for task {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30291: Error while inserting task routing slip
Cause: Error while inserting task {1} routing slip
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30292: Error while locking the routing slip during update
Cause: Error while locking the routing slip during updateof routing slip for task {0}
Action: The task is being updated by another user, merge and update the task later

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30293: Attempt to update already deleted routing slip
Cause: Attempt to update already deleted routing slip for task {0}
Action: Refresh the task list by a new query.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30294: Error while updating routing slip
Cause: Error while updating routing slip for task {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30295: Error while querying routing slip
Cause: Error while querying routing slip for task {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30296: Error while deleting routing slip
Cause: Error while deleting routing slip for task {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30297: Error while initializing persistency service
Cause: Error while initializing persistency service
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30298: Error during persistency service commit
Cause: Error during persistency service commit
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30299: Error during persistency service rollback
Cause: Error during persistency service rollback
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30300: Error while closing persistency service
Cause: Error while closing persistency service
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30301: Error while creating prepared statement in persistency service
Cause: Error while creating prepared statement for {0} in persistency service
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30302: Invalid join operator
Cause: Invalid join operator {0}
Action: Change the operator in the given predicate.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30303: Predicate join columns are null
Cause: Predicate join columns are null
Action: Specify valid, non null, join columns for the given prediate.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30304: Error while joining columns of different types in predicate
Cause: Error while joining columns of different types in predicate
Action: Joined columns are of different type, verify the types of columns in the predicate.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30305: Invalid value type in predicate
Cause: Invalid value type {0} in predicate
Action: Unrecognized value type specified in the predicate, pass the appropriate value type for the column.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30306: Transaction is open
Cause: Transaction is open
Action: Close the current transaction and then open a new one.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30307: Transaction is open
Cause: Transaction is open
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30308: Transaction is close
Cause: Transaction is close
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30312: Error while creating attribute label map
Cause: Error while creating attribute label map
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30313: Error while updating attribute label map
Cause: Error while updating attribute label map for {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30314: Error while deleting attribute label map
Cause: Error while deleting attribute label map for {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30315: Error while querying attribute label map
Cause: Error while querying attribute label map
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30316: Error while creating attribute usages
Cause: Error while creating attribute label usages for AttributeLabel type {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30317: Error while deleting attribute usages
Cause: Error while deleting attribute label usages for AttributeLabel type {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30318: Error while querying attribute usages
Cause: Error while querying attribute label usages
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30319: Error while inserting workflow task timer
Cause: Error while inserting workflow task timer {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30320: Error while querying workflow task timer
Cause: Error while querying workflow task timer based on task metadata and application name
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30321: Error while deleting workflow task timer
Cause: Error while deleting workflow task timer {0}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30322: Error while querying workflow task
Cause: Error while querying workflow task {0}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30323: Error while inserting workflow task
Cause: Error while inserting workflow task {0}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30324: Error while updating workflow task
Cause: Error while deleting workflow task {0}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30325: Error while deleting workflow task
Cause: Error while updating workflow task timer {0}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30326: Current user does not have the WRITE privilege on task attribute: {1}
Cause: Current user {0} does not have WRITE privilege for {1} on task with taskId {2}
Action: Grant the WRITE access for the current user/role. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30327: Current user does not have the ADD privilege on task attribute: {1}
Cause: Current user {0} does not have ADD privilege for {1} on task with taskId {2}
Action: Grant the ADD access for the current user/role. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30328: Current user does not have the READ privilege on task attribute: {1}
Cause: Current user {0} does not have READ privilege for {1} on task with taskId {2}
Action: Grant the READ access for the current user/role. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30329: Error while querying workflow task assignment statistic
Cause: Error while querying workflow task assignment statistic {0}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30330: Error while inserting workflow task assignment statistic
Cause: Error while inserting workflow task assignment statistic {0}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30331: Error while updating workflow task assignment statistic
Cause: Error while deleting workflow task assignment statistic {0}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30332: Error while deleting workflow task
Cause: Error while updating workflow task timer {0}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30333: Error while Inserting Evidence
Cause: Insertion of task evidence : {0}, resulted in error : {1}
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections. Ensure that a valid Evidence is being inserted by the worklist application.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30334: Error while Updating Evidence
Cause: Updation of task evidence : {0}, resulted in error : {1}
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30335: Error while Fetching Evidence
Cause: Querying for task evidence matching {0} condition, resulted in error : {1}
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30336: Error while Inserting Evidence Service data
Cause: Inserting into {0} table, resulted in error : {1}
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30337: Error while Updating Evidence Service data
Cause: Updating record(s) of {0} table, resulted in error : {1}
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30338: Error while Deleting Evidence Service data
Cause: Deleting record(s) from {0} table, resulted in error : {1}
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30339: Error while Fetching Evidence Service data
Cause: Fetching records from {0} table, resulted in error : {1}
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30340: Error while Inserting header properties data
Cause: Inserting into {0} table, resulted in error : {1}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30341: Error while Deleting header properties data
Cause: Deleting from {0} table, resulted in error : {1}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30342: Error while Fetching header properties data
Cause: Fetching records from {0} table, resulted in error : {1}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30343: Error while Inserting rule dictionary data.
Cause: Inserting into {0} table, with dictionary {1}, package {2} resulted in error: {3}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30344: Error while Deleting rule dictionary data.
Cause: Deleting from {0} table, with dictionary {1}, package {2} resulted in error: {3}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30345: Error while Updating rule dictionary data.
Cause: Updating {0} table, with dictionary {1}, package {2} resulted in error: {3}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30346: Error while Fectching rule dictionary data.
Cause: Fetching records from {0} table, with dictionary {1}, package {2} resulted in error: {3}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30347: Cannot write dictionary with outstanding updates.
Cause: Dictionary {0}, package {1} has outstanding updates that must be committed.
Action: Commit all dictionary edits by calling update method on RuleDictionary before writing to database.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30348: Cannot update a read-only dictionary.
Cause: Dictionary {0}, package {1} is marked as 'read only' and cannot be updated in the database.
Action: Dictionaries can be marked as read-only or otherwise using the WFRuleDictionaryFinder class.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30349: Rule Dictionary name conflict.
Cause: A dictionary with the name {0} and package {1} already exists in the database.
Action: Specify a different name and/or package for the dictionary.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30350: Error while inserting approval group.
Cause: Inserting approval group {0} resulted in error: {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30351: Error while updating approval group.
Cause: Updating approval group {0} resulted in error: {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30352: Error while deleting approval group.
Cause: Deleting approval group {0} resulted in error: {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30353: Error while getting approval group.
Cause: Getting approval group {0} resulted in error: {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30354: Error while getting approval groups.
Cause: Getting approval groups with search string {0} and search type {1} resulted in error: {2}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30360: Error while inserting approval record.
Cause: Inserting approval record with task Id {0} and record ID {1} resulted in error: {2}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30361: Error while updating approval record.
Cause: Updating approval record with task Id {0}, subtask ID {1}, history version {2}, dimension instance ID {3}, and stage instance ID {4} resulted in error: {5}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30362: Error while deleting approval record.
Cause: Deleting approval record with task Id {0} resulted in error: {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30363: Error while getting approval record.
Cause: Getting approval record with task Id {0} and version {1} resulted in error: {2}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30370: Error while inserting approval instance.
Cause: Inserting approval instance {0} resulted in error: {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30371: Error while updating approval instance.
Cause: Updating approval instance {0} with task Id {1}, instance type {2}, and entity name {3} resulted in error: {4}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30372: Error while deleting approval instance.
Cause: Deleting approval instance with task Id equals {0} resulted in error: {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30373: Error while getting approval instance.
Cause: Getting approval instance with approval instance Id {0} resulted in error: {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30374: Error while getting approval instances.
Cause: Getting approval instance with approval task Id {0} resulted in error: {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30380: Error while inserting approval record reason.
Cause: Inserting approval record reason with reason Id {0}, reason code {1}, and reason type {2} resulted in error: {3}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30381: Error while updating approval record reason.
Cause: Updating approval record reason with reason Id {0}, reason code {1}, and reason type {2} resulted in error: {3}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30382: Error while deleting approval record reason.
Cause: Deleting approval record reason with reason Id {0} and sequence {1} resulted in error: {2}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30383: Error while getting approval record reason.
Cause: Getting approval record reason with reason Id {0} and sequence {1} resulted in error: {2}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30385: Error while inserting task sequence change.
Cause: Inserting task sequence change with correlation Id {0}, anchor chain {1}, change type {2} resulted in error: {3}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30386: Error while updating task sequence change.
Cause: Updating task sequence change with correlation Id {0} resulted in error: {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30387: Error while deleting task sequence change.
Cause: Deleting task sequence change with correlation Id {0} resulted in error: {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30388: Error while getting task sequence change.
Cause: Getting task sequence change with correlation Id {0} resulted in error: {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30390: Error during update.
Cause: No matching row found while updating {0} with parameter {1}.
Action: Verify that the row is available during update.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30391: Error while querying task payload collection targets
Cause: Error while querying task payload collection targets for task {1} with version{2}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30392: Error while performing {0} operation related to task aggregation
Cause: Error while performing {0} operation related to task aggregation
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30400: Error occured while inserting a task attachment record.
Cause: Error occured whilst inserting attachment {0} for task {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30401: Error occured while versioning a task attachment record.
Cause: Error occured whilst versioning attachment {0} for task {1}, version {2}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30402: Error occured while generating a new Task Number.
Cause: Generation of a new Task Number failed with the error: {0}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30403: Error occured while creating a new task history entry.
Cause: Creation of task history entry for task id {0} failed with the error: {1}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30404: Error occured while writing task translation data.
Cause: Write of task translation data for task id {0} failed with the error: {1}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30405: Failed to query task number for task.
Cause: Attempt to query task number for task id {0} failed.
Action: Check the task id is correct, and that the task has not been deleted. Check any underlying exception, and the database connection.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30406: Unsupported database type for human workflow persistency.
Cause: The databse type {0} is not supported by human workflow services persistency.
Action: Check your installation settings, and ensure that RCU install completed correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30407: Error querying the process instances based on the logged in user.
Cause: Error in querying process instances based on the logged in user {0}
Action: Check your installation settings, and ensure that RCU install completed correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30408: Eror in querying instance stake holder for logged in user.
Cause: Error in querying instance stake holder for logged in user {0}.
Action: Check your installation settings, and ensure that RCU install completed correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30409: Error in deleting process instance attachment
Cause: Error in deleting process instance {0} attachment {1}.
Action: Check your installation settings, and ensure that RCU install completed correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30410: Error while deleting workflow task metadata
Cause: Error while deleting workflow task metadata {0}
Action: Check the underlying exception and the database connection information.If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30411: Error occured while inserting a pre-initiated task attachment record.
Cause: Error occured while inserting attachment {0} for task correlationId {1}.
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30412: Error occured updating attachment record to add pre-initiated task attachment to the task
Cause: Error occured while updating attachment records for correlationId {0} to add it to task {1}
Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30450: JAXB-Toplink conversion failed.
Cause: Conversion of {0} to {1} failed with error {2}
Action: Check the underlying exception.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30451: Persistency not supported for this object type.
Cause: The class {0} does not suppot persistency of objects of type {1}.
Action: Check the type of object and the class being used to persist it.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30501: Error in authenticating user
Cause: Error in authenticating and creating a workflow context for user {0}
Action: Verify that the user credentials and identity service configurations are correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30502: Error in Verification Service when creating Context
Cause: Error in Verification Service when creating Context. {0}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30503: Invalid Token Error in Verification Service
Cause: Invalid Token Error in Verification Service. Received invalid token in {0}
Action: Verify that correct token is passed.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30504: Internal Error in Verification Service
Cause: Internal Error in Verification Service for user {0}. {1}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30506: Runtime error in Task Query Service
Cause: Runtime error in Task Query Service. {0}
Action: Verify that the parameters passed are correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30507: Runtime error in Task Report Service
Cause: Runtime error in Task Report Service. {0}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30508: Error while inoking URL to display the content
Cause: Error while invoking URL. {0}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30509: Insufficient privileges to authenticate on-behalf of another user.
Cause: User {0} cannot authenticate on-behalf of user {1} without admin privileges.
Action: Only users with admin privileges can authenticate on-behalf of another user.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30513: Insufficient privileges to access the task info for this task
Cause: User {0} cannot access the task info for task: {1}
Action: Ensure that the user has been granted appropriate privileges to access the task info for this task.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30514: Session timed out
Cause: Session has timed out, because it was inactive for {0} minutes and {1} seconds.
Action: Relogin in to the application.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30515: Access to internal workflow context is denied
Cause: Requested access to internal workflow context is not allowed according to security policy
Action: Ensure that correct security policy is used. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30516: Token decryption failed
Cause: Could not extract infromation from Workflow context token
Action: Ensure that the Workflow context is not corrupted and it was generated from one of the nodes in the same cluster.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30701: Insufficient privileges to access metadata for another user.
Cause: User {0} attempted to access metadata for user {1} without having appropriate admininstrator privileges.
Action: Ensure that the appropriate privileges have been granted before attempting to access metadata belonging to another user.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30704: Failed to instantiate workflow rule repository service
Cause: Could not create repository service for workflow rule dictionary {1}, package {2}
Action: Check underlying exception. Ensure dictionary name and package are valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30705: Failed to get workflow rules
Cause: Could not get workflow rules for {0}
Action: Check underlying exception. Ensure user or group name is correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30706: Rule tests for task payload cannot be defined in this release
Cause: Definition of rules with tests that check the task payload is not supported in this release.
Action: Remove any payload tests from the rule definition.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30707: Invalid workflow rule action.
Cause: Action type {0} is not a valid rule action type.
Action: Specify a valid rule action type.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30708: Failed to update rule dictionary.
Cause: Update of dictionary {0} failed with error: {1}
Action: Check underlying exception. Ensure that workflow rules dictionary name is valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30709: Failed to load ruleset.
Cause: Failed to load ruleset from dictionary {0} for rule with ID {1}.
Action: Check underlying exception. Ensure dictionary name and rule ID are valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30710: Failed to create ruleset.
Cause: Failed to create ruleset in dictionary {0}.
Action: Check underlying exception. Ensure dictionary name is valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30711: Invalid authentication context.
Cause: Invalid authentication context has been passed to user metadata service.
Action: Ensure valid authentication context is passed.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30712: Failed to execute workflow ruleset.
Cause: Rules engine reported error when executing workflow ruleset in dictionary {0}.
Action: Check underlying exception. Ensure rules are correctly defined in ruleset.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30713: Failed to parse workflow ruleset.
Cause: Rules repository reported error when generating RuleLanguage for workflow ruleset in dictionary {0}.
Action: Check underlying exception. Ensure rules are correctly defined in ruleset.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30714: Missing date in date range.
Cause: Both start date and end date must be specified.
Action: Specify both a start date and an end date.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30715: End date is before start date.
Cause: End date cannot occur before the start date.
Action: Specify an end date that occurs after the start date.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30716: Invalid workflow rule test attribute
Cause: Workflow rule test {0} uses an invalid task attribute: {1}.
Action: Specify valid task attributes when defining workflow rules.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30717: Invalid operator in workflow rule test expression.
Cause: The workflow rule test {0} uses the invalid operator {1}.
Action: Ensure that a valid operator is specified and that it is appopriate for the datatype of the attribute.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30718: Cannot specify null value in workflow rule test expression.
Cause: The workflow rule test {0} compares the task attribute to null.
Action: A valid value must be specified for the test expression.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30719: Cannot define a rule test for a Duration attribute.
Cause: The workflow rule test {0} is for an attribute of type Duration.
Action: Rule tests for Duration attribute types are not supported. Select another attribute.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30720: Error in invoking user metadata service.
Cause: A client side error occured in invoking the user metadata service.
Action: Verify that the connection information for the server is correct, and that the server hosting the user metadata service is available.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30721: Error in invoking user metadata service operation.
Cause: An client side error occured in invoking the user metadata service operation {0}.
Action: Verify that the connection information for the server is correct, and that the server hosting the user metadata service is available.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30722: Fault reported by user metadata Web service.
Cause: The user metadata service returned a fault for the following error: {0}
Action: Refer to the error reported by the fault.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30723: User does not exist.
Cause: There is no such user as {0}.
Action: Enter a valid user name.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30724: Group does not exist.
Cause: There is no such group as {0}.
Action: Enter a valid group name.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30725: Cannot reassign to user or group.
Cause: {0} does not have the neccessary permissions to assign tasks to {1}
Action: Select a different user or group.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30726: Rule name is not unique.
Cause: A rule named {0} already exists for {1}.
Action: Specify a different name.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30727: Cannot update GrantedTaskView grant type.
Cause: Updates to UserTaskView grants cannot change grant type.
Action: Do not change the grant type when updating UserTaskView ViewGrants.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30728: Invalid ViewGrant type.
Cause: Invalid View Grant type of {0} was specified for grant of view {1} to {2}.
Action: Valid ViewGrant types are SHARE_DATA and SHARE_DEFINITION.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30729: Invalid UserTaskView type.
Cause: {0} is not a valid value for view type.
Action: Valid UserTaskView types are VIEW and STANDARD_VIEW.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30730: Public UserTaskView access error.
Cause: User {0} does not have permission to manage views of type STANDARD_VIEW.
Action: Only users with workflow administrator privilege can create, update or delete UserTaskViews of type PUBLIC_VIEW.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30731: View for update does not exist.
Cause: Cannot update view {0}. No view exists with ID {1}.
Action: Check that the view ID is correct, and that another user has not deleted the view being updated.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30732: Invalid OptionalInfo value specified.
Cause: {0} specifies an invalid OptionalInfo value of {1}.
Action: Specify a valid OptionalInfo value.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30733: Invalid column specified for ordering clause.
Cause: {0} specifies an invalid ordering column name of {1}.
Action: Specify a valid Task column name in the ordering clause.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30734: Invalid sort order specified for ordering clause.
Cause: {0} specifies and invalid sort order of {1} for the column {2}.
Action: Specify a valid sort order in the ordering clause.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30735: Invalid column specified for view chart group by column.
Cause: The view {0} specifies an invalid chart group by column name of {1}.
Action: Specify a valid Task column name.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30736: Rules cannot be associated with 'TODO' tasks.
Cause: The rule {0} illegally specifies the 'TODO' task type {1}.
Action: Assocatiate the rule with a different task type, or with no task type.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30737: Application role does not exist.
Cause: There is no such role as {0} in application {1}.
Action: Specify a valid role and application name.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30738: Invalid Participant type.
Cause: Participant named {0} specifies an invalid type of {1}.
Action: Specify a valid ParticipantType. Valid types are USER, GROUP, APPROLE.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30739: Invalid Arguments specified.
Cause: Atleast one among {0} , {1} and {2} seems to be invalid .
Action: Specify valid arguments.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30740: Policy Object already exists.
Cause: Policy object {0} already exists in the policy store.
Action: .

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30741: Policy Store error.
Cause: Failed to perform the desired operation.
Action: See the exception log for the reason behind the failure to fix the issue.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30742: Attempt to execute privileged action.
Cause: An attempt to execute a privileged action was made.
Action: Ensure that the codebase being used has the necessary permissions and privileges. If not, grant the same in the application's policy file. Contact oracle support if error is not fixable.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30743: Application Role in use.
Cause: Application Role named {0} is in use, the desired operation cannot be performed.
Action: Clear all the dependencies on the app role {0} before performing this operation.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30744: Policy Object not found.
Cause: Atleast one policy object among {0},{1} not found in the policy store.
Action: Provide valid arguments

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30745: Invalid Application type.
Cause: Application named {0} specifies an invalid type.
Action: Specify a valid Application Type. Valid types are soa-infra, OracleBPM, OracleBPMComposer.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30746: Invalid User type.
Cause: User {0} does not have administrator privileges.
Action: Login as an adminitrator to perform this operation.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30747: UserApplicationData not found.
Cause: No UserApplicationData found with the id {0}
Action: Check the id is correct. The UserApplicationData may have been deleted.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30748: Presentation not found.
Cause: No Presentation found with the id {0}
Action: Check the id is correct. The Presentation may have been deleted.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30749: Invalid PresentationDataType.
Cause: The presentation {0} specifies an invalid PresentationDataType of {1}. Valid values are: {2}.
Action: Specify a valid PresentationDataType.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30750: Presentation type mismatches View type.
Cause: The view {0} is associated with Presentation {1}, which is of type {2}, instead of the expected type {3}.
Action: Views must be associated with Presentations of matching type. Associate the view with a Presentation of the appropriate type.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30751: Dynamic Assignment Framework function {0} experienced error querying the workflow schema: {1}
Cause: A Dynamic Assignment Function experienced an error whilst attempting to query data from the workflow schema.
Action: Check the underlying error. Verify that the workflow datasource is correctly configured, and that database server is available. If this is a custom dynamic assignment fuction, ensure that the SQL being executed is valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30752: Group {0} not found by Authorization Service
Cause: The Dynamic Assignment Framework was unable to locate a group named {0} using the Authorization Service.
Action: Check that the group name is correct. If the group name is correct, check that the Authorization Service is configured correctly, and that the directory it uses contains the specified group.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30753: Dynamic Assignment Framework experienced error invoking Authorization Service: {0}
Cause: The Dynamic Assignment Framework experienced an error whilst attempting to invoke the Authorization Service.
Action: Check the underlying error, and verify that the identity service is configured correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30755: No such Dynamic Assignment Function as {0}
Cause: There is no such function as {0} registered with the Dynamic Assignment Framework. Specify a valid function name
Action: Check that a correct function name is specified. If this is a correct function name, ensure that the function is registered in the workflow configuration file.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30756: Dynamic Assignment Function {0} does not support user assignment.
Cause: The Dynamic Assignment Function {0} does not allow dynamic assignment to users. Only assignment to groups is supported.
Action: Only use this function for group assignments. To enable user assignment, the java class that implements this function must be modified to implement the IDynamicUserAssignment interface.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30757: Dynamic Assignment Function {0} does not support group assignment.
Cause: The Dynamic Assignment Function {0} does not allow dynamic assignment to groups. Only assignment to users is supported.
Action: Only use this function for user assignments. To enable group assignment, the java class that implements this function must be modified to implement the IDynamicGroupAssignment interface.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30758: Could not locate Dynamic Assignment Function implementation class: {0}
Cause: The Dynamic Assignment Framework could not locate function implementation class: {0} Either the class name is incorrect, or the class is not in the classpath
Action: Check that the specified class is located in the classpath. Check that the correct classname is specified in the workflow configuration file.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30759: Dynamic Assignment Function class interface implementation error.
Cause: Dynamic Assignment Function class Classes that implement {0} does not implement IDynamicUserAssignmentFunction or IDynamicGroupAssignmentFunction.
Action: Dynamic Assignment Functions must implement at least one of the interfaces IDyanmicUserAssignmentFunction or IDynamicGroupAssignmentFunction. Check the specified class and ensure it implements one of the interfaces.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30760: Failed to instantiate instance of Dynamic Assignment Function class.
Cause: The Dynamic Assignment Framework could not instantiate the Dynamic Assignment Function class: {0} because it is not a concrete class.
Action: Ensure that the class {0} is not an interface or abstract class.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30761: Dynamic Assignment Function class constructor error.
Cause: The Dynamic Assignment Framework could not instantiate an instance of {0} becuase there is no accessible no-argument constructor.
Action: Ensure that the class {0} is public, and procides a public, no-argument constructor.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30762: Dynamic Assignment Function class does not implement IDynamicAssignmentFunction.
Cause: Dynamic Assignment Function class {0} must implement the interface IDynamicAssignmentFunction.
Action: Check the specified class and ensure it implements the interface IDynamicAssignmentFunction.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30801: Error selecting user metadata from repository.
Cause: An attempt to select data from table {0} resulted in the error: {1}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30802: Error inserting user metadata into repository.
Cause: An attempt to insert user data into table {0} resulted in the error: {1}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30803: Error updating user metadata in repository.
Cause: An attempt to update user data in table {0} resulted in the error: {1}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30804: Error deleting user metadata from repository.
Cause: An attempt to delete user data from table {0} resulted in the error: {1}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30805: Operation not supported for this column type.
Cause: The operator {0} is not supported for columns of type {1}.
Action: Use a different operator when specifying predicate conditions for this column.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30851: User has insufficient privileges to update workflow runtime configuration data.
Cause: User {0} attempted to update runtime configuration data without having the required {1} privilege.
Action: Ensure that the user has been granted the appropriate workflow privileges before updating runtime configuration data.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30852: Invalid task message attribute specified in attribute label.
Cause: The flexfield label {0} uses the invalid task flexfield column name {1}.
Action: Specify a valid task flexfield column name.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30853: Workflow definition does not exist.
Cause: No workflow definition found with ID {0}.
Action: Specify a valid workflow defintion ID.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30854: Failed to retreive list of Dynamic Assignment Functions.
Cause: Could not get list of Dynamic Assignment Functions.
Action: Check underlying exception. Ensure Dynamic Assignment Functions are configured correctly in the workflow configuration file.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30855: Flexfield mappings for complex payload attributes must specify an xpath expression.
Cause: Payload attribute {0} is a complex type. Mappings must provide an xpath to a simple type property.
Action: Provide a valid xpath expression that maps to a simple-type property of the complex type.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30856: Payload attribute type does not match flexfield label type.
Cause: Payload attribute {0} has a type that does not match the type for flexfield label {1}.
Action: Use a flexfield label of the appropriate type.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30857: Workflow payload attribute not found.
Cause: Workflow task type {0} does not have a payload attribute named {1}.
Action: Ensure that workflow task type and payload attribute name are correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30858: Error in invoking runtime config service.
Cause: A client side error occured in invoking the runtime config service.
Action: Verify that the connection information for the server is correct, and that the server hosting the runtime config service is available.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30859: Error in invoking runtime config service operation
Cause: An client side error occured in invoking the runtime config service operation {0}.
Action: Verify that the connection information for the server is correct, and that the server hosting the runtime config service is available.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30860: Fault reported by runtime config service
Cause: The runtime config service returned a fault for the following error: {0}
Action: Refer to the error reported by the fault.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30861: Label name is already in use.
Cause: A label with the name {0} already exists.
Action: Specify a different name for the label.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30862: Workflow definition does not exist.
Cause: No workflow definition found with task definition namespace {0}.
Action: Specify a valid workflow definition namespace.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30863: Cannot delete an attribute label for which payload mappings exist.
Cause: Payload mappings exist for the attribute label {0}.
Action: Remove all payload mappings before deleting the attribute label.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30864: Label is already in use by this task component definition.
Cause: The attribute label {0} is already being used by this workflow definition.
Action: Specify a different label.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30865: Invalid attribute type.
Cause: An invalid attribute type of {0} was specified.
Action: Specify a valid attribute type.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30866: Flexfield is already in use by this task component definition.
Cause: The flexfield {0} is already being used by this workflow definition in a mapping to the label {1}.
Action: Specify another label that uses a different flexfield.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30890: Approval Group already exists
Cause: An Approval Group with this name already exists:{0}
Action: Use a different name for the Approval Group or use updateApprovalGroup method if referring to this Approval Group .

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30891: Approval Group not found.
Cause: Approval Group with the given name doesnot exist: {0}
Action: Verify that the Approval Group name is correct and whether it has been correctly created.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30892: Approval Group not deleted.
Cause: The specified Approval Group could not be deleted: {0}
Action: Verify that the Approval Group name is correct and whether it had been correctly created.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30893: Approval Group member not in list.
Cause: The specified Approval Group member was not found in the member list for the given Approval Group: {0}
Action: Verify that the Approval Group name is correct and that the specified member had been correctly created in the group.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30894: Approval Group member not created.
Cause: The specified member could not be added to the given Approval Group: {0}
Action: Verify that the Approval Group name is correct and that the member is valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30895: Approval Group member not updated.
Cause: The specified member could not be updated in the given Approval Group: {0}
Action: Verify that the Approval Group name is correct and that the member had been correctly created.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30897: Approval Group member not deleted.
Cause: The specified member could not be deleted from the given Approval Group: {0}
Action: Verify that the Approval Group name is correct and whether the member had been correctly created.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30898: Approval Group member already exists.
Cause: The specified member already exists in the given Approval Group: {0}
Action: Use the updateInGroup api instead.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30899: No matching Approval Group found.
Cause: There are no Approval Groups matching the given search condition: {0}
Action: Verify the search condition and search type specified.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30900: Unable to log adhoc approver insertion .
Cause: There was an error trying to log the adhoc approver insertion information in the AMX Change table: {0}
Action: Verify that the stage name and task ID provided are valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30901: Task Evidence does not exist.
Cause: No Evidence found in the repository.
Action: Ensure that an evidence corresponding to the operation exists in the repository.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30902: Task Evidence JAXB Model is malformed.
Cause: This could either be because the XML data for the model does not confirm to the schema or there was an internal JAXB error.
Action: Ensure that the XML data being passed confirms to the Task Evidence Service schema.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30903: Certificate does not exist.
Cause: A certificate with Serial Number {0} and Issuer DN {1} was not found.
Action: Upload the certificate before proceeding. Also ensure that the CA and the URL have been uploaded.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30904: The evidence is not valid.
Cause: All required parmaters are not set.
Action: Ensure that all required parameters are set into the evidence object.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30905: The certificate with Serial Number {0} and Issuer DN {1} is not valid.
Cause: The certificate could have expired. The certificate could also be in an unsupported format or malformed.
Action: Ensure that the certificate is as supplied by the certificate authority.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30906: The signature is not valid.
Cause: The signature does not confirm to the content and certificate. The signature may also be in an unsupported format or malformed.
Action: Ensure that the signature is not modified once it is created.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30907: Internal Error.
Cause: The underlying Security APIs have thrown an exception.
Action: Look at the exception trace for more information.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30908: CRL validation error for certificate Id {0} and CA name {1}.
Cause: The CRL could not be validated.
Action: Ensure that the CA URL exists and is correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30909: Certificate cannot be uploaded.
Cause: The certificate could not be uploaded. Only X.509 certificates are supported.
Action: Ensure that the file or string contains a X.509 certificate in a supported format. Also, ensure that the certificate or any other certificate in the chain do not exist in the system. All those certificate which did not exist in the system would have been uploaded.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30910: Invalid Access Error.
Cause: User {0} does not have permission to perform {1}.
Action: Ensure the user has been granted appropriate privileges.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30911: Unable to initialize the queue connection factory for queue {0}
Cause: Unable to initialize the queue connection factory for queue {0}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30912: Error in invoking task evidence service
Cause: A client side error occured in invoking the task evidence service.
Action: The service could be down. Check the exception error stack to identify the error. If the error persists, contact Oracle Support Services..

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30913: Error in task evidence SOAP service
Cause: An error occured in invoking the task evidence service over SOAP.
Action: Ensure that soap messages are proper and well formed. Check the exception error stack to identify the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30951: Invalid view ID.
Cause: The view ID: {0} does not match any view stored in the repository.
Action: Ensure that a correct view ID is being passed.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30952: Invalid display column.
Cause: The display column {0} is not a valid Task column.
Action: Specify a valid column name.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30953: User has insufficient privileges to use given filter.
Cause: The user {0} in identity context {1} does not have sufficient privileges to query tasks with {2} filter.
Action: Ensure that proper privileges are granted to the user.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30954: Invalid assignment filter value specified for predicate.
Cause: The predicate specifies an invalid AssignmentFilter value of {0}.
Action: Specify a valid AssignmentFilter value.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30955: Invalid column name used in predicate.
Cause: The predicate specifies a column named {0} which does not exist on the table {1}.
Action: Specify a valid column and table in the predicate.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30956: Invalid logical operator used in predicate.
Cause: The predicate uses an invalid logical operator of {0}.
Action: Use a valid logical operator. Valid values are AND and OR.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30957: Invalid operator used in predicate.
Cause: The predicate uses an invalid operator value of {0} with column {1}.
Action: Specify a valid operator value.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30958: Predicate specifies an invalid operator for a null value.
Cause: The operator {0} cannot be used with a value of null.
Action: Specify a value, or use the EQ, NEQ, IS_NULL or IS_NOT_NULL operators.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30959: Predicate clause with ValueListType must use IN or NOT_IN operator.
Cause: The operator {0} cannot be used with a value list.
Action: Use the IN or NOT_IN operators when using a value list.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30960: Invalid value specified for N_DAYS operator in predicate clause.
Cause: The predicate value {0} is not valid for the operator {1}.
Action: Specify an integer value.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30961: Invalid value specified in predicate clause.
Cause: The value {0} for column {1} is invalid for the column's datatype.
Action: Specify a value that is of the correct type, or is another column with a matching datatype.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30962: Invalid Presentation type.
Cause: The specified Presentation {0} is of type {1}, but the required type is {2}.
Action: Specify a different Presentation of the correct type.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-30963: Invalid View type.
Cause: The specified View {0} is of type {1}, which is not valid for querying tasks.
Action: Specify a different View of a correct type (VIEW or STANDARD_VIEW).

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31002: Error while publishing message to notification queue
Cause: Error while publishing message to notification queue
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31003: Unable to initialize the queue connection factory for queye {0}
Cause: Unable to initialize the queue connection factory for queye {0}
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31004: Error while querying notification from repository for ID {0}
Cause: Error while querying notification from repository for ID {0}
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31005: Error while inserting notification in repository
Cause: Error while inserting notification in repository
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31006: Error while updating notification in repository for ID {0}
Cause: Error while updating notification in repository for ID {0}
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31007: Error while deleting notification in repository for ID {0}
Cause: Error while deleting notification in repository for ID {0}
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31008: Incoming message could not be processed
Cause: Incoming message could not be processed
Action: Ensure that the response message is not corrupted

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31009: Incoming message content is invalid
Cause: Incoming message could not be processed due to invalid content
Action: Ensure that the response message is not corrupted: The encrypted response should begin and end with '[[NID]]'

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31010: No NID Placeholder
Cause: Incoming message content does not contain Notification ID placeholders
Action: Ensure that the response message is not corrupted

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31011: Error while updating table
Cause: Error while updating {0} table
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31012: Error while inserting into table
Cause: Error while inserting into {0} table
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31013: Error while deleteing from table
Cause: Error while deleting from {0} table
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31014: Error while selecting from table
Cause: Error while selecting from {0} table
Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31015: Error while sending notification
Cause: Error while sending notification to {0}
Action: Check the underlying exception and fix it.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31016: Error while receiving notification response
Cause: Error while receiving response from {0} at {1}; for message {2}
Action: Ensure that response message is not corrupted; User should respond to actionable notifications from the same email account to which it was sent; Task status has not changed

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31017: Cannot create notification object
Cause: Error while creating {0} object
Action: Internal Error; Cannot create Notification Object

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31018: Incorrect Notification Configuration
Cause: Incorrect Configuration : {0}
Action: NotificationMode in workflow-notification-config.xml should be either EMAIL or ALL to send Email notifications; It should be ALL to send any other type of notifications

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31019: MimeType not supported
Cause: MimeType {0} is not suppored for channel type{1}
Action: In the application, Use only supported mime types for sending notifications

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31020: Auto Reply Error
Cause: Error while sending auto reply on {0} channel
Action: Internal Error. Ensure that the message being replied to is not corrupted

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31021: Invalid Parameters
Cause: Invalid parameters supplied for Notification : {0}
Action: Provide valid notification inputs like recipient Address, Channel type etc

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31022: Could not register/un register/fetch spam sources
Cause: Could not register/un register/fetch spam sources: {0}
Action: Possible cause : Invalid address is being registered/unregistered

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31023: Cannot send Notification to specified address
Cause: Cannot send {0} notification to {1} address. The address is being marked as 'invalid' and no further notification would be sent to this address.
Action: Make sure that : the address specified is correct; the Email/Gateway server is up and running. Once the problem is corrected, remove the address from invalid address list using EM.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31024: Invalid recipient address
Cause: Recipient address specified for {0} notification is invalid : {1}
Action: Check Workflow Notification Configuration; Ensure that Email/IM recipient address is valid.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31025: Actionable Email/IM has been responded from a different account.
Cause: Actionable {2} had been sent to {0}, but received response from {1}.
Action: Actionable notifications should be responded from the same account to which it was sent.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31026: user-ID not set
Cause: user-ID field is not set in the user payload
Action: Ensure that the payload contains user ID

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31027: group-ID is not set
Cause: group-ID field is not set in the group payload
Action: Ensure that Payload contains group ID

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31028: Could not send notification to user
Cause: Could not send notification to user {0}
Action: Check Workflow Notification Configuration. Ensure that underlying channels are configured.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31029: Notification Channel not supported
Cause: Notification Channel {0} is not supported
Action: Requested channel is not supported.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31030: Error while creating notification content
Cause: Could not create notification content
Action: Ensure that the files being used for attachment exist and not corrupted.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31031: Incorrect incoming Notification Configuration
Cause: Incorrect Incoming Configuration : {0}
Action: The AccountName in workflow-config.xml should be one of the names used in workflow-notification-config.xml

Level: 1

Type: ERROR

Impact: Programmatic

BPM-31032: Error status received from UMS.
Cause: Status detail : Status type : {0}, Status Content : {1}, Addressed to : {2}, UMS Driver : {3}, UMS Message Id : {4}, Gateway message Id : {5}, Status Received at : {6}
Action: Check status details and fix the underlying reason, which caused error

Level: 1

Type: ERROR

Impact: Programmatic

BPM-32001: Error in Identity Service
Cause: Error occurs while using Identity Service
Action: Check underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-32002: Error in create parameters from WSIF Java Web Services message
Cause: The {0} could not be created because expected element {1} is not be found in the element {2} in the parameter passed to WSIF Java Web Services
Action: Check the message passed to the Web service. Also check underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-35001: Configuration file {0} not found.
Cause: Could not locate configuration file with the path: {0}
Action: Ensure that the path is correct, and that there is a configuration file at the specified path.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-35002: Configuration file format error whilst parsing file {0}: {1}
Cause: Could not parse the configuration file {0} because of the error: {1}
Action: Check the underlying error, and ensure that the configuration file is formatted correctly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-35003: Error saving configuration file {0}: {1}
Cause: Failed to save the configuration file to {0} because of the error: {1}
Action: Check the underlying error. Ensure that the path {0} is correct, and that if the file already exists that it is in a writeable state.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-35004: Workflow deployment is not supported
Cause: Workflow deployment is not supported in platform {0}
Action: Check the underlying error. Ensure that the platform {0} is correct

Level: 1

Type: ERROR

Impact: Programmatic

BPM-35005: Unable to deploy workflow files
Cause: Unable to deploy workflow files
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-35006: Unable to undeploy workflow files/metadata
Cause: Unable to undeploy workflow files/metadata
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-35007: Unable to load service client configuration file
Cause: Unable to load service client configuration file {0}.
Action: Check if service client configuration file {0} exists in the classpath. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-35008: Unable to find service definision in client configuration file
Cause: Unable to find service {0} definision in client configuration file {1}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-35009: Unable to obtain scheduler to schedule workflow service timers
Cause: Unable to obtain scheduler to schedule workflow service timers
Action: Retry the action if possible. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-35010: Unable to Encrypt data
Cause: Unable to Encrypt data
Action: Check installation/post-installation steps for errors. Check for errors during SOA server startup.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-35011: Unable to Decrypt data
Cause: Unable to Decrypt data
Action: Check for corrupted encrypted data. Check installation/post-installation steps for errors. Check for errors during SOA server startup.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-35012: Unable to fetch/generate encryption key
Cause: Unable to fetch/generate encryption key
Action: Check installation/post-installation steps for errors. Check for errors during SOA server startup.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36001: Internal error.
Cause: An internal error occurred in the Decision Service, info code {0}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36011: Error while initializing decision service.
Cause: Error while initializing decision service.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36012: Error creating a JAXB marshaller for the decision service.
Cause: Error while creating a JAXB marshaller for the decision service.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36013: Error creating a JAXB unmarshaller for the decision service.
Cause: Error while creating a JAXB unmarshaller for the decision service.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36050: Error in decision service interaction pattern.
Cause: An error occurred in interpreting the interaction pattern {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36051: Error while executing interaction pattern Assert.
Cause: Error while executing interaction pattern Assert for path {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36052: Error while executing interaction pattern AssertExecute.
Cause: Error while executing interaction pattern AssertExceute for path {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36053: Error while executing interaction pattern Watch.
Cause: Error while executing interaction pattern Watch for path {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36054: Error while executing interaction pattern AssertExceuteWatchStateless.
Cause: Error while executing interaction pattern AssertExceuteWatchStateless for path {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36055: Error while executing interaction pattern AssertExceuteWatchStateful.
Cause: Error while executing interaction pattern AssertExceuteWatchStateful for path {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36056: Error while executing interaction pattern CallFunctionStateless.
Cause: Error while executing interaction pattern CallFunctionStateless for path {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36057: Error while executing interaction pattern CallFunctionStateful.
Cause: Error while executing interaction pattern CallFunctionStateful for path {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36101: Error while initializing the decision service cache.
Cause: Error while initializing the decision service cache.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36102: Error reading configuration file.
Cause: Error while trying to read the configuration file {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36103: Error creating the payload.
Cause: Error while trying to create the payload for element {0}, namespace {1}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36104: Error creating the decision document.
Cause: Error while trying to create the decision document for {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36105: Error creating the decision service error SOAP element.
Cause: Error while trying to create the decision service error SOAP element for service {0}, pattern {1}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36106: Error creating the SOAP element from decision.
Cause: Error while trying to create the SOAP element from the decision of service {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36107: Error unmarshalling the decide context.
Cause: Error while trying to unmarshal the payload for pattern {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36108: Decision Service metadata not in cache.
Cause: Cannot find metadata in path {0} for {1}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36109: Error caching the Decision Services metadata.
Cause: Error caching the decision services metadata for path {0}.
Action: Check the underlying exception and correct the error. This is most likely due to a rule modeling isssue. Validate the rule dictionary in rule designer and fix any errors and warnings. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36110: Error unmarshalling decision services configuration.
Cause: Error while trying to unmarshal decision services configuration from URL {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36111: Error validating the decision service request.
Cause: The request for path {0}, service {1} pattern {2} is not valid.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36112: A Decision Service of the given name doesn't exist.
Cause: The component {1} in composite {0} does not expose a service {2}
Action: Check the services that are exposed by component {1}. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36150: Decision Service configuration not available.
Cause: No configuration information available for service {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36151: Error while creating deployment directory.
Cause: Error while creating deployment directory {0} for service {1}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36152: Error while creating WSDL for backend decision service.
Cause: Error while creating the WSDL for the backend decision service {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36153: Error while creating service configuration file for backend decision service.
Cause: Error while creating the service configuration file for the backend decision service {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36154: Error while copying supporting XSD files for decision service.
Cause: Error while copying supporting XSD files for decision service {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36155: Error while generating JAXB classes for decision service.
Cause: Error while generating JAXB classes from {0} for the backend decision service {1}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36156: Error while creating deployment descriptor for decision service.
Cause: Error while creating deployment descriptor {0} for the backend decision service {1}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36157: Error while copy rule repository file to deployment directory.
Cause: Error while copy the file {0} to {1} for decision service {2}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36158: Error while creating partnerlink WSDL.
Cause: Error while creating partnerlink WSDL for {0} in {1}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36159: Error compiling fact classes.
Cause: Error while compiling fact classes for service {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36160: Error copying decision service configuration file.
Cause: Error copying decision service configuration file to {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36161: Error copying decision service files.
Cause: The target directory {0} does not exist.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36162: Rule engine not found.
Cause: Unable to find rule engine provider {1} for {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36163: XML schema type not found.
Cause: Unable to find XML schema type for {0}.
Action: Check the rule model and decision service interaction. Make sure that all the required XSD schema files are part of the project.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36164: Type not supported.
Cause: Unable to create XML schema element for type {0}.
Action: Check the rule model and decision service interaction. Make sure that all the required XSD schema files are part of the project.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36200: Error while initializing the rule engine factory.
Cause: Error while initializing the rule engine factory.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36201: Error while loading a rule engine.
Cause: Error while loading a rule engine for {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36202: Error while loading a fact context.
Cause: Error while loading a fact context for {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36203: Error while creating a rule engine.
Cause: Error while creating rule engine for provider {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36204: Error while creating the fact context.
Cause: Error while creating the fact context for {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36205: Error while creating a rule engine.
Cause: No rule engine class loaded for provider {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36206: Error while creating the fact context.
Cause: No fact context class loaded for fact context {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36207: JAXB context not available for fact.
Cause: No JAXB fact context available for fact {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36208: The type is not supported by decision service.
Cause: The type {0} is not supported by decision service.
Action: Remodel rules and decision service interaction to use supported types.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36311: Unknown rule repository type.
Cause: The rule repository type {0} is unknown or unsupported in this context.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36312: Error while initializing the rule repository.
Cause: The rule repository cannot be initialized.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36313: Error while loading the rule catalog.
Cause: The rule catalog cannot be loaded.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36314: Error while trying to close the rule engine.
Cause: The rule engine cannot be closed.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36321: Error while loading the rule set.
Cause: The rule set cannot be loaded.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36322: A rule catalog could not be found.
Cause: The catalog {1} in package {0} could not be found.
Action: Make sure that the rule catalog {0}.{1} exists in the path {2}. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36331: Error while initializing the rule session.
Cause: The rule session {0} failed to initialize.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36332: Error while resetting the rule session.
Cause: The rule session {0} reset failed.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36333: Error while executing the rule session.
Cause: The rule session {0} failed to execute.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36334: Error while executing a rule session unit of work.
Cause: The rule session {0} failed to execute step {1} {2}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36335: Fact not found in the rule engine working memory, rule session execution failed.
Cause: The rule session {0} failed because an instance of the fact {1} could not be found in the working memory of the rule session.
Action: This is most likely a rule modeling error. The decision service interaction expects the fact instance to exist in the working memory of the rule session. Check the rule actions in rule designer and make sure that a fact of the expected type is being asserted. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36336: Error while executing a rule session unit of work, duplicate fact instances found.
Cause: The rule session {0} failed because more than one fact instance of the fact {1} exists in the rule session working memory. The decision service cannot identify which one to take.
Action: This is most likely due to a rule modeling issue. Make sure that the fact of the given type is asserted only once. One common issue is that the rule conditions are not mutually exclusive and as a result of that more than one rule action is executed. In case the rule action has a assert new statement of the given fact type then multiple fact instances are created in the rule session working memory and the decision service is not able to identify the one that should be returned as the result of the decision service interaction. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36337: Number of facts requested does not match number of facts retrieved from rule engine.
Cause: There are {0} facts requested but the rule engine returned {1} facts.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36338: Wrong fact from rule engine.
Cause: The requested fact name is {0} whereas the onegiven by the rule engine is {1}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36341: Rule session pool object does not exist.
Cause: The requested rule session pool object for path {0} and key {1} does not exist.
Action: Check the underlying exception and correct the error. This is most likely due to a rules validation error. Validate the rule dictionary in Rule Designer and correct the validation error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36351: Error loading fact types into the datamodel.
Cause: The data model failed to load fact types.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36352: Error loading functions into the datamodel.
Cause: The data model failed to load functions.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36353: URL error while reading XSD.
Cause: The data model failed to read the XSD {0} because of an URL error.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36354: Error building the XML schema for a XSD.
Cause: The data model failed to build the XML schema from XSD {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36355: Element not found in XML-Schema file.
Cause: The element for fact type {0} could not be found in XML Schema file {1}.
Action: Make sure that the element {0} exists in the schema file {1} or in one of the schema files that is imported by {1}. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36356: Element not unique in XML-Schema file.
Cause: The element for fact type {0} could not be identified in XML Schema file {1}. There exists multiple elements that could define the fact type {0}: {2}
Action: Make sure that the element for fact type {0} is unique in the schema file {1} or in one of the schema files that is imported by {1}. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36357: The function doesn't exist in the datamodel .
Cause: The requested function {0} does not exist in the rule dictionary data model of decision service {1}.
Action: Check the rule dictionary of decision service {1}. Make sure that the function {0} exists and has correct parameter and package name settings. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36358: The XML-Schema file for the fact {0} could not be found in the composite.
Cause: The XML-Schema file {2} could not be found in the composite. The XML fact {0} of target namespace {1} assumes the existence of the schema file in the composite.
Action: Check the composite for the schema {2} and make sure it has target namespace {1}. The schema is expeccted in the project xsd or businessCatalog folder. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36610: No rule engine provider implementation found for Ilog JRules.
Cause: Rule Engine provider implementation for Ilog JRules not found.
Action: Check the configuration file DecisionServicesConfiguration.xml. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36611: Error communicating with Rule Execution Server.
Cause: Rule Execution Server communication error, {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services..

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36612: Unsupported Ilog JRules session provider class
Cause: The rule session provider class {0} is unsupported or does not exist.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36615: Error reading Rule Application Archive.
Cause: Failed to read rule application archive {0} because of {1}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36616: Error creating unmarshaller.
Cause: Failed to create an unmarshaller for {1}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36617: Error unmarshalling metadata from the rule application.
Cause: Failed to unmarshal metadata from {0}.
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36620: Creation of rule session failed.
Cause: Failed to create a rule session for {0} {1}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36621: Error in rule execution.
Cause: Failed to execute rule session {0} {1}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36622: Error in rule execution, issue with remote connection to Rule Execution Server
Cause: Failed to execute rule session {0} because of a remote error. {1}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36623: Error resetting rule session.
Cause: Failed to reset rule session {0} {1}
Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36801: Error initializing the Rule Management Service Factory.
Cause: Attempt to initialize the Rule Management Service Factory failed because of a JAXB error
Action: Refer to the soainfra log files for details and contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36820: Error {0} in Oracle Business Rules.
Cause: Eror {0} occurred in the backend rule engine. The error message is {1}
Action: Fix the error and try again.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36841: Error unmarshalling from org.w3c.dom.Element to JAXB.
Cause: Attempt to unmarshall element {0} using JAXB context {1} resulted in error: {2}
Action: Refer to the soainfra log files for details and contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-36842: Error in rule management service Web service operation invocation
Cause: Error in rule management service Web service operation invocation. The error is {0}.
Action: Verify that the SOAP connection information for the server is correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37001: Error adding List Builder property.
Cause: Failed to add property: {0}
Action: Verify validity of list builder properties.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37002: Error setting starting point implicitly.
Cause: Failed to walk up the hierarchy as requestor or requestor role is already top approver: {0}
Action: Set the starting point explicitly to some one below the top Approver.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37003: Error setting hierarchy provider instance in list builder.
Cause: Failed to set hierarchy provider instance {0} in list builder.
Action: Set the valid hierarchy provider instance in the list builder.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37012: Approval Group is empty.
Cause: The specified Approval Group is empty: {0}
Action: Set the ALLOW_EMPTY_GROUP property to true or populate the Approval Group with members.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37013: Dynamic Approval Group expansion error.
Cause: Couldnot retrieve approvers from the dynamic Approval Group: {0}
Action: Ensure that the Dynamic Approval Group has been correctly implemented.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37014: Approval Group could not be expanded.
Cause: The specified Approval Group could not be expanded to retrieve approvers: {0}
Action: Verify the contents and member list of the Approval Group.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37051: Invalid preference for the list builder.
Cause: Invalid preference set for the list builder: {0}
Action: Set the preference to a value greater than 0.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37052: No voting regime i set for the list builder.
Cause: No voting regime is set for the list builder: {0}
Action: Set the voting regime to a valid value.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37053: Constraint is not set.
Cause: No constraint is set.
Action: Set the constraint to a valid value.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37054: Constraint Level is not valid.
Cause: Constraint Level is not valid.
Action: Set the level to a value greater than 0.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37055: Approval Group name is empty.
Cause: Approval Group name is empty.
Action: Populate the Approval Group name.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37056: Identification key is not found.
Cause: Identification key is not found in the Task object.
Action: Populate the Identification key.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37057: Invalid approver list builder map value.
Cause: The approver list builder map value {0} is invalid.
Action: Verify that the approver list builder map value is correct in the task definition.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37058: Invalid value for xpath expression.
Cause: The xpath expression {0} is invalid for the task.
Action: Verify that the xpath expression is valid for the task data.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37059: Invalid approver list builder constraint value.
Cause: The approver list builder constraint value {0} is invalid.
Action: Verify that the approver list builder constraint value is correct in the task definition.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37100: List Builder had unfulfilled constraints
Cause: The following constraints were unfulfilled: {0}
Action: Verify validity of input properties.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37101: List Builder failed to initialize principal hierarchy
Cause: List Builder could not initialize principal hierarchy service.
Action: Verify availability of user hierarchy service.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37102: List Builder failed while crawling principal hierarchy
Cause: List Builder failed while crawling principal hierarchy.
Action: Verify availability of user hierarchy service and validity of user data.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37103: Service provider failed to initialize.
Cause: Service provider {0} initialization failed.
Action: This error occurs due to error in service provider configuration or if it is not found in config file. Please check configuration for service provider {0} and verify that it is accessible. Please checkactual exception below for more details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37104: Service provider invocation error.
Cause: Failed to invoke web method on Service provider {0} .
Action: This error occurs when service provider is unavailable, unreachable, or if error in configuration.This error may occurs during invocation of web methods of the provider due to above reason. Please check the log file for more specific exception and actual cause of the error.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37105: Service provider class definition error.
Cause: Failed to load the class required for the provider {0} .
Action: This error occurs when a service provider class is not specified correctly in the configuration file. Check the documentation for correct class name for provider {0}.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37106: Service provider could not be loaded.
Cause: Service provider {0} load failed.
Action: This exception occurs when service provider could not be loaded or used as defined in the configurations and the flag mustUseSpecifiedProvider is set to true. Please check configuration for service provider {0} and verify that it is accessible. Please checkactual exception in the log for more details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37150: Approval Management Decision Handler Error - Missing required parameter.
Cause: Missing one or more of the required parameter(s) - {0}.
Action: Make sure parameter is passed properly.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37151: Error while calling Approval Management Prescription Action.
Cause: Calling Approval Management Prescription Action with decision point name {0}, stage name {1}, and rule name {2} result in error {3}.
Action: Verify underlying exception(s) for details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37152: Error while calling Approval Management Decision Service.
Cause: Calling Approval Management Decision Service result in error {0}.
Action: Verify underlying exception(s) for details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37153: Error in invoking the approval management Service.
Cause: Approval management service evaluates the rule in the routing slip corresponding to the task definition {0}. During evaluation of this rule, there was an error. See the underlying exception for details.
Action: See the underlying exception(s) for details.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37154: Payload Error in Approval Management Service.
Cause: Mandatory payload element {0} missing.
Action: Populate the element {0} in the payload.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-37155: No Rule Error in Approval Management Service.
Cause: No valid rule could be found.
Action: Verify the rule setup is correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-38001: Error in invoking activity guide metadata service
Cause: An client side error occured in invoking the activity guide metadata service.
Action: Verify that the connection information of the server is correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-38002: Error in invoking activity guide query service
Cause: An client side error occured in invoking the activity guide query service.
Action: Verify that the connection information of the server is correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-38003: Insufficient privileges to access the activity guide.
Cause: User {0} cannot access the activity guide with ciKey: {1}
Action: Ensure that the user has been granted appropriate privileges to access the activity guide info.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-38004: Insufficient privileges to use the ADMIN assignment filter.
Cause: User {0} does not have the activity guide administration privilege required for the using of the ADMIN assignment filter.
Action: Only users with activity guide administrator privilege can use the ADMIN assignment filter when invoking the activity guide query service.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-38005: Error while querying activity guide instance {0}
Cause: Error while querying activity guide instance {0}
Action: Verify that the parameters passed are correct.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-38006: Runtime error in AG Query Service
Cause: Runtime error in AG Query Service. {0}
Action:

Level: 1

Type: ERROR

Impact: Programmatic

BPM-38007: Invalid input AG display column.
Cause: The column name, {0}, specified in the AG display column list does not map to a valid AG field.
Action: Refer to the AG query service javadoc to find a list of valid AG columns, and make sure that the input AG columns are in the list.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-38101: Activity Guide instance {0} not found in registration cache.
Cause: The Activity Guide instance is not found in the registration cache.
Action: Re-register the activity guide instance.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-38201: Messaging Service cannot create JNDI initial context.
Cause: Messaging service cannot create JNDI context.
Action: Contact your system Administator.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-38202: Messaging Service time out occured on a receive.
Cause: Messaging service receive timed out while waiting on JMS topic.
Action: Confirm that message producer is functioning and message consumer is listening on correct topic.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-38203: Messaging service fail to lookup JMS object {0} in JNDI.
Cause: Messaging service cannot create JNDI object.
Action: Check if the JMS object {0} is configured in JNDI.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39001: Unauthorized user
Cause: User, {0}, is not authorized to finish this operation
Action: Login with appropriate user

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39002: MDS is not supporting versioning
Cause: Configured MDS is not supporting versioning.
Action: Check soa-infra MDS configuration and configure it to point to a store that supports versioning. Ex: database

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39003: Generic MDS Error
Cause: Error occured while performing MDS operation. Error: {0}
Action: Contact system administrator

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39004: SOAP Element conversion error
Cause: Error occured while converting the result object into SOAP message
Action: Contact system administrator

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39005: Empty sandbox name
Cause: Sandbox name cannot be empty
Action: Specify a valid name for the sand box

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39501: Configuration error
Cause: Clients are not configured
Action: Specify a FederatedClient in configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39502: No server name in client configuration
Cause: Client configuration doesn't contain proper server name
Action: Specify a srver name in client configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39504: Duplicate server name in client configuration
Cause: Client configuration contain duplicate names {0}
Action: Specify a correct server name in client configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39505: Client configuration error
Cause: Client configuration error for server {0}
Action: Review server information in client configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39506: Requested client type isn't supported
Cause: Requested client type for server {0} isn't supported
Action: Specify a correct client type for server {0} in client configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39507: No connection to servers
Cause: Either client arn't configured, or there is an issue with the existing client configuration.
Action: Verify that at least one client connection is configured for this application, and that no unresolved ''ConfigurationExceptions'' exceptions are logged.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39508: More items not currently available
Cause: Date are not available from some servers
Action: Check failed servers and client configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39509: Information not currently available
Cause: Information not currently available for all servers
Action: Check failed servers and client configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39510: Server has more data
Cause: Only the first {0} tasks display for this server
Action: Specify a correct client type in client configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39511: Several servers have more data
Cause: Only the first {0} tasks display for these servers
Action: Specify a correct client type in client configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39512: No default server in client configuration
Cause: Confuration needs to have one default server
Action: Specify a correct default server in client configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39513: Duplicate default server in client configuration
Cause: Confuration needs to have only one default server in client configuration
Action: Specify one default server in client configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39514: Cannot find client configuration
Cause: Cannot find client configuration for server {0}
Action: Specify correct server name which can found in client configuration

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39515: Not defined client type
Cause: Request does not specify client type
Action: Specify correct client type

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39516: Encryption issue in client configuration file.
Cause: Encryption failed in client configuration file.
Action: Please verify if the encryption algorithm {0} is supported.Also check if the key is valid and of correct length.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-39517: Decryption issue in client configuration file.
Cause: Decryption failed in client configuration file.
Action: Please verify if the decryption algorithm {0} is supported.Also check if the key is valid and of correct length.

Level: 1

Type: ERROR

Impact: Programmatic

BPM-40001: Calendar not defined
Cause: The calendar with id {0} is not defined
Action: Specify an existing calendar

Level: 1

Type: ERROR

Impact: Programmatic

BPM-40002: OrganizationalUnit not defined
Cause: The OrganizationalUnit with id {0} is not defined
Action: Specify an existing OrganizationalUnit

Level: 1

Type: ERROR

Impact: Programmatic

BPM-40003: Parent OrganizationalUnit not defined
Cause: The Parent OrganizationalUnit with id {0} is not defined
Action: Specify an existing OrganizationalUnit as a parent OrganizationalUnit

Level: 1

Type: ERROR

Impact: Programmatic

BPM-40004: OrganizationalUnit name not specified
Cause: The OrganizationalUnit name for the OrganizationalUnit with id {0} is not specified
Action: Specify the OrganizationalUnit name

Level: 1

Type: ERROR

Impact: Programmatic

BPM-40005: OrganizationalUnit Id not specified
Cause: The Id for OrganizationalUnit is not specified
Action: Specify the OrganizationalUnit Id

Level: 1

Type: ERROR

Impact: Programmatic

BPM-40006: Id for the association between ApplicationRole, OrganizationalUnit, and CalendarRule not specified
Cause: Id for the association between ApplicationRole, OrganizationalUnit, and CalendarRule not specified
Action: Specify the association Id

Level: 1

Type: ERROR

Impact: Programmatic

BPM-40007: CalendarRule for the association between ApplicationRole, OrganizationalUnit, and CalendarRule not specified
Cause: The CalendarRule Id for the association between ApplicationRole, OrganizationalUnit, and CalendarRule not specified
Action: Specify the CalendarRule Id

Level: 1

Type: ERROR

Impact: Programmatic

BPM-40008: OrganizationalUnit for the association between ApplicationRole, OrganizationalUnit, and CalendarRule not specified
Cause: The OrganizationalUnit Id for the association between ApplicationRole, OrganizationalUnit, and CalendarRule not specified
Action: Specify the OrganizationalUnit Id

Level: 1

Type: ERROR

Impact: Programmatic

BPM-40009: Association between ApplicationRole, OrganizationalUnit, and CalendarRule is not defined
Cause: The association between ApplicationRole, OrganizationalUnit, and CalendarRule with Id {0} is not defined
Action: Specify an existing association between ApplicationRole, OrganizationalUnit, and CalendarRule

Level: 1

Type: ERROR

Impact: Programmatic

BPM-40010: OrganizationalUnit with Id {0} exists
Cause: The OrganizationalUnit with the specified Id exists
Action: Specify a unique Id for the OrganizationalUnit

Level: 1

Type: ERROR

Impact: Programmatic

BPM-40011: Association between ApplicationRole, OrganizationalUnit, and CalendarRule with Id {0} exists
Cause: The association between ApplicationRole, OrganizationalUnit, and CalendarRule with the specified Id exists
Action: Specify a unique Id for the association between ApplicationRole, OrganizationalUnit, and CalendarRule

Level: 1

Type: ERROR

Impact: Programmatic