2.2 Messages from KDEC20000 to KDEC39999 : Messages

KDEC20000-E

An attempt to resolve the data source has failed. cause = aa....aa

aa....aa: Error cause code

Description

An attempt to resolve the data source failed. The Possible causes are as follows:

Resolution of the javax.sql.DataSource object failed.
If the cause code is NAME, then name resolution failed.
If the cause code is CLASS, the object type is invalid.

(O)

Check and, if necessary, revise the environment settings so that an appropriate javax.sql.DataSource object is registered in the specified name context.

KDEC20001-E

An error occurred in the DBMS. details = aa....aa

aa....aa: DBMS error message

Description: An error occurred in the DBMS.
(O): Check the DBMS error message, system log information, and DBMS-related error information, and then take appropriate action.

KDEC20002-E

A correlation set is duplicated. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, scope-name = cc....cc, correlation-set-name = dd....dd, correlation-set-value = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Scope name

dd....dd: Correlation set name

ee....ee: Correlation set value

Description: A duplicate correlation set is detected.
(O): Revise the message text (message) flowing in the business process definition or the business process in such a way so that the correlation set is not duplicated.

KDEC20003-E

The value is outside the valid range. kind = aa....aa, business-process-definition-name = bb....bb, business-process-definition-version = cc....cc, scope-name = dd....dd, name = ee....ee, value = ff....ff, details = gg....gg

aa....aa: Value type code

For a correlation set: CORRELATIONSET
For a variable: VARIABLE

bb....bb: Business process definition name

cc....cc: Business process definition version

dd....dd: Scope name

ee....ee: Correlation set name or variable name

ff....ff: Correlation set value or variable value

For a message type variable: Byte length
In other cases: Value

gg....gg: DBMS error message

Description: The correlation set value or variable value exceeds the valid range.
(O): Revise the message text (message) flowing in the business process definition or the business process in such a way so that the correlation set value or variable value does not exceed the valid range.

KDEC20004-E

An attempt to load the definition file has failed. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, file-name = cc....cc

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Definition file name

Description

An attempt to read the business process definition file failed.

The Possible causes are as follows:

The file does not exist.
The user does not have the read permissions.

(O)

Check the specified file name, re-package the business process in the development environment, and then re-deploy the business process in the execution environment. If the problem is not resolved, contact maintenance personnel.

KDEC20005-E

The definition file cannot be parsed. details = aa....aa

aa....aa: Detailed information

Description

The definition file cannot be parsed.

The Possible causes are as follows:

The XML Processor (XML parser) is not available
The business process definition or data definition file cannot be read.

(O)

Check the installed program configuration. If there is no problem, check the settings for the J2EE server running on the HCSC server.

Alternatively, re-package the business process in the development environment, and then re-deploy the business process in the execution environment. If the problem is not resolved, contact maintenance personnel.

KDEC20006-E

The contents of the definition file are incorrect. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, file-name = cc....cc, line-number = dd....dd, details = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Definition file name

dd....dd: Line number

ee....ee: Detailed information

Description

The contents of the definition file are incorrect.

(O)

Check the contents of the specified file name, implement the re-packaging of the business process in the development environment again, and then re-deploy the business process in the execution environment.

The line number indicates the line where the element ends (example: </invoke>).

When checking the attribute value, check the line where the element starts (example: <invoke>) as well.

If the problem is not resolved, contact maintenance personnel.

KDEC20007-E

Evaluation of the expression failed. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, expression = cc....cc, details = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Expression

dd....dd: Detailed information

Description: The XPath expression is inappropriate.
(O): Check the displayed XPath expression.

KDEC20008-E

Evaluation of the function failed. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, function = cc....cc, details = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Extension function name

dd....dd: Detailed information

Description

An attempt to evaluate the extension function failed:

Possible causes are as follows:

An inappropriate extension function has been specified.
An inappropriate argument has been specified.

(O)

Check the displayed extension function.

KDEC20009-E

The message catalog could not be loaded.

Description: The written message resource file could not be read.
(O): Re-install Service Coordinator. If the problem is not resolved, contact maintenance personnel.

KDEC20010-E

The message explaining the problem could not be obtained. message-ID = aa....aa

aa....aa: ID of the message that could not be acquired

Description: The event for the displayed message ID occurred, but the corresponding message could not be obtained.
(O): Take action according to the message indicated in the message ID.

KDEC20012-W

An attempt to start trace output has failed. cause = aa....aa

aa....aa: Error cause

Description: An attempt to start the trace output failed.
(O): Remove the cause of the error on the basis of the error cause.

KDEC20013-E

An error occurred during access to the message container. details = aa....aa

aa....aa: Detailed information

Description: An attempt to access the message container failed.
(O): Reference the error information output before this message.

KDEC20014-E

Parsing of the resource adapter failed. lookup-name = aa....aa, cause = bb....bb

aa....aa: Resource adapter lookup name

bb....bb: Cause

Description

The parsing of the resource adapter failed.

The Possible causes are as follows:

If the cause code is NAME, the name resolution failed.
If the cause code is CLASS, the object type is invalid.

(O)

Check whether the DB Connector settings associated with the resource adapter lookup name are correct.

KDEC20015-E

A JMS exception occurred. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, activity-name = cc....cc, message = dd....dd, code = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Activity name

dd....dd: JMS error message

ee....ee: JMS error code

Description

An error occurred during the JMS processing.

(O)

Make sure that JMS (Reliable Messaging) environment variable settings or operations are correct.

Alternatively, you can check whether the standard reception has been started, please start when it is not activated.

KDEC20016-E

The specified JMS control variable is invalid. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, activity-name = cc....cc, JMS-control-variable-key = dd....dd, JMS-control-variable-type = ee....ee, details = ff....ff

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Activity name

dd....dd: JMS control variable name

ee....ee: JMS control variable type

ff....ff: Detailed information

Description

An unsupported JMS control variable name was specified or the JMS control variable has not been set up.

(O)

Take the following action according to detailed-information:

For NotSupportedKey

Check and, if necessary, revise the JMS control variable name in the business process definition.
For NotFound

Check and, if necessary, revise the JMS control variable name in the business process definition. If the JMS control variable name is correct, make sure that the defined JMS control variable has been set.
For VariableNull

Check and, if necessary, revise the JMS control variable name and type in the business process definition. If the JMS control variable name is correct, make sure that the defined JMS control variable has been set.

KDEC20017-E

The specified value cannot be substituted for the variable. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, activity-name = cc....cc, from-name = dd....dd, from-type = ee....ee, from-scope-name = ff....ff, to-name = gg....gg, to-type = hh....hh, to-scope-name = ii....ii

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Activity name

