- CWWBS0000E: A required attribute ''{0}'' is missing in {1} element.
- Explanation: A required attribute is missing in an FDML extensibility element for data plug-ins.
- User Action: Add the required attribute, then retry.
- CWWBS0000I: The staff service is initializing.
- Explanation: The staff service is being initialized. This usually happens when the server is started.
- User Action: This is an informational message.
- CWWBS0001E: Element {0} must contain one text node, but it contains {1} text nodes.
- Explanation: An FDML extensibility element for data plug-ins contains no text node or more than one text node, and therefore is not valid.
- User Action: Make sure that the extensibility element contains exactly one text node.
- CWWBS0001I: The staff service is starting.
- Explanation: The staff service is being started. This usually happens when the server is started.
- User Action: This is an informational message.
- CWWBS0002E: Error while copying message {0}: {1}
- Explanation: A message could not be copied, for example, when using the Java type system. The message type is neither cloneable nor serializable.
- User Action: Use only message types that can be copied.
- CWWBS0002I: The staff service stopping.
- Explanation: The staff service is being stopped. This usually happens when the server is stopped.
- User Action: This is an informational message.
- CWWBS0003E: Error loading plug-in {0}
- Explanation: A plug-in cannot be loaded.
- User Action: Check the nested exception for the detail error message.
- CWWBS0004E: The staff service is unavailable.
- Explanation: The staff service has been disabled and is unavailable.
- User Action: Enable the staff service and try again.
- CWWBS0005E: Error processing the staff plug-in configuration.
- Explanation: An error occurred while reading the staff plug-in configuration. The configuration data might be corrupt, and the staffplug-in configuration might not work as expected.
- User Action: Verify that the staff plug-in provider and the staff plug-in configuration data are correct and try again.
- CWWBS0006E: Error processing the staff plug-in configuration \"{0}\".
- Explanation: An error occurred while reading the staff plug-in configuration. The configuration data might be corrupt, and thestaff plug-in configuration might not work as expected.
- User Action: Verify that the staff plug-in provider and staff plug-in configuration data are correct and try again.
- CWWBS0007E: The staff plug-in configuration \"{0}\" was not created.
- Explanation: An error occurred while creating the staff plug-in configuration. The configuration data might be corrupt.
- User Action: Verify that the staff plug-in provider and staff plug-in configuration data are correct and try again.
- CWWBS0008E: The staff service encountered a naming exception.
- Explanation: An unexpected naming exception occurred.
- User Action: Check the log for other naming exceptions, verify the configuration, and try again.
- CWWBS0009I: Exception trace information: {0}
- Explanation: An unknown exception has occurred. This is the exception trace for that exception.
- User Action: Review the exception trace to determine the cause of the exception. Verify the installation and try again.
- CWWBS0010E: The JNDI name \"{0}\" was not found.
- Explanation: An unexpected error occurred while binding to the specified JNDI name. The staff service configuration whichspecifies this JNDI name might be incorrect.
- User Action: Verify that the staff plug-in provider and staff plug-in configuration data are correct. Also verify that the staffservice is enabled. Try the operation again.
- CWWBS0011I: Review the activity log.
- Explanation: Something unexpected happened.
- User Action: Review the activity log messages to determine the cause of the problem. Try the operation again.
- CWWBS0013E: Contact IBM Support for additional information.
- Explanation: An unexpected error occurred.
- User Action: Contact IBM Support for more information.
- CWWBS0014E: Staff service error: \"{0}\"
- Explanation: An unexpected error occurred.
- User Action: Follow the directions given in this error message and try again.
- CWWBS0015I: Staff service information: \"{0}\"
- Explanation: This is an informational message.
- User Action: This is an informational message.
- CWWBS0016I: Binding the staff plug-in configuration \"{0}\" to \"{1}\".
- Explanation: The specified staff plug-in configuration is being bound to the specified JNDI name.
- User Action: This is an informational message.
- CWWBS0017E: The XSL Transform file \"{0}\" was not found.
- Explanation: The specified XSL transform file could not be opened.
- User Action: Verify that the file name is correct in the staff plug-in configuration and that the file exists. Try the operationagain.
- CWWBS0018E: Transformer configuration error.
- Explanation: An unknown error occurred while trying to configure the transformer.
- User Action: Verify that the XSL transform file is correct, and try the operation again.
- CWWBS0019E: Transformer error.
- Explanation: An unknown error occurred while trying to transform the staff service query.
- User Action: Verify that the XSL transform file is correct. Also check the verbs used in the query. Try the operation again.
- CWWBS0020E: Staff plug-in provider configuration error \"{0}\".
- Explanation: An error occurred while trying to get the configuration data for the staff plug-in provider. Explanation: 1 - the JAR filewas not found, 2 - the configuration file was not found in the JAR file, 3 - failureparsing the configuration file.
- User Action: Verify that the staff plug-in provider specifies the correct JAR file and the JAR file is not corrupt. Try theoperation again.
- CWWBS0022E: Verb mapping error.
- Explanation: An unexpected error occurred while using a verb mapping.
- User Action: Check the verb mapping, and try again.
- CWWBS0023E: Error in deployStaffQuery.
- Explanation: An unexpected error occurred in deployStaffQuery.
- User Action: Check the verb mapping and the transformation file, and try the operation again.
- CWWBS0024E: Error in resolveStaffQuery.
- Explanation: An unexpected error occurred in resolveStaffQuery.
- User Action: Check the configuration and try again.
- CWWBS0025E: Configurations exist for this provider.
- Explanation: One or more staff plug-in configurations exist for this staff plug-in provider. Deleting thisprovider will cause all of its configurations to be invalid.
- User Action: Delete all of the configurations that are dependent on this provider and then try to delete the provider again.
- CWWBS0027E: The staff plug-in provider JAR file \"{0}\" changed.
- Explanation: The staff plug-in provider JAR file has been changed. This might result in a failure of the staff plug-inconfigurations that use this staff plug-in provider.
- User Action: Replace the changed staff plug-in provider JAR file with the file that was used when it was created. Alternatively, create and use another staff plug-in provider whichspecifies this new JAR file.
- CWWBS0028E: Unknown type \"{0}\"
- Explanation: An unknown type was encountered while configuring the staff plug-in.
- User Action: Check the staff plug-in configuration properties and try again.
- CWWBS0029E: File not found error: \"{0}\"
- Explanation: The specified file was not found.
- User Action: Make sure the file exists and try again.
- CWWBS0030I: The staff service is disabled.
- Explanation: The staff service has been disabled in the configuration, and it will be inaccessible on the server.
- User Action: This is an informational message.
- CWWBS0031W: The staff service is disabled due to previous errors.
- Explanation: The staff service experienced an error during initialization. The service will be inaccessible on the given server.The root error should have been logged previously.
- User Action: Try to resolve the previously logged errors. If you are unable to resolve the errors, contact IBM support.
- CWWBS0032I: The staff service started successfully.
- Explanation: The staff service has been started successfully.
- User Action: This is an informational message.
- CWWBS0033E: The staff service could not resolve the {0} service.
- Explanation: The staff service could not resolve the specified service, which is required for the Staff Service. Look throughthe log to see if the specified service started successfully.
- User Action: To use the staff service, correct the problem with the specified service. If you are unable to correctthe problem, contact IBM support.
- CWWBS0034E: Unable to open JAR file {0}.
- Explanation: Unable to open a JAR file because the JAR file is using classes that are not in the class path.
- User Action: Place all dependent classes in the class path of the administrative server and of any applicationservers hosting the JAR file.
- CWWBS0050E: This schema reference wraps a DTD.
- Explanation: This method cannot retrieve DTDs. DTDs cannot be parsed as XML documents.
- User Action: Check the message type definition in the FDML.
- CWWBS0051E: The Java class loader could not retrieve the file resource ''{0}''.
- Explanation: The Java class loader could not load the file.
- User Action: Check the file name and the classpath.
- CWWBS0052E: The file ''{0}'' could not be parsed.
- Explanation: The XML parser could not parse the file.
- User Action: Check the file name, its content, and the classpath.
- CWWBS0053E: An error occurred while parsing.
- Explanation: An error occurred while parsing a message or schema.
- User Action: Verify the message content.
- CWWBS0054E: The URI ''{0}'' could not be resolved.
- Explanation: The URI could not be resolved. Either the URI is wrong or the message is null.
- User Action: Verify the URI specification and check if the process allows this message to be null.
- CWWBS0055E: The version of the used JVM is lower than version 1.4.
- Explanation: This feature is supported only with JDK version 1.4 or higher.
- User Action: Use JDK 1.4.
- CWWBS0056E: The URI ''{0}'' could not be transformed into a JAXP Source object.
- Explanation: The URI could not be transformed into a JAXP Source object.
- User Action: Check the exception that caused the error.
- CWWBS0057E: Syntax error in XSLT document() function argument: {0}
- Explanation: The argument of the XPath document() function must begin either with single quotes (') or double quotes (").
- User Action: Verify the XPath expression.
- CWWBS0058E: The namespace prefix ''{0}'' could not be resolved to a namespace URI
- Explanation: The namespace prefix could not be resolved to a namespace URI.
- User Action: Verify the XPath expression and the corresponding XML messages. Define all namespaces in the FDML using the 'prefixResolverEntry' tag.
- CWWBS0059W: The XPath expression ''{0}'' accesses a document that is no variable and no processMessage: {1}
- Explanation: The XPath expression accesses a document that is no variable and no processMessage: {1} You cannot precompile such XPath expressions.
- User Action: None. This is a warning for a possible performance issue.
- CWWBS0060E: The element ''{0}'' was expected instead of the element ''{1}''.
- Explanation: The FDML does not correspond with the specification.
- User Action: Check the FDML for errors.
- CWWBS0061E: A condition specification contains no XPath expression.
- Explanation: A condition specification in the FDML contains no XPath expression. The XPath expression must be normal text format in the condition specification.
- User Action: Check the FDML for syntax errors, and add a valid XPath condition.
- CWWBS0062W: The XPath expression ''{0}'' cannot be precompiled because of exception: {1}
- Explanation: The XPath expression cannot be precompiled. An exception occurred while trying to precompile the XPath expression.
- User Action: Check the XPath expression. This is a warning for a possible performance issue.
- CWWBS0063E: An XML Schema or a DTD file must be defined for a system message type that is XML.
- Explanation: An XML Schema or a DTD file must be defined for a system message type that is XML.
- User Action: Check the FDML for syntax errors, and add a valid XML message type definition.
- CWWBS0064E: The XPath expression ''{0}'' cannot be evaluated to a {1} result.
- Explanation: The XPath expression could not be evaluated, or returned a result that cannot be converted into the expected type (class).
- User Action: Verify the XPath expression and the involved messages.
- CWWBS0065E: An exception occurred during the execution of the mapping.
- Explanation: An exception occurred during the execution of the mapping.
- User Action: Check the mapping style sheet and the FDML for logical errors, that is, if the involved messages are null or are not formatted correctly.
- CWWBS0066E: The element with the name ''{0}'' was not found or many occurrences of this element were found.
- Explanation: The FDML does not correspond with the specification.
- User Action: Check the FDML.
- CWWBS0067E: The XSL templates needed for this XML data map could not be created or precompiled.
- Explanation: The XSL templates needed for this XML data map could not be created or precompiled.
- User Action: Check the FDML and the mapping style sheet.
- CWWBS0068E: The DOM Node could not be serialized to an XML stream.
- Explanation: The DOM Node could not be serialized to an XML stream. Note that in this case XML serialization is meant, not Java.
- User Action: Check the FDML and the mapping style sheet.
- CWWBS0069E: No source was found to parse.
- Explanation: An error occurred while parsing. None of the possible fields to specify an XML document contained data.
- User Action: Verify the XML document wrapper construction. Either only the default constructor was used or the constructor arguments were incorrect.
- CWWBS0070E: The wrapped document has not been parsed yet.
- Explanation: The wrapped document has not been parsed yet.
- User Action: Invoking this method makes only sense, if the document has been parsed, has been retrieved using getDocument() and modified outsidethe XML document wrapper.
- CWWBS0071E: Multiple document XPath expressions without URIResolver cannot be executed. XPath expression: {0}
- Explanation: Multiple document XPath expressions without URIResolver cannot be executed.
- User Action: Invoke the API with a URIResolver which is able to resolve all URIs contained in this XPath statement.
- CWWBS0072E: The XPath expression evaluation failed: {0}
- Explanation: The XPath expression evaluation failed.
- User Action: Check the XPath expression and the involved messages.
- CWWBS0073E: The file resource ''{0}'' could not be retrieved by the Java class loader.
- Explanation: The Java class loader could not load the file.
- User Action: Verify the file name and the classpath.
- CWWBS0074E: The namespace prefix ''{0}'' has been found more than once, pointing to different namespace URIs.
- Explanation: The namespace prefix has been found more than once, pointing to different namespace URIs. The prefix is Probably defined in many input messages, pointing to different namespace URIs.
- User Action: Verify the XPath expression and the corresponding XML messages. Make sure that a prefix points only to a single namespace in all documents that are used in this XPath expression.
- CWWBS0075E: The reference message of this condition is null. Condition: ''{0}'', activity template name: ''{1}''.
- Explanation: The reference (base) message of this condition is null.
- User Action: Check the condition specification, and check if the process specification allows this message to be null.
- CWWBS0076E: The reference message of this mapping is null. Mapping reference message: ''{0}'', activity template name: ''{1}''.
- Explanation: The input message for this XSL transformation (mapping) is null.
- User Action: Check the mapping specification, and check if the process specification allows this message to be null.
- CWWBS0077E: An exception occurred during the evaluation of the condition. Condition: ''{0}'', activity template name: ''{1}''.
- Explanation: An exception occurred during the evaluation of the condition. Check the causing exception for details.
- User Action: Check the mapping style sheet and the FDML for logical errors, that is, if the involved messages are null or are not formatted correctly.
- CWWBS0100E: Plug-in error: ''{0}''. Error parameter(s): {1}.
- Explanation: General purpose message used when the product is in service and a new message is needed.
- User Action: Check the exception stack and the error parameters for more information.
- CWWBS0150E: The mapping specification contains no mapping node.
- Explanation: The mapping specification contains no mapping node.
- User Action: Check the FDML for errors.
- CWWBS0151E: The mapping type ''{0}'' is not supported.
- Explanation: The mapping type is not supported.
- User Action: Check the FDML for errors.
- CWWBS0152E: Error while converting data of type ''{0}''.
- Explanation: The instance data for the specified XSD type is incorrect.
- User Action: Check the XPath expressions in the process and the input in the client.
- CWWBS0200E: Exception {1} occurred during invocation deployment in ''{0}''.
- Explanation: The deployment of an implementation failed.
- User Action: Verify that the FDML and WSDL documents are correct.
- CWWBS0201E: Exception {2} occurred while interpreting element {1} in ''{0}''.
- Explanation: An element of an FDML document cannot be interpreted correctly.
- User Action: Verify that the FDML document is correct.
- CWWBS0202E: Exception {1} occurred while reading and interpreting WSDL document in ''{0}''.
- Explanation: An element of a WSDL document cannot be interpreted correctly.
- User Action: Verify that the WSDL document is correct.
- CWWBS0203E: ''{0}'' received parameter ''{1}'' but expected an instance of type ''{2}''.
- Explanation: A parameter contains an instance of an unexpected type.
- User Action: Check the exception stack for more information.
- CWWBS0204E: Exception {1} occurred during implementation invocation in ''{0}''.
- Explanation: An invocation failed due to an unexpected error condition.
- User Action: Check the exception stack for more details about the error source.
- CWWBS0205E: ''{0}'' cannot handle deployed invocation specifications of type ''{1}''.
- Explanation: A deployed invocation specification of an unknown type was passed over to an invocation plug-in.
- User Action: Make sure that the business process container connects to a database that it is compatible with.
- CWWBS0206E: Input message of type ''{1}'' received by ''{0}'' is not compatible with the expected message type ''{2}''.
- Explanation: A wrong input message type was passed when invoking an implementation.
- User Action: Check that the message definitions in WSDL and the message type definitions in FDML match the actual message instance passed to this invocation.
- CWWBS0207E: Web Services Invocation Framework (WSIF) invocation failed with exception {1} detected by ''{0}''.
- Explanation: An exception in the Web Services Invocation Framework (WSIF) was detected.
- User Action: Verify both the invoked service and its WSDL description. Make sure that the service is running and that a connection to the service can be established.
- CWWBS0209E: Service ''{0}'' does not support the selected interaction style ''{1}''.
- Explanation: A service cannot be invoked because it does not support the selected interaction style.
- User Action: Check the service definition for more details.
- CWWBS0211E: Service ''{0}'' cannot be resolved.
- Explanation: An invocation activity specifies a service which cannot be resolved.
- User Action: Check the service definition for more details.
- CWWBS0212E: Service ''{0}'' cannot be invoked because the opertion ''{1}'' cannot be resolved.
- Explanation: A service cannot be invoked because the specified operation cannot be resolved.
- User Action: Check the service definition for more details.
- CWWBS0410E: Generic staff resolution plug-in deployment error: {0}
- Explanation: An error occurred during the deployment of a staff resolution query statement.
- User Action: Enable tracing to get a detailed error description.
- CWWBS0411E: ''{0}'' must occur in pairs. Error in staff query string: {1}.
- Explanation: A syntax error was found in the staff query string.
- User Action: Check the staff query string for errors.
- CWWBS0412E: Attribute ''{0}'' contains an invalid value: ''{2}''. Valid values are: {1}.
- Explanation: An invalid attribute value was found.
- User Action: Check the staff extension elements in the FDML and the staff verb mapping XSLT stylesheets for errors.
- CWWBS0413E: Generic staff resolution plug-in runtime error: {0}
- Explanation: An error occurred during a staff resolution query.
- User Action: Enable tracing to get a detailed description of the error.
- CWWBS0414E: The staff query elements 'everybody', 'nobody', and 'userID' are not allowed in an 'intermediateResult' element.
- Explanation: These staff query elements produce constant results that have no meaning in intermediate results.
- User Action: Use 'user', 'usersOfGroup', or 'search' staff query elements for intermediate results, or use the intended output of this query directly in the follow-on queries.
- CWWBS0415E: No further staff query is allowed if 'everybody' or 'nobody' is used in a 'staffQueries' list.
- Explanation: These staff query elements allow either everybody or nobody to access the work item, additional user IDs are not meaningful.
- User Action: Delete the other staff query elements.
- CWWBS0416E: No configuration parameters were found.
- Explanation: The parameters were neither obtained by the method call, nor stored in the cache.
- User Action: Specify at least the mandatory configuration parameters before using the LDAP staff resolution plug-in.
- CWWBS0417E: The staff plug-in is not available.
- Explanation: See the nested exception for details.
- User Action: See the nested exception for details.
- CWWBS0418E: The JNDI initial context is null.
- Explanation: No initial context can be obtained from JNDI.
- User Action: Check the staff resolution plug-in configuration and the specified staff repository server.
- CWWBS0419E: Circular recursion for object "{0}" occurred while processing an LDAP staff query.
- Explanation: The staff query specification is wrong or the LDAP repository contains objects that reference each other recursively.
- User Action: Check the LDAP repository and the staff query specification.
- CWWBS0420E: Only one multi-value variable is allowed per staff query. Affected variables: "{0}" and "{1}".
- Explanation: Staff queries that contain more than one variable with multiple values (String array) are not supported.
- User Action: Only use one multi-value variable per query.
- CWWBS0421W: Empty intermediate result set: {0}.
- Explanation: The intermediate result set contains no values. This is probably not intended and may lead to erroneous query results.
- User Action: Verify the staff query specification and the LDAP repository content.
- CWWBS0422W: No LDAP plug-in configuration parameters available. Using values from process.properties file.
- Explanation: No LDAP plug-in configuration parameters available. Using values from process.properties file.
- User Action: Verify the LDAP plug-in configuration.
- CWWBS0423E: Syntax error in deployed attribute property: {0}. Colon missing or surplus in unit: {1}
- Explanation: The syntax for the attribute configuration property is wrong.
- User Action: Correct syntax: objectclass1:attribute1,objectclass2:attribute2,....
- CWWBS0424E: Syntax error in deployed attribute property: {0}
- Explanation: The syntax for the attribute configuration property is wrong. See the nested exception for details.
- User Action: Correct the syntax. The correct syntax is: objectclass1:attribute1,objectclass2:attribute2,...
- CWWBS0425E: Empty String is not a valid value for attribute ''{0}'' in element ''{1}''.
- Explanation: An invalid attribute value was found.
- User Action: Specify a valid attribute value.
- CWWBS0426E: The UserRegistry is null.
- Explanation: A UserRegistry object cannot be obtained from JNDI.
- User Action: Check the UserRegistry and WebSphere configuration. Possible cause: Security is not enabled for the WebSphere Application Server. Security must be enabled for business processes with staff support.
- CWWBS0427E: XML element "{0}" has wrong namespace URI: "{1}. Expected namespace URI: "{2}".
- Explanation: The namespace URI or prefix of the specified XML element is wrong.
- User Action: Change the namespace prefix or the namespace URI to the expected namespace URI.
- CWWBS0428E: The Java class of the solicited LDAP attribute is not supported "{0}". Only String-like LDAP attributes are supported. Attribute name: "{1}". LDAP objectclass: "{2}".
- Explanation: Only String-like LDAP attributes are supported as return values of LDAP queries.
- User Action: Specify an LDAP attribute as return value that is a String.
- CWWBS0429E: An LDAP attribute is already registered for this object class. New attribute name: ''{0}'', Attribute objectclass: ''{1}''.
- Explanation: Only one attribute can be registered for an LDAP object class.
- User Action: Specify only one LDAP attribute per object class.
- CWWBS0430W: The LDAP object with dn ''{0}'' could not be found.
- Explanation: The LDAP object with the specified dn could not be retrieved.
- User Action: Check the staff query specification and the LDAP repository content.
- CWWBS0431W: LDAP syntax error in dn ''{0}''.
- Explanation: The specified dn does not correspond to the LDAP syntax.
- User Action: Check the staff extension elements in the FDML and the staff verb mapping XSLT stylesheets for errors.
- CWWBS0432W: The attribute ''{0}'' could not be retrieved for the LDAP object with dn ''{1}''.
- Explanation: The LDAP object with the specified dn does not contain an attribute with the specified name.
- User Action: Check the staff query specification and the LDAP repository content.
- CWWBS0433W: The attribute ''{0}'' is empty for the LDAP object with dn ''{1}''.
- Explanation: The LDAP attribute is empty for the LDAP object with the specified dn.
- User Action: Check the staff query specification and the LDAP repository content.
- CWWBS0434W: The LDAP search with the base dn ''{0}'' and the filter value ''{1}'' returned no objects.
- Explanation: The LDAP search did not return any values.
- User Action: Check the search base dn, the search filter, and the LDAP repository content.
- CWWBS0435W: Syntax error in LDAP search filter ''{0}''.
- Explanation: The specified filter does not correspond to the LDAP syntax.
- User Action: Check the staff extension elements in the FDML and the staff verb mapping XSLT stylesheets for errors.
- CWWBS0436W: Could not retrieve the display name for user ''{0}''.
- Explanation: The specified user has no display name defined or the User Registry configuration has errors.
- User Action: Check the staff repository and the User Registry configuration for errors.
- CWWBS0437W: Could not retrieve the security name for user ''{0}''.
- Explanation: The specified user has no corresponding security name or the User Registry configuration has errors.
- User Action: Check the staff repository and the User Registry configuration for errors.
- CWWBS0438W: Could not retrieve the group with the name ''{0}''.
- Explanation: The specified group could not be found.
- User Action: Check the staff repository and the User Registry configuration for errors.
- CWWBS0439E: Unknown User Registry type.
- Explanation: A User Registry must be configured.
- User Action: Check your User Registry configuration for errors.
- CWWBS0440E: A search attribute is already registered. Attribute name: ''{0}''.
- Explanation: Only one search attribute can be registered for a given attribute name.
- User Action: Specify each search attribute only once.
- CWWBS0441E: A return type is already registered. Return type: ''{0}'', attribute name: ''{1}''.
- Explanation: Each return type can only be registered once.
- User Action: Specify each return type only once.
- CWWBS0442W: Exception in WebSphere Member Manager method ''{0}''. Input parameter: ''{1}'', Exception message: ''{2}''.
- Explanation: An error occurred during the WebSphere Member Manager API call.
- User Action: Check the staff verb, as well as the WebSphere Member Manager repository and configuration for errors.
- CWWBS0443W: The WebSphere Member Manager member ''{0}'' could not be found. Exception message: ''{1}''.
- Explanation: An error occurred during the WebSphere Member Manager API call.
- User Action: Check for errors in the staff verb, the WebSphere Member Manager repository, and the configuration.
- CWWBS0444W: The search attribute reference value ''{0}'' could not be converted in an object of type ''{1}''. Exception message: ''{2}''.
- Explanation: The string with the reference value could not be converted into an object of the solicited type.
- User Action: Check the staff verb and its mapping XSLT stylesheet for errors.
- CWWBS0445W: Caught exception during context variable resolution. Exception message: ''{0}''.
- Explanation: An exception occurred during the resolution of context variable data.
- User Action: Check the context variable name or XPath expression, as well as the accessed message definition and content.
- CWWBS0446W: Could not retrieve the User Registry from JNDI. Possible cause: Security is not enabled for the WebSphere Application Server. Security must be enabled for business processes with staff support.
- Explanation: WebSphere Application Server security must be enabled for business processes with staff support.
- User Action: Enable WebSphere Application Server security.
- CWWBS0447W: Staff warning: ''{0}''. Warning parameter(s): {1}.
- Explanation: General purpose message used when the product is in service and a new message is needed.
- User Action: Check the warning message for a description of the warning.
- CWWBS0448E: Cannot access the WebSphere Member Manager EJB. Reason: ''{0}''.
- Explanation: Access to the WebSphere Member Manager EJB is denied.
- User Action: Check the reason for more information. The user ID or password may be invalid.
- CWWBS0449E: Multi-value context variables are not supported in query attribute or element ''{0}''.
- Explanation: Some staff queries cannot be performed if context variables resolve to more than one value.
- User Action: Only use context values that resolve to a single value for this query attribute or element.
- CWWBS0450W: Unknown query result type class: ''{0}''.
- Explanation: Unknown result types are converted to Strings using their toString() method. This may lead to subsequent errors if this method returns nonsense.
- User Action: Use queries that return values of supported types.