# Troubleshooting

This section lists all of the messages generated by the BPEL Validator. The SA (Static Analysis) column contains hyperlinks to the OASIS WS-BPEL 2.0 specification entry for each validation rule to which the message applies. It is possible that one message is applicable to more than one BPEL element or attribute, therefore all of the SA rules that are relevant are listed for each message.

Refer to the OASIS documentation linked in the SA column for a detailed explanation of the BPEL requirement, and for possible resolutions for the error.

## Note

The substitution parameters (for example: {0} and {1}) are placeholders for the BPEL element, attribute or value identified by the Validator.

## Error messages

Message text | SA
--- | ---
{1} "{2}" of type "{4}" is not compatible with WSDL message "{3}". | 00048 00058 00087
The start activity <{0}> must be the first activity in the process. | 00056
Standard fault "{1}" cannot be handled in <{0}> when exitOnStandardFaults is set to yes. | 00003
The partner link "{1}" referenced from this <{0}> must have "{2}" defined. | 00037
Target scope "{2}" does not exist. | 00077
Target {3} "{2}" must have a compensationHandler or a faultHandler. | 00078
{1,choice,0#Node|1#Activity} <{0}> must contain at least {5,choice,1#one node|1<{5} nodes} from {3} | 02002
The <{1}> node present in this <{0}> has {2,choice,0# unspecified text value (is empty)| 1<="" td=""> | 00038
<{3}> can only occur at most {5,choice,1#one time|1<{5} times} in parent {1,choice,0#node|1#activity} <{0}> | 02002
<{1}> name "{2}" is already defined in this scope/process. | 00018 00023 00044 00064 00068 00069
This <{0}> with name="{1}" was already defined previously | 00022
Cannot import type "{1}" from location "{2}" | 01234
The XSD type "{1}" of {2} "{3}" in this <{0}> is not a simple XSD type. | 00045
This <{0}> uses undefined message part "{1}" in message type "{2}". | 00021
There is no "{2}" message that is used by this <{0}> - {3,choice,0#node <{4}> |2#attribute "{4}"} must be omitted. | 00047
Solicit-response operation "{4}" in portType "{3}" cannot be used in a BPEL process. | 00001
XSD element <{0}> in import {1} conflicts with element of the same name in {2}. | 00014
{1,choice,0#Node|1#Activity} <{0}> must have {2} {3,choice,0#node|1#activity|2#attribute} present. | 00080 00081 00083 00090
The variable name "{1}" is used as a counter name in <{2}>. | 00076
The link "{1}" used as a {0} is not defined in the enclosing flow. | 00065
Scope "{1}" cannot have a <{2}> because because it is itself inside an FCT-hander. | 00079
The <link> "{1}" has a control cycle where the source "{2}" has the target "{3}" as a preceding activity. | 00072
<{0}> cannot be a child of <{1}>; it can only be a child of {2} | 02001
The link "{1}" does not have a source. | 00066
{0} attribute refers to an unsupported language URI {1} | 00004
A catch for fault "{1}" already exist. | 00093
Extension "{1}" is not supported by this implementation. | 00009
{1,choice,0#Node|1#Activity} <{0}> must specify one {3,choice,0#node|1#activity|2#attribute} {2}. | 00081 00090
The attribute {1} must be set to "{2}" on this <{0}> | 00057
Attribute "{0}" must not be set on this <{1}> {2,choice,0#node|1#activity}. | 00046
{3,choice,0#Node|1#Activity|2#Attribute} {2} must not be specified on {1,choice,0#node|1#activity} <{0}>. | 00090
Attribute "{1}" cannot be set because {2} "{3}" is not an element. | 00042
Immediately enclosed {0} "{1}" must have a unique name within the outer scope "{3}". | 00092
"{1}" is set to "{2}" on this <{0}> {4,choice,0#node|1#activity} but it can only be set to {3} | 00017 00032 00046 00090 01001 01010 02003 02004
The {1} of "{2}" is not compatible with {3} of "{4}" - {5} | 00043
Message part "{1}" does not exist in message "{2}" | 00034 00054
partnerLink "{1}" uses portType "{3}" (via partnerLinkType "{2}") which has an overloaded operation "{4}". | 00002
Attribute "{1}" is not set on this <{0}> {2,choice,0#node|1#activity}. | 00000 00010 00024 00032 00046 00047 00081 00088 00090 01001 01004 01010 02003 02004
The <{0}> activity named "{1}" must be in a fault, compensate, or termination handlers. | 00007 00008
The "{1}" cannot be used on <{0}> that does not have {2} defined. | 00017
<{0}> activity "{1}" specifies a portType "{2}", yet this portType does not match the portType derived from "{4}" of partnerLink "{3}" defined in WSDL "{5}" | 00005
Isolated scope "{1}" cannot exist within another isolated scope (scope "{3}"). | 00091
<{0}> activity "{1}" is trying to use partnerLink "{2}" which does not have a "{3}" defined. | 00084
Part "{3}" must be specified on this <{2}> - activity <{1}> requires it. | 00050
The targetNamespace {2} of the imported document is not the default namespace. | 00012
This <{0}> activity is a start activity and cannot have an onAlarm component. | 00062
The import namespace {1} and the imported document target namespace {2} do not match. | 00011
The {1} start activities must share at least one correlation. | 00057
Either "{1}" or "{2}" attribute is required on this <{0}> | 00019 00020
The partner link "{1}" referenced from this <{0}> must have "{2}" defined. | 00035 00036
The <{1}> activity named {0} must be in a fault handler. | 00006
The part "{1}" is already specified in another <{0}>. | 00053
The link "{1}" is not unique - the link "{2}" also makes an identical connection. | 00067
The form of <{0}> is not valid (too many variants detected). | 00032
The variable name "{0}" contains an illegal period (.) character. | 00024
Notification operation "{4}" in portType "{3}" (via partnerLinkType "{2}") cannot be used in a BPEL process. | 00001
The link "{1}" does not have a target. | 00066
The link "{1}" crosses repeatable boundary on <{2}>. | 00070
The "{0}" attribute of this <{1}> is set to "{2}" - it is not a valid NCName. | 00000 00024 01004
Either <{1}> *or* attribute "{2}" must be specified on <{0}>. | 00051 00052 00055 00059 00063 00085
The {1} "{2}" is not of messageType and a "part" is specified in this <{0}> node. | 00034
"{1}" is set to "{3}" on this <{0}> {2,choice,0#|1#activity} but it cannot be resolved (check value of "{1}", imports, WSDLs or XSDs). | 00010 00017 00021 00032 00045 00081 00088 00090 02003 02004
Link "{1}" must be outbound only; target activity must be outside of the enclosing <{2}>. | 00071
Variable "{0}" must be have either messageType,element, or type defined. | 00025
There is no start activity in process "{1}" | 00015
{0} "{1}" must have "{2}" and/or "{3}" set. | 00016

## Warning messages

Message text | SA
--- | ---
The expression in <{0}> cannot be checked - no expression validator has been registered for language {1}. | 00029 00033 01000
The {1} of simple type "{2}" is not compatible with {3} of simple type "{4}" - a BPEL runtime may provide an implicit conversion. | 00043
The {3,choice,0#node|1#activity} <{0}> refers to a {1} (via the attribute "{2}") - this {1} needs to be defined correctly. | 00032 02003 02004

## Information messages

Message text | SA
--- | ---
Copy rule not checked - {1} type-of "{2}", {3} type-of "{4}". | 00043
The {1} of {0} is not defined in BPEL 2.0 and is not understood by this implementation. | 00013