dd....dd: Source JMS control variable or variable name

ee....ee: Source JMS control variable or variable type

ff....ff: Scope name belonging to the source JMS control variable or variable

gg....gg: Target JMS control variable or variable name

hh....hh: Target JMS control variable or variable type

ii....ii: Scope name belonging to the target JMS control variable or variable

Description: An attempt was made to assign a value that cannot be stored to the JMS control variable or variable.
(O): Check and, if necessary, revise the business process definition so that the target variable type can store the source variable value. Alternatively, make sure that the value used can be stored in the target variable.

KDEC20018-E

The variable type was not convertible for substitution. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, activity-name = cc....cc, from-name = dd....dd, from-type = ee....ee, from-scope-name = ff....ff, to-name = gg....gg, to-type = hh....hh, to-scope-name = ii....ii

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Activity name

dd....dd: Source JMS control variable or variable name

ee....ee: Source JMS control variable or variable type

ff....ff: Scope name belonging to the source JMS control variable or variable

gg....gg: Target JMS control variable or variable name

hh....hh: Target JMS control variable or variable type

ii....ii: Scope name belonging to the target JMS control variable or variable

Description: The type of the source and destination JMS control variable or variable cannot be converted.
(O): Check and, if necessary, revise the business process definition so that the variable type can be converted between the source and target.

KDEC20023-E

A service call failed. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, invoke-activity-name = dd....dd, service-name = ee....ee, details = ff....ff

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: invoke activity name

ee....ee: Service name

ff....ff: Detailed information

Description: An error occurred during the invocation of the service components in the invoke service activity.
(O): Reference the error information output before this message.

KDEC20024-E

An executed 'while' activity exceeded the specified loop limit frequency. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, while-activity-name = cc....cc

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: while activity name

Description: An executed while activity exceeded the specified maximum loop count (loopLimit attribute). The maximum loop count is too small, or the evaluation formula of the conditional expression (condition attribute) for the while activity, or the path of the recursive element specified in the iteration list (iteratorLocation attribute) is incorrect.
(O): Increase the maximum loop count for the while activity. Alternatively, check and, if necessary, revise the XPath expression specified in the conditional expression for the while activity, or the path of the recursive element specified in the iteration list. If the conditional expression or iteration list references a variable, also revise the other activities that affect the value of the variable, and the contents of referenced messages.

KDEC20025-E

A message telegram was received by a 'receive' activity that did not have the waiting-to-receive status. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, receive-activity-name = cc....cc

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: receive activity name

Description

A request was received from a service requester in a receive activity that did not have the waiting-to-receive status.

(O)

Check and revise the business process definition from the following viewpoints or check and revise the service requester that requests the business process:

Is the order of the receive activity in the sequence activity correct?
Is the conditional expression, specified in the transition condition settings (transitionCondition attribute) for the link dialog associated with the receive activity, correct?
Is the request order (order of arrival to reception) from the service requester correct?

KDEC20026-E

A 'reply' activity was executed without the service requester in a waiting-for-response state. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, reply-activity-name = cc....cc, reply-activity-operation-name = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: reply activity name

dd....dd: reply activity operation name

Description

A reply activity was executed when the service requester was not in a waiting-for-response state. The Possible causes are as follows:

The communication model of a receive activity (for example: synchronize attribute) that must be synchronous (yes), is asynchronous (no).
The communication model of a receive activity (for example: synchronize attribute) is asynchronous (no), but a reply activity has been defined.
The location of the reply activity is incorrect.

(O)

Check and, if necessary, revise the business process definition in terms of the above causes.

KDEC20027-E

A business process definition contains a contradiction. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, element-kind = cc....cc, element-information = dd....dd, details = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Type of element in which contradiction was found

dd....dd: Information about element in which contradiction was found

ee....ee: Detailed information

Description

A non-executable contradiction was found in the business process definitions or data definition. The Possible causes are as follows:

A business process definition was changed such that execution could not continue, and then a request that had been generated before the change was executed for a business process instance.
The business process definition was created or changed using a method that is not provided in the development environment.
The business process definition is corrupted.

(O)

Contact a customer engineer.

KDEC20028-E

A fault was not handled by any 'catch' or 'catchAll' element. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, fault-information = cc....cc, activity-name = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Fault information

dd....dd: Name of activity in which the fault occurred

Description

A fault response from a service component, throw activity, or validate activity, or the CSBUserException exception thrown by a Java class was not processed by catch and catch-all defined in the dialog box allocated for fault processing.

(O)

Check and revise the business process definition from the following viewpoints or check and revise the service component or Java class:

Is the fault processing for catch or catch-all missing from the definition in the invoke service activity, invoke java activity, or scope activity?
Does the service component executed in the invoke service activity return a fault defined in the business process definition and service adapter definition?

To revise the service component executed in the invoke service activity, compare the WSDL provided by the service component and the format of the fault message returned by the service component.

To revise the Java class executed by the invoke java activity, check and, if necessary, revise the information specified in the CSBUserException exception thrown by the Java class.

To revise the throw activity or validate activity, check and, if necessary, revise the format of the fault message for the specified variable.

KDEC20029-E

A Java class having the specified name was not found. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, java-activity-name = cc....cc, java-class-name = dd....dd, details = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Invoke java activity name

dd....dd: User class name

ee....ee: Detailed information

Description

The Java class with the specified name was not found in the invoke java activity.

(O)

Check and revise the business process definition from the following viewpoints. If the problem is not resolved, contact maintenance personnel.

Is the user-created Java class that was invoked from the invoke java activity, created or changed using a method that is not provided on the development environment?
Is the business process definition corrupted?
Is there a shortage of resources in the execution environment?

KDEC20030-E

The user-made Java class returned an unallocatable value. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, java-activity-name = cc....cc, java-class-name = dd....dd, output-variable = ee....ee, scope-name = ff....ff

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Invoke java activity name

dd....dd: User class name

ee....ee: Output variable name

ff....ff: Scope name

Description

A user-created Java class returned an unallocatable value in the invoke java activity.

(O)

Check and revise the business process definition or created Java class from the following viewpoints:

Does the type of variable allocated for the return value of the invoke java activity (outputVariable) in the business process definition match the value type returned by the user-created Java class?
Is the return value of the Java class that is invoked from invoke java activity an Object value of a type that is supported by the business process infrastructure?

Make sure that the return value of the Java class has the same type as the variable allocated for return value specified in the invoke java activity of the business process definition.

KDEC20031-E

The user-made Java class returned an unexpected exception. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, java-activity-name = cc....cc, java-class-name = dd....dd, cause-exception = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Invoke java activity name

dd....dd: User class name

ee....ee: Cause exception name

Description: The user-created Java class returned an unexpected exception in the invoke java activity.
(O): Make sure that only CSBUserException or CSBSystemException exceptions are returned in the exception handling of the Java class.

KDEC20032-E

Assignment between the specified types is not supported. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, assign-activity-name = cc....cc, details = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: assign activity name

dd....dd: Error details

Description: In the assign activity, assign processing has been specified for the types that are not supported by the business process infrastructure.
(O): Check and revise the combination of variables or values specified in copy source <from> and copy destination <to>, defined in the assign activity.

KDEC20033-E

A business process definition suitable for starting the business process was not found. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb

aa....aa: Business process definition name

bb....bb: Business process definition version

Description

A business process definition suitable for starting the business process was not found. The possible causes are as follows:

The business process definition was created or changed by a method that is not provided in the development environment.
The business process definition is corrupted.
An attempt was made to execute a business process of a deleted version.
The receive activity of an operation matching with the specified operation name was not found in the execution of the business process by the service requester.

(S)

Processing is interrupted.

(O)

Take the following action:

Make sure that you are not trying to execute a business process of a deleted version.
Review and, if necessary, revise the request messages from the service requester, and specify the receive activity operation name, existing in the business process definition, in the request message.

If the problem is not resolved, contact maintenance personnel.

KDEC20034-E

An invalid type of request was specified for the business process base. business-process-definition-name = aa....aa

aa....aa: Business process definition name

Description

An invalid request type was specified for the business process.

(O)

Check and revise the service requester that invokes the business process from the following viewpoints:

Was an appropriate application used to send the request to the business process infrastructure?
Is RECOVER specified as the request type when the process instance is re-executed?

KDEC20035-E

Processing cannot continue because initialization failed. details = aa....aa

aa....aa: Details of cause

Description

The processing cannot continue because the initialization for starting the business process failed.

(O)

The initialization might have failed due to incorrect HCSC server environment.

Reference the error information output before this message.

If the problem is not resolved, contact maintenance personnel.

KDEC20036-E

Data conversion failed. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, conversion-file-name = cc....cc

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Data transformation definition file name

Description: The data transformation defined in the data transformation (data-transformation) activity failed.
(O): Reference the data transformation-related error information output before this message, and then check and, if necessary, revise the business process definition.

KDEC20037-E

The process instance was deleted during execution of the process. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

Description: The process instance was deleted during the execution of the business process.
(O): Re-send the request from the service requester so that a new process instance is generated, and then executed.

KDEC20038-I

The same message was called twice. JMS-message-ID = aa....aa

aa....aa: Asynchronous message ID

Description: The request from the service requester is invoked twice for the same process instance of the same business process.
(O): No action is needed because the process is being executed when the first request is received by the service requester.

KDEC20039-E

A process instance of the specified correlation set was not found. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, correlation-set-name = cc....cc, correlation-set-value = dd....dd, scope-name = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Correlation set name

dd....dd: Correlation set value

ee....ee: Name of scope to which the correlation set belongs

Description: In the execution of the business process from the service requester, the process instance matching the correlation set value specified in the request message was not found.
(O): Check the request message from the service requester, and specify the correlation set value of an existing process instance in the request message.

KDEC20040-E

The 'receive' activity of the specified operation name was not found. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, operation-name = cc....cc

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Operation name

Description: The receive activity of the operation matching with the specified operation name was not found in the execution of the business process from the service requester.
(O): Check the request message from the service requester, and specify the operation name of the receive activity that exists in the business process definition, in the request message.

KDEC20041-E

Execution processing could not reach the 'receive' activity of the specified operation name. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, operation-name = cc....cc

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Operation name

Description: In the execution of the business process from the service requester, the execution processing could not reach the receive activity of the specified operation name.
(O): Check the business process definition, and correct the business process definition so that the execution processing can reach the receive activity.

KDEC20042-E

Execution processing could not reach the 'reply' activity corresponding to the 'receive' activity. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, receive-activity-name = cc....cc, receive-activity-operation-name = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: receive activity name

dd....dd: receive activity operation name

Description: The execution processing could not reach the reply activity corresponding to the receive activity with the business process definition.
(O): Check the business process definition, and correct the business process definition so that the execution processing can reach the reply activity.

KDEC20043-E

An attempt was made to execute a basic activity before the 'receive' activity. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, activity-name = cc....cc

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Name of the activity to be executed

Description: An attempt was made to execute a basic activity even before the receive activity was executed.
(O): Check the business process definition, and correct the business process definition so that the receive activity is executed first.

KDEC20044-E

The 'receive' activity cannot be received because the specified correlation set is invalid. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, correlation-set-name = dd....dd, scope-name = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Correlation set name

ee....ee: Name of scope to which the correlation set belongs

Description

The requests cannot be received by the receive activity because the correlation set specified in the message is invalid in the execution of the business process from the service requester and the response from the service component.

(O)

Check the request message from the service requester and the response message from the service component, and then specify a valid correlation set value in the message.

Check whether the same correlation set value has been specified in the messages for different process instances.

Also, check whether a request is being sent from the service requester to a correlation set where the process and the processing of the scope in the process is complete and disabled.

KDEC20045-E

The specified correlation set value is invalid. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, correlation-set-name = dd....dd, scope-name = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Correlation set name

ee....ee: Name of scope to which the correlation set belongs

Description

The correlation set value specified in the message is invalid in the execution of the business process from the service requester and the response from the service component.

(O)

Check the request message from the service requester and the response message from the service component, and then specify the correct correlation set value in the message.

Check whether the value in the part specified in the correlation set is Null or null character.

KDEC20046-E

An exception occurred at the start of a transaction. business-process-definition-name = aa....aa, details = bb....bb

aa....aa: Business process definition name

bb....bb: Detailed exception information

Description: An exception occurred while a transaction was being started.
(O): Eliminate the cause of the error in the transaction manager or resource manager based on the displayed detailed exception information.

KDEC20047-E

An exception occurred at the start of a transaction. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, details = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Detailed exception information

Description: An exception occurred while a transaction was being started.
(O): Eliminate the cause of the error in the transaction manager or resource manager based on the displayed detailed exception information.

KDEC20048-E

An exception occurred at the commit of a transaction. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, details = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Detailed exception information

Description: An exception occurred while a transaction was being committed.
(O): Eliminate the cause of the error in the transaction manager or resource manager based on the displayed detailed exception information.

KDEC20049-E

An exception occurred at the rollback of a transaction. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, details = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Details

Description: An exception occurred while a transaction was being rolled back.
(O): Eliminate the cause of the error in the transaction manager or resource manager based on the displayed detailed exception information.

KDEC20051-E

An error occurred at access to a message telegram. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, variable-name = cc....cc, scope-name = dd....dd, details = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Variable name

dd....dd: Name of scope to which the variable belongs

ee....ee: Details

Description: An error occurred when the user message (message), displayed in the variable name, was accessed.
(O): Reference the error information output before this message.

KDEC20052-E

An attempt was made to load the value of an un-initialized variable. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, variable-name = cc....cc, scope-name = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Variable name

dd....dd: Name of scope to which the variable belongs

Description

An attempt was made to read the value of an uninitialized variable among the variables defined in the business process definition.

(O)

Check the business process definition, and then correct the business process definition so that the value of only initialized variable is read.

If the variable type is a message type, the XML data must be stored in the variable before that variable is referenced in the activity.

KDEC20053-E

An attempt was made to substitute a string that cannot be converted to a numeric value. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, to-variable-name = cc....cc, to-variable-type = dd....dd, to-variable-scope-name = ee....ee, details = ff....ff

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Name of target variable

dd....dd: Type of target variable

ee....ee: Name of scope to which the target variable belongs

ff....ff: Details

Description: An attempt was made to substitute a string that cannot be converted to a numeric value when substituting the numeric value for the destination variable with the assign activity.
(O): Correct the source variable (message) so that a value convertible into a numeric value can be substituted or check the definition for the assign activity in the business process definition.

KDEC20054-E

The type of variable cannot be converted. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, from-variable-name = cc....cc, from-variable-type = dd....dd, from-variable-scope-name = ee....ee, to-variable-name = ff....ff, to-variable-type = gg....gg, to-variable-scope-name = hh....hh

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Name of source variable

dd....dd: Type of source variable

ee....ee: Name of scope to which the source variable belongs

ff....ff: Name of target variable

gg....gg: Type of target variable

hh....hh: Name of scope to which the target variable belongs

Description: An attempt was made to substitute a variable of a non-convertible type when substituting a variable for the destination variable with the assign activity.
(O): Check the business process definition, and then correct the assign activity so that a variable of a convertible type will be substituted.

KDEC20055-E

The operation names between the 'receive' activity and the 'reply' activity do not match. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, receive-activity-name = cc....cc, receive-activity-operation-name = dd....dd, reply-activity-name = ee....ee, reply-activity-operation-name = ff....ff

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: receive activity name

dd....dd: receive activity operation name

ee....ee: reply activity name

ff....ff: reply activity operation name

Description

The operation name of the receive activity does not match with the operation name of the corresponding reply activity.

(O)

Check the business process definition, and then correct the settings so that the receive activity operation name and the reply activity operation name matches.

Alternatively, correct the business process definition so that the reply activity matching the receive activity operation name can be reached.

KDEC20056-E

The maximum number of activity instances that can be generated in one process instance was exceeded. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, activity-name = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Activity name

Description

The maximum number of activity instances that can be generated in one process instance was exceeded.

(O)

Delete the corresponding process instance. Subsequently, correct the business process definition so that the maximum number of activity instances that can be generated in one process instance will not be exceeded. The maximum number of activity instances is as follows:

If activitynumber-maximum-compatible=ON: 32,768
If activitynumber-maximum-compatible=OFF: 2,147,483,648

KDEC20057-E

Execution is not possible because the process has completed. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

Description: The processing cannot be executed because the business process is complete.
(O): Send the request to a business process that is not complete.

KDEC20058-E

An attempt to load properties has failed. details = aa....aa

aa....aa: Detailed information

Description

An attempt to read properties failed.

(O)

The HCSC server might not be running. Check the HCSC server status and if the server is not running, start the HCSC server.

If the problem is not resolved, contact maintenance personnel.

KDEC20059-E

An attempt to start log output has failed.

Description: An attempt to start log output failed.
(O): Check and, if necessary, revise the configuration of the installed program. If the problem is not resolved, contact maintenance personnel.

KDEC20060-E

An attempt was made to overwrite a value already set in the correlation set. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, correlation-set-name = dd....dd, scope-name = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Correlation set name

ee....ee: Name of scope to which the correlation set belongs

Description: An attempt was made to overwrite a value already set in the correlation set.
(O): Check and revise the business process definition so that no value will be overwritten in the correlation set.

KDEC20061-E

An error occurred during access to a message telegram, during correlation set processing. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, activity-name = cc....cc, correlation-set-name = dd....dd, details = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Activity name

dd....dd: Correlation set name

ee....ee: Detailed information

Description: An error occurred while a user message (message) was being accessed during the processing of a correlation set.
(O): Reference the error information output before this message.

KDEC20062-E

A correlation set value does not match a telegram information value. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, correlation-set-name = dd....dd, scope-name = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Correlation set name

ee....ee: Name of scope to which the correlation set belongs

Description

The correlation set value in the user message (message) differs from the correlation set value created for each process instance.

(O)

Check and, if necessary, revise the service requester that invokes the business process from the following viewpoints:

Is the correlation set value in the user message (message) changed using the service requester?
During the execution of the business process from the service requester, was the request sent with a correlation set value different from the value used while executing the applicable process instance?

KDEC20063-E

A request message in the message container is invalid. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, element-kind = cc....cc, element-information = dd....dd, details = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Type of invalid element

dd....dd: Name of invalid element

ee....ee: Detailed information

Description: The user message (message) sent with the request from the service requester was blank although the variable attribute is defined in the business process definition.
(O): Check and, if necessary, revise the service requester invoking the business process so that the correct message will be sent.

KDEC20065-E

An attempt was made to load the value of an un-initialized correlation set. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, correlation-set-name = cc....cc, scope-name = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Correlation set name

dd....dd: Name of scope to which the correlation set belongs

Description

An attempt was made to read the value of an uninitialized correlation set in a business process definition.

(O)

Check the business process definition, and correct the business process definition so that the value of only initialized correlation set will be read.

The value must be stored in the correlation set before the correlation set is referenced.

KDEC20066-E

The process instance of the specified correlation set exists, but the 'receive' activity of the specified operation name has completed. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, receive-activity-name = dd....dd, operation-name = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: receive activity name

ee....ee: Operation name

Description

The process instance of the correlation set specified by the service requester exists, but the receive activity of the specified operation name is complete.

(O)

Check, and, if necessary, revise the correlation set specified in the request message from the service requester that invokes the business process.

Alternatively, check the business process definition, and then correct the user message (message) defined in the variable or the business process definition.

KDEC20067-E

The 'invoke' activity has already completed. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, invoke-activity-name = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Invoke activity name

Description

An attempt was made to execute an invoke service activity that is already complete.

(O)

The process instance might have been re-executed in the service invocation for the invoke service activity. Check the time at which the process instance was re-executed.

Alternatively, check whether the process ID specified in the process re-execution utility specifies the correct process for re-execution.

KDEC20068-E

An exception occurred. details = aa....aa

aa....aa: Detailed information (exception class name)

Description: An exception occurred.
(O): Contact a customer engineer.

KDEC20069-I

The evaluation result of the XPath query is an empty string. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, XPath-query = cc....cc

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: XPath query

Description: The evaluation result of the XPath expression is null.
(O): Check whether the XPath expression evaluation result is intended to be a null character.

KDEC20070-E

The user-made Java class threw an exception. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, java-activity-name = dd....dd, details = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Invoke java activity name

ee....ee: Detailed information

Description: The user-created Java class returned an exception inheriting CSBSystemException in the invoke java activity.
(O): Remove the cause of the exception, and then re-execute the process instance.

KDEC20071-E

The combination of the specified process instance ID and the specified process definition name is invalid. process-instance-ID = aa....aa, expected business-process-definition-name = bb....bb, specified business-process-definition-name = cc....cc

aa....aa: Process instance identifier

bb....bb: Expected business process definition name

cc....cc: Specified business process definition name

Description: The business process definition name corresponding to the process instance identifier, specified when a request is made for the re-execution of the process instance, is invalid.
(O): Specify the correct business process definition name from the service requester that invokes the business process.

KDEC20072-E

The 'wait' activity has already completed. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, wait-activity-name = dd....dd, wait-activity-number = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: wait activity name

ee....ee: wait activity number

Description

An attempt was made to process an already complete wait activity.

(O)

An attempt might have been made to execute the process re-execution utility for a running process. Check and, if necessary, revise the following details:

Time at which the process instance was re-executed.
Is the process ID that is specified in the process re-execution utility correct?

KDEC20073-E

The result of evaluating a deadline expression is invalid. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, activity-name = dd....dd, activity-number = ee....ee, expression = (ff....ff), value = (gg....gg), details = (hh....hh)

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Activity name

ee....ee: Activity number

ff....ff: Expression

gg....gg: Evaluation result

hh....hh: Detailed information

Description

The evaluation result of the XPath expression is invalid.

(O)

Check and, if necessary, revise the displayed XPath expression and the evaluation result.

Is the evaluation result of the XPath expression a dateTime type?
Is the evaluation result of the XPath expression within the valid range?

KDEC20074-E

The result of evaluating a duration expression is invalid. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, activity-name = dd....dd, activity-number = ee....ee, expression = (ff....ff), value = (gg....gg), details = (hh....hh)

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Activity name

ee....ee: Activity number

ff....ff: Expression

gg....gg: Evaluation result

hh....hh: Detailed information

Description

The evaluation result of the XPath expression is invalid.

(O)

Check, and if necessary, revise the displayed XPath expression and evaluation result.

Is the evaluation result of the XPath expression a duration type?
Is the evaluation result of the XPath expression within the valid range?

KDEC20075-E

An attempt to access a SessionBean used for process processing has failed. business-process-definition-name = aa....aa, process-instance-ID = bb....bb, activity-number = cc....cc, details = (dd....dd)

aa....aa: Business process definition name

bb....bb: Process instance identifier

cc....cc: Activity number

dd....dd: Detailed information

Description: An error occurred during the invocation of the SessionBean for processing a process.
(O): Reference the error information output before this message.

KDEC20076-E

The 'wait' activity cannot be executed for the process definition is invalid. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, wait-activity-name = dd....dd, wait-activity-number = ee....ee, details = (ff....ff)

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: wait activity name

ee....ee: wait activity number

ff....ff: Detailed information

Description

The method of defining the wait activity is invalid.

(O)

Check and, if necessary, revise the business process definition from the following viewpoints:

Is the wait activity defined for a non-persistent business process?
Is the process defined in such a way so that the wait activity is being executed post the execution of the receive activity until the execution of the reply activity?

KDEC20077-E

An attempt to access a SessionBean used for timer control has failed. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, details = (dd....dd)

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Detailed information

Description: An error occurred during the invocation of the SessionBean for timer control.
(O): Reference the error information output before this message.

KDEC20078-I

The timer has already been registered. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, process-instance-ID = cc....cc, activity-name = dd....dd, activity-number = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Process instance identifier

dd....dd: Activity name

ee....ee: Activity number

Description

The timer registration processing is omitted because the timer has already been registered.

(O)

An attempt might have been made to execute the process re-execution utility for a running process. Check and, if necessary, revise the following details:

Time at which the process instance was re-executed.
Is the correct process ID specified in the process re-execution utility?

KDEC20079-E

An attempt to execute a process instance failed because of a SessionBean used for timer control. business-process-definition-name = aa....aa, process-instance-ID = bb....bb, activity-number = cc....cc, details = (dd....dd)

aa....aa: Business process definition name

bb....bb: Process instance identifier

cc....cc: Activity number

dd....dd: Detailed information

Description: An attempt to execute an activity after the completion of the wait activity, has failed.
(O): Reference the error information output before this message.

KDEC20080-E

An attempt to start the business process failed because the maximum loop count of the 'while' activity is invalid. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, while-activity-name = cc....cc

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: while activity name

Description: The maximum loop count specified for the while activity is invalid.
(O): The maximum while count value that can be set up in the while activity is 2147483647. Check whether the specified value exceeds the maximum while count value.

KDEC20081-E

A header in the message container is invalid. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, element-kind = cc....cc, element-information = dd....dd, details = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Type of the invalid element

dd....dd: Name of the invalid element

ee....ee: Details

Description

The sent user message (header) is invalid. The possible causes are as follows:

The user message (header) sent in the request from the service requester is empty although the variable attribute is defined in the business process definition.
The header corresponding to the root element attribute and namespace attribute, defined in the business process definition, does not exist in the user message (header) sent in the request from the service requester.

(S)

Processing is interrupted.

(O)

Review and, if necessary, revise the processing for invoking the business process. Specify the settings so that the header is sent correctly.

KDEC20082-E

One or more header values are invalid. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, variable-name = cc....cc, scope-name = dd....dd, details = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Variable name

dd....dd: Name of the scope to which the variable belongs

ee....ee: Details

Description

The header allocation variable value defined in the business process definition is invalid. The possible causes are as follows:

The variable value is not initialized.
An empty array is stored in the variable value.
XML parsing is performed for the variable value and an exception occurred.

(S)

Processing is interrupted.

(O)

Review the business process definition and make sure that the variable value is correct.

KDEC20083-E

An attempt was made to acquire from a variable a value that cannot be acquired. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, variable-name = cc....cc, variable-type = dd....dd, message-variable-type = ee....ee, variable-scope-name = ff....ff

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Variable name

dd....dd: Variable type

ee....ee: Type of the message type variable

ff....ff: Name of the scope to which the variable belongs

Description

An attempt was made to obtain an unobtainable value from a variable. The possible causes are as follows:

An attempt was made to obtain a variable value from a message type variable (non-XML, any), with a character string.
An attempt was made to obtain a partial (property) value from the message type variable (any).
An attempt was made to obtain a part (part) value from the message type variable (non-XML, any).

(O)

Specify a value that can be obtained.

KDEC20084-E

The business process definition version of the business process to be executed is invalid. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb

aa....aa: Business process definition name

bb....bb: Business process definition version

Description

An attempt was made to execute a non-executable business process version. The possible causes are as follows:

An attempt was made to execute a business process version which is not the latest version (a business process can be re-executed and a standby asynchronous reception can be executed).

(S)

Processing is interrupted.

(O)

Execute a business process with an executable business process definition version.

If you have changed the business process definition, make sure that the changed information (such as the operation name and the correlation set-related values) is correct.

KDEC20085-I

The definition files will now be cached. business-process-definition-name = aa....aa, definition-file-type = bb....bb, file-num = cc....cc

aa....aa: Business process definition name

bb....bb: Definition file type

formatdef: Format definition
transformdef: Data transformation definition

cc....cc: Number of definition files

Description: The process of caching the format definitions and data transformation definitions in a batch will start.
(S): Processing continues.
(O): If you cannot obtain the expected cache effect, review and, if necessary, revise the formatdef-maxcache-num and transformdef-maxcache-num values based on the number of definition files.

KDEC20086-E

The 'while' activity of the form [List setting] are defined in a persistent business process. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, while-activity-name = cc....cc

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: while activity name

Description

The while activity of the list specification method must be used with the non-persistent business processes, therefore, do not use this while activity with the persistent business processes.

(S)

Processing is interrupted.

(O)

Review and, if necessary, revise the repetition mode of the while activity.

Define the while activity of the list specification method in the non-persistent business processes.

KDEC20087-W

A fault occurred. exception = aa....aa, exception-message = bb....bb, scope-name = cc....cc, activity-name = dd....dd, activity-type = ee....ee, process-instance-ID = ff....ff, root-ap-info = gg....gg, extensions = (hh....hh)

aa....aa: Exception name

bb....bb: Exception message

cc....cc: Scope name

dd....dd: Activity name

ee....ee: Activity type

ff....ff: Process instance identifier

gg....gg: Root application information

hh....hh: Extension information

Description: A fault occurred.
(S): Processing continues.
(O): See the messages displayed before this message, and correct the business process definitions as and when required.

KDEC20088-E

The named charset is invalid. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, activity-name = cc....cc, activity-type = dd....dd, process-instance-ID = ee....ee, root-ap-info = ff....ff

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Activity name

dd....dd: Activity type

ee....ee: Process instance identifier

ff....ff: Root application information

Description: An internal error occurred.
(S): Processing is interrupted.
(O): Contact maintenance personnel.

KDEC20090-W

An unsupported attribute is specified. attribute-name = aa....aa, attribute-value = bb....bb

aa....aa: Attribute name

bb....bb: Attribute value

Description: An unsupported attribute is specified and is ignored.
(S): Processing continues.
(O): Review and, if necessary, revise the business process definition attributes.

KDEC20091-E

A correlation set is duplicated. process-instance-ID = aa....aa, business-process-definition-name = bb....bb, business-process-definition-version = cc....cc, scope-name = dd....dd, correlation-set-name = ee....ee, correlation-set-value = ff....ff, duplicate-process-instance-ID = gg....gg

aa....aa: Process instance identifier

bb....bb: Business process definition name

cc....cc: Business process definition version

dd....dd: Scope name

ee....ee: Correlation set name

ff....ff: Correlation set value

gg....gg: Process instance identifiers (demarcated by commas (,)) with duplicated correlation sets

Description: A duplicated correlation set is detected.
(S): Processing is interrupted.
(O): Make sure that the correlation sets are not duplicated. Execute the cscpiselect command to check for any process instance identifiers with duplicated correlation sets. If such process instance identifiers do not exist, send the request again.

KDEC20092-E

The namespace and root element specified in the header do not match the actual namespace and root element. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, activity-name = cc....cc, activity-type = dd....dd, namespace = ee....ee, root element = ff....ff

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Activity name

dd....dd: Activity type

ee....ee: Namespace

ff....ff: Root element

Description

The part specified with the namespace and the root element in the header allocation variable was not found in the header message.

(S)

If the data validation function is enabled: Processing is interrupted.
If the data validation function is disabled: Processing continues.

(O)

Review and, if necessary, revise the processing for invoking the business processes, and make sure that the header is sent correctly.

KDEC20093-E

The interface implemented by the user-made Java class does not support multiple arguments. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, java-activity-name = cc....cc, java-class-name = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Invoke java activity name

dd....dd: User class name

Description: The variable allocated for multiple arguments is specified for the invoke java activity, but the interface implemented by the user-created Java class does not support multiple arguments.
(S): Processing is interrupted.
(O): Change the interface to be implemented by the Java class to jp.co.Hitachi.soft.csc.bp.receiver.ejb.CustomClassInterfaceM.

KDEC30000-I

Processing for debugging the business process stopped. process-instance-ID = aa....aa

aa....aa: Process instance identifier

Description: The processing for debugging the business process stopped.

KDEC30001-E

An illegal parameter was set while debugging the business process. aa....aa

aa....aa: One of the following description is displayed:

Pattern 1: Process instance identifier = Process instance identifier, name = name, Value = value
Pattern 2: Process instance identifier = Process instance identifier, expression = expression
Pattern 3: Process instance identifier = Process instance identifier, Activity name = Activity name, expression = expression
Pattern 4: Process instance identifier = Process instance identifier, Details = Details

Description

An invalid parameter was set up while the business process was being debugged. The Possible causes are as follows:

A value inappropriate for the data type was specified in the variable update request (when the contents for pattern 1 are displayed).
An invalid XPath expression was specified in the XPath evaluation request (when the contents for pattern 2 are displayed).
The evaluation of the break point conditional expression failed (when the contents for pattern 3 are displayed).
Manual emulation was executed during the suspension of activities other than the invoke service activity (when the contents for pattern 4 are displayed).

(O)

This is an exception message reported to the development environment, when an invalid parameter is set up while debugging the business process. Action need not be taken.

KDEC30002-E

An internal error occurred while debugging the business process. process-instance-ID = aa....aa

aa....aa: Process instance identifier

Description

An internal error occurred while a business process was being debugged. The Possible causes are as follows:

A non-existing instance identifier was specified.
A non-existing variable was specified.
An unexpected exception occurred during the debugging process.

(O)

This is an exception message reported to the development environment, when an internal error occurs while debugging the business process. Contact maintenance personnel.

KDEC30003-E

A fault exception occurred while debugging the business process. process-instance-ID = aa....aa, fault-code = bb....bb, fault-string = cc....cc, fault-actor = dd....dd

aa....aa: Process instance identifier

bb....bb: Fault code

cc....cc: Fault string

dd....dd: Fault actor

Description: A fault exception occurred while a business process was being debugged.
(O): This is an exception message reported to the development environment, when a fault exception occurs while debugging the business process. Check whether the information set up in the development environment is correct.

KDEC30004-E

A system exception occurred while debugging the business process. process-instance-ID = aa....aa, message-ID = bb....bb, message = cc....cc, exception = dd....dd

aa....aa: Process instance identifier

bb....bb: Message ID

cc....cc: Message

dd....dd: Exception name

Description: A system exception occurred while a business process was being debugged.
(O): This is an exception message reported to the development environment, when a system exception occurs while debugging the business process.

KDEC30005-E

Data exceeding the data size limit was received while debugging the business process. process-instance-ID = aa....aa

aa....aa: Process instance identifier

Description: Data exceeding the data size limit was received while a business process was being debugged.
(O): This is an exception message reported to the development environment, when data exceeding the data size limit is received while debugging the business process. Make sure that the correct values are specified in the Debug settings tab in the Debug Configuration dialog box in the development environment.

KDEC30006-E

A communication error occurred while debugging the business process. process-instance-ID = aa....aa

aa....aa: Process instance identifier

Description: A communication error occurred while a business process was being debugged.
(O): This is an exception message reported to the development environment, when a communication error occurs while debugging the business process. Check whether the information set up in the development environment is correct.

KDEC30007-E

A socket connection timeout occurred. host-name = aa....aa, port = bb....bb, timeout = cc....cc, details = dd....dd

aa....aa: Host name

bb....bb: Port number

cc....cc: Connection timeout value

dd....dd: Detailed information

Description: A socket connection timed out while starting the debugging of a business process.
(O): This exception message is issued when a timeout occurs while starting the debugging of the business process. Make sure that there are no problems in the values specified in the Debug settings tab in the Debug Configuration dialog box in the development environment. Also make sure that there is no problem with the network.

KDEC30008-E

A socket connection error occurred. host-name = aa....aa, port = bb....bb, details = cc....cc

aa....aa: Host name

bb....bb: Port number

cc....cc: Detailed information

Description: An error occurred in the socket connection while starting the debugging of a business process.
(O): This exception message is issued when an error occurs in the socket connection while starting the debugging of the business process. Make sure that there are no problems in the values specified in the Debug settings tab in the Debug Configuration dialog box in the development environment. Also make sure that there is no problem in the network.

KDEC35000-E

A database access error occurred. HCSC-cluster-name = aa....aa, table-kind = bb....bb, operation-type = cc....cc, SQL-message = dd....dd, SQL-state = ee....ee, SQL-error-code = ff....ff

aa....aa: HCSC cluster name

bb....bb: Table type

PROCESS: PROCESS table
ACTIVITY: ACTIVITY table/ ACTIVITY table view
CORRELATIONSET: CORRELATIONSET table
LINK: LINK table/ LINK view
BOOL_VARIABLE: BOOL_VARIABLE table/ BOOL_VARIABLE view
STR_VARIABLE: STR_VARIABLE table/ STR_VARIABLE view
NUM_VARIABLE: NUM_VARIABLE table/ NUM_VARIABLE view
MSG_VARIABLE: MSG_VARIABLE table/ MSG_VARIABLE view
MSG_RELATION: MSG_RELATION table

cc....cc: Operation type

INFO: Acquiring the process information
INFO_PID: Acquiring the process instance identifier
INFO_JOIN: Acquiring the process information from the correlation set information
COUNT: Acquiring the relevant number of records of the process information
COUNT_JOIN: Acquiring the relevant number of records of the process information from the correlation set information
DELETE: Delete the process information

dd....dd: SQL error message

ee....ee: SQL status code

ff....ff: SQL error code

Description

A DBMS error occurred. The Possible causes are as follows:

The specified HCSC cluster name or the process information search conditions are invalid.
DBMS error

(O)

Check, and if necessary, revise the specified HCSC cluster name or the process information search condition.

The value of a variable cannot be specified as the search condition for message-type variables.

Check the DBMS error message, system log information, and DBMS-related error information, and then take appropriate action.

KDEC35001-E

Process deletion did not complete because a database access error occurred. HCSC-cluster-name = aa....aa, number of the target process instances to be deleted = bb....bb, number of the deleted process instances = cc....cc, SQL-message = dd....dd, SQL-state = ee....ee, SQL-error-code = ff....ff

aa....aa: HCSC cluster name

bb....bb: Total number of the target process instances to be deleted

cc....cc: Number of the deleted process instances

dd....dd: SQL error message

ee....ee: SQL status code

ff....ff: SQL error code

Description: A DBMS error occurred.
(O): Check the DBMS error message, system log, and DBMS-related error information, and then take appropriate action. To obtain the number of process instances that were not deleted, perform a search with the same conditions as those specified for deletion.

KDEC35002-E

An attempt to connect to the database has failed. JDBC-type = aa....aa, JDBC-url = bb....bb, SQL-message = cc....cc, SQL-state = dd....dd, SQL-error-code = ee....ee

aa....aa: JDBC driver type

bb....bb: Database URL for connecting to the database

cc....cc: SQL error message

dd....dd: SQL status code

ee....ee: SQL error code

Description

An attempt to connect to the DBMS failed.

(O)

Check, and if necessary, revise the database URL.

Make sure that DBMS is running and is ready to be connected.

Check the DBMS error message, system log, and DBMS-related error information, and then take appropriate action.

KDEC35003-E

Initialization of the JDBC driver failed. JDBC-type = aa....aa

aa....aa: JDBC driver type

Description

An attempt to load the JDBC driver failed.

(O)

Check, and if necessary, revise the JDBC driver type.

Make sure that the CLASSPATH environment variable for the JDBC driver, as well as all other environment variables required for the JDBC driver, have been set correctly.

KDEC35004-E

A property value is invalid. property-name = aa....aa, value = bb....bb

aa....aa: Property key of the set up item

bb....bb: Specified property key value

Description: The set up property value is invalid.
(O): Check the setting and set the corresponding item to the correct value.

KDEC35005-E

A parameter value is invalid. argument = aa....aa, value = bb....bb

aa....aa: Incorrect argument name

HCSC-server-name: HCSC server name
business-process-definition-name: Business process definition name
process-instance-ID: Process instance identifier

bb....bb: Specified argument value

Description: The specified argument value is invalid.
(O): Set the correct value for the indicated item.

KDEC35006-E

An executable process was not found. HCSC-cluster-name = aa....aa, business-process-definition-name = bb....bb

aa....aa: HCSC cluster name

bb....bb: Business process definition name

Description: The process that must be re-executed was not found.
(O): Check the re-execution conditions, and then make sure that the business process to be re-executed exists.

KDEC35007-E

An error occurred in process re-execution. J2EE-server-name = aa....aa, HCSC-cluster-name = bb....bb, business-process-definition-name = cc....cc, process-instance-ID = dd....dd, cause = ee....ee

aa....aa: J2EE server name

bb....bb: HCSC cluster name

cc....cc: Business process definition name

dd....dd: Process instance identifier

ee....ee: Error message

Description

An attempt to re-execute the process failed.

(S)

Processing is interrupted.

(O)

Check the -csc option specified for the cscpireexec command, and make sure that the HCSC server to be re-executed is correct.

From the process instance identifier and business process definition name, check the process instance you are trying to re-execute, specify the correct conditions, and then re-execute the cscpireexec command.

Based on the error message, check whether the process can be invoked.

Make sure that the synchronous requester service (EJB) of the HCSC server is running.

Check the log information for the J2EE server that caused the error, and then eliminate the cause of the error.

KDEC35008-E

The message catalog could not be loaded.

Description: The written message resource file could not be read.
(O): Re-install Service Coordinator. If the problem is not resolved, contact maintenance personnel.

KDEC35009-E

The message explaining the problem could not be obtained. message-ID = aa....aa

aa....aa: ID of the message that could not be acquired

Description: The event indicated by the ID occurred, but the corresponding message could not be obtained.
(O): Take an appropriate action according to the message displayed by the message ID.

KDEC35011-W

An attempt to start trace output has failed.

Description: An attempt to start trace output failed.
(O): Check and, if necessary, revise the configuration of the installed program. If the problem is not resolved, contact maintenance personnel.

KDEC35012-E

An attempt to start log output has failed.

Description: An attempt to start log output failed.
(O): Check and, if necessary, revise the configuration of the installed program. If the problem is not resolved, contact maintenance personnel.

KDEC35013-E

An attempt to load properties has failed. HCSC-server-name = aa....aa, cause = bb....bb

aa....aa: HCSC server name

bb....bb: Error reason

Description

An attempt to read the properties failed.

(O)

Check, and if necessary, revise the HCSC server name.

Eliminate the cause of the error on the basis of the indicated cause.

KDEC35014-I

Number of deleted process instances = aa....aa, HCSC-cluster-name = bb....bb

aa....aa: Number of deleted processes

bb....bb: HCSC cluster name

Description: The displayed number of processes were deleted for the specified HCSC cluster.

KDEC35015-W

Database access was cancelled because the specified time has elapsed. HCSC-cluster-name = aa....aa, specified time(sec) = bb....bb, number of the deleted process instances = cc....cc

aa....aa: HCSC cluster name

bb....bb: Specified time

cc....cc: Number of deleted process instances

Description

The access to the database was interrupted because the specified time has elapsed.

(S)

Processing is interrupted.

(O)

Include the undeleted process instances as targets for the next regular deletion process, or re-execute the operation after considering the system load. If this error occurs repeatedly, take one or both of the following actions:

Change the conditions so that the number of process instances to be deleted is reduced.
Increase the interruption time.

KDEC35016-W

Database access was cancelled because the specified time has elapsed. HCSC-cluster-name = aa....aa, specified time(sec) = bb....bb

aa....aa: HCSC cluster name

bb....bb: Specified time

Description

The access to the database was interrupted because the specified time has elapsed.

(S)

Processing is interrupted.

(O)

Take one or both of the following actions:

Change the conditions so that the items to be searched are few.

Increase the interruption time.

KDEC36000-E

An attempt to read the emulation setting information definition file failed. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, activity-name = cc....cc, file-path = dd....dd, details = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Activity name

dd....dd: File path of the definition file for emulated configuration information

ee....ee: Detailed information

Description: An attempt to read the definition file for emulated configuration information failed.
(S): Processing is interrupted.
(O): Make sure that the definition file for emulated configuration information exists. If the file exists, make sure that the file contents are correct.

KDEC36001-E

The emulation setting information definition file includes an invalid setting. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, activity-name = cc....cc, attr-name = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Activity name

dd....dd: Attribute of the definition file for emulated configuration information

Description: Settings in the definition file for emulated configuration information are invalid.
(S): Processing is interrupted.
(O): Specify the correct attribute value in the definition file for emulated configuration information.

KDEC36002-E

An attempt to read the response message file failed. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, activity-name = cc....cc, file-path = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Activity name

dd....dd: File path of the response message file

Description: An attempt to read the response message file failed.
(S): Processing is interrupted.
(O): Make sure that the response message file exists.

KDEC36004-E

An attempt to convert data in the request message failed. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, activity-name = cc....cc, file-path = dd....dd, details = ee....ee

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Activity name

dd....dd: File path of the response message file

ee....ee: Detailed information

Description: An attempt to convert data in the request message failed.
(S): Processing is interrupted.
(O): Based on the detailed information, make sure that the contents of the style sheet specified for the file path of the response message file are correct.

KDEC36005-E

An error occurred during the XPath evaluation. business-process-definition-name = aa....aa, business-process-definition-version = bb....bb, activity-name = cc....cc, details = dd....dd

aa....aa: Business process definition name

bb....bb: Business process definition version

cc....cc: Activity name

dd....dd: Detailed information

Description: An error occurred during XPath evaluation.
(S): Processing is interrupted.
(O): Check and, if necessary, revise the XPath expression specified for the condition attribute in the definition file for emulated configuration information.