WebSphere Process Server messages     Operating Systems: All supported
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 people assignment service (staff service) is being initialized.
Explanation: This happens when the server is started or the service is started by a WebSphere Application Server system administrator.
User Action: None.

 

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 people assignment service (staff service) is being started.
Explanation: This happens when the server is started or the service is started by a WebSphere Application Server system administrator.
User Action: None.

 

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 people assignment service (staff service) is being stopped.
Explanation: This normally happens when the server is stopped or the service is stopped by a WebSphere Application Server system administrator.
User Action: None.

 

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 people assignment service (staff service) is unavailable.
Explanation: The people assignment service (staff service) has been disabled (by an administrator) and is unavailable.
User Action: Enable the people assignment service (staff service) and try again.

 

CWWBS0005E: An error occurred while reading the people directory configuration (staff plug-in configuration).
Explanation: An error occurred when the people directory configuration (staff plug-in configuration) was read. The configuration data might be corrupt, and the people directory configuration might not work as expected.
User Action: Verify that the people directory provider (staff plug-in provider) and the people directory configuration (staff plug-in configuration) data are correct and try again.

 

CWWBS0006E: An error occurred while configuration for the people directory (staff plug-in configuration) \"{0}\" was being processed.
Explanation: An error occurred when the people directory configuration (staff plug-in configuration) was read. The configuration data might be corrupt, and the people directory configuration might not work as expected.
User Action: Verify that the people directory provider (staff plug-in provider) and people directory configuration (staff plug-in configuration) data are correct and try again.

 

CWWBS0007E: The people directory configuration (staff plug-in configuration) \"{0}\" was not created.
Explanation: An error occurred while creating the people directory (staff plug-in) configuration. The configuration data might be corrupt.
User Action: Verify that the people directory provider (staff plug-in provider) and people directory (staff plug-in) configuration data are correct and try again.

 

CWWBS0008E: The people assignment service (staff service) could not look up the people directory (staff plugin) configuration using the name service.
Explanation: The people assignment service (staff service) could not look up the people directory (staff plugin) configuration using the name service.
User Action: Check that the people directory JNDI name (staff plugin JNDI name) is available in the server name space, if not, make sure the people directory (staff plugin) configuration is made available as a people directory (staff plugin) provider resource.

 

CWWBS0009I: Exception trace information: {0}
Explanation: An exception has occurred. This is the exception trace for the 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 error occurred while looking up the JNDI name. The people directory (staff plug-in) configuration that specifies this JNDI name might be incorrect.
User Action: Verify that the people directory (staff plug-in) provider and people directory (staff plug-in) configuration data are correct. Also verify that the people assignment (staff) service is enabled and 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.

 

CWWBS0014E: A people assignment service (staff service) error has occurred: \"{0}\"
Explanation: An error occurred.
User Action: Follow the directions given in this error message and try again.

 

CWWBS0015I: People assignment service (staff service) information: \"{0}\"
Explanation: This is an informational message.
User Action: None.

 

CWWBS0016I: The people directory configuration (staff plug-in configuration \"{0}\" is being bound to \"{1}\".
Explanation: The specified people directory configuration (staff plug-in configuration) is being bound to the specified JNDI name.
User Action: None.

 

CWWBS0017E: The XSL Transform file \"{0}\" was not found.
Explanation: The XSL transform file specified could not be opened.
User Action: Verify that the file exists and that the file name is correct in the people directory (staff plug-in) configuration. Try the operation again.

 

CWWBS0018E: An error occurred while applying the XSL transformation file.
Explanation: An error occurred while applying the XSL transformation file.
User Action: Make sure that the XSL transformation file is correct, and try the operation again.

 

CWWBS0019E: An error occurred while applying the XSL transformation file.
Explanation: An error occurred while applying the XSL transformation file.
User Action: Make sure that the XSL transformation file is correct. Also check the people assignment criteria (staff verb) for correctness. Try the operation again.

 

CWWBS0020E: A people directory (staff plug-in) configuration error \"{0}\" has occurred.
Explanation: An error occurred while the configuration data for the people directory (staff plug-in) provider was being obtained. There are several possible causes for this error: 1. The JAR file was not found. 2. The configuration file was not found in the JAR file. 3. There was a failure while parsing the configuration file.
User Action: Verify that the people directory (staff plug-in) provider specifies the correct JAR file and that the JAR file is not corrupt. Try the operation again.

 

CWWBS0022E: A people assignment criteria (staff verb) mapping error has occurred.
Explanation: A people assignment criteria (staff verb) mapping error has occurred.
User Action: Make sure that the people assignment criteria (staff verb) mapping definition in the XSL transformation file is correct, and try again.

 

CWWBS0023E: An XSL transformation error has occurred.
Explanation: An XSL transformation error has occurred.
User Action: Make sure that the people assignment criteria (verb mapping) definition in the XSL transformation file is correct, and try again.

 

CWWBS0024E: An error occurred during people resolution (staff resolution).
Explanation: An error occurred during people resolution (staff resolution).
User Action: Make sure that the people directory configuration (staff plugin configuration) and the XSL transformation file are correct and try again.

 

CWWBS0025E: Configurations exist for this provider.
Explanation: One or more people directory configurations (staff plug-in configurations) exist for this people directory provider (staff plug-in provider). Deleting this provider will cause all of its configurations to be invalid.
User Action: Delete all of the configurations that depend on this provider, and then try to delete the provider again.

 

CWWBS0027E: The people directory provider (staff plug-in provider) JAR file \"{0}\" has changed.
Explanation: The people directory provider (staff plug-in provider) JAR file has been changed. This might cause the people directory configurations (staff plug-in configurations) that use this staff plug-in provider to fail.
User Action: Replace the changed people directory provider (staff plug-in provider) JAR file with the file that was used when it was created. Alternatively, create and use another people directory provider (staff plug-in provider) that specifies this new JAR file.

 

CWWBS0028E: Unknown type \"{0}\" has been encountered.
Explanation: An unknown type was encountered while configuring the people directory provider (staff plug-in provider).
User Action: Make sure that the people directory configuration (staff plug-in configuration) properties are correct, and try again.

 

CWWBS0029E: A file not found error has occurred: \"{0}\".
Explanation: The specified file was not found.
User Action: Make sure the file exists and try the operation again.

 

CWWBS0030I: The people assignment service (staff service) is disabled.
Explanation: The people assignment service (staff service) has been disabled in the configuration, and it will be inaccessible on the server.
User Action: None.

 

CWWBS0031W: The people assignment service (staff service) is disabled because of previous errors.
Explanation: The people assignment service (staff service) experienced an error during initialization. The service will not be available on the given server. The root error should have been logged previously.
User Action: Resolve the previously logged errors. Restart the server.

 

CWWBS0032I: The people assignment service (staff service) started successfully.
Explanation: The people assignment service (staff service) started successfully.
User Action: None.

 

CWWBS0033E: The people assignment service (staff service) could not resolve the {0} service.
Explanation: The people assignment service (staff service) could not resolve the specified service, which is required for the people assignment service. Review the log to see if the specified service started successfully.
User Action: To use the people assignment service (staff service), correct the problem with the specified service.

 

CWWBS0034E: JAR file {0} cannot be opened.
Explanation: The JAR file cannot be opened because it is using classes that are not in the class path.
User Action: Make sure that all dependent classes are in the class paths of the administrative server and of any application servers that host 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: No action is required. 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 outside the 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: The invocation plug-in class ''{0}'' cannot handle deployed invocation specifications of type ''{1}''.
Explanation: A deployed invocation specification for an unknown type was passed to an invocation plug-in.
User Action: Make sure that the Business Flow Manager 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 specified a service that cannot be resolved.
User Action: Check the service definition for more details.

 

CWWBS0212E: Service ''{0}'' cannot be invoked because the operation ''{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 people directory (staff resolution) plug-in deployment error: {0}
Explanation: An error occurred during the deployment of a people resolution query statement.
User Action: For more information, enable tracing to get a detailed error description.

 

CWWBS0411E: The character ''{0}'' must occur in matching pairs. Error in people (staff) query string: {1}.
Explanation: A syntax error was found in the people query string.
User Action: Check the people query string for errors.

 

CWWBS0412E: The value ''{2}'' is not valid for the attribute ''{0}''. Valid values are: {1}.
Explanation: A bad attribute value was found.
User Action: Check the people (staff) query elements in the human task model and the people assignment criteria (staff verb) mapping XSLT stylesheets for errors.

 

CWWBS0413E: Generic people directory (staff resolution) plug-in runtime error: {0}
Explanation: An error occurred during a people (staff) resolution query.
User Action: To get a more detailed description of the error, enable tracing.

 

CWWBS0414E: The people (staff) query elements 'everybody', 'nobody', and 'userID' are not allowed in an 'intermediateResult' element.
Explanation: These people (staff) query elements produce constant results that have no meaning in intermediate results.
User Action: Use 'user', 'usersOfGroup', or 'search' people (staff) query elements for intermediate results, or use the intended output of this query directly in the follow-on queries.

 

CWWBS0415E: If 'everybody' or 'nobody' is in a 'staffQueries' list, no other people (staff) queries are allowed.
Explanation: These people (staff) query elements allow either everybody or nobody to access the work item, additional user IDs are not meaningful.
User Action: Delete the other people (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 people directory (staff resolution) plug-in.

 

CWWBS0417E: The people directory (staff) plug-in is not available.
Explanation: See the nested exceptions for details.
User Action: See the nested exceptions for details.

 

CWWBS0418E: The Java Naming and Directory Interface (JNDI) initial context is null.
Explanation: No initial context can be obtained from JNDI.
User Action: Check the people directory (staff plug-in) configuration and the specified people directory (staff repository) server.

 

CWWBS0419E: Circular recursion for object "{0}" occurred while processing a Lightweight Directory Access Protocol (LDAP) people (staff) query.
Explanation: Either the people (staff) query specification is wrong or the LDAP directory contains objects that reference each other recursively.
User Action: Check the LDAP directory and the people (staff) query specification.

 

CWWBS0420E: Only one multiple-value variable is allowed per people (staff) query. The affected variables are: "{0}" and "{1}".
Explanation: People (staff) queries that contain more than one variable with multiple values (a string array) are not supported.
User Action: Only use one multiple-valued 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 people (staff) query specification and the content of the Lightweight Directory Access Protocol (LDAP) directory.

 

CWWBS0422W: No Lightweight Directory Access Protocol (LDAP) plug-in configuration parameters are available. Values from the properties file will be used.
Explanation: No LDAP plug-in configuration parameters are available. Values from the properties file will be used.
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, security might be disabled for WebSphere Application Server.
Explanation: A UserRegistry object cannot be obtained from the Lightweight Directory Access Protocol (LDAP) server, security might be disabled for WebSphere Application Server.
User Action: Check the UserRegistry and WebSphere configuration. To run business processes that contain human tasks, you must enable security.

 

CWWBS0427E: The XML element "{0}" has the wrong namespace URI: "{1}". The namespace URI "{2}" was expected.
Explanation: Either the namespace URI or the 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 Lightweight Directory Access Protocol (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 people (staff) query specification and the contents of the LDAP directory.

 

CWWBS0431W: Lightweight Directory Access Protocol (LDAP) syntax error in dn ''{0}''.
Explanation: The specified dn does not conform to the LDAP syntax.
User Action: Check the people (staff) query specification and the contents of the LDAP directory.

 

CWWBS0432W: The attribute ''{0}'' could not be retrieved for the Lightweight Directory Access Protocol (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 people (staff) query specification and the contents of the LDAP directory.

 

CWWBS0433W: The attribute ''{0}'' is empty for the Lightweight Directory Access Protocol (LDAP) object with dn ''{1}''.
Explanation: The LDAP attribute is empty for the LDAP object with the specified dn.
User Action: Check the people (staff) query specification and the contents of the LDAP directory.

 

CWWBS0434W: The Lightweight Directory Access Protocol (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 contents of the LDAP directory.

 

CWWBS0435W: The Lightweight Directory Access Protocol (LDAP) search filter ''{0}'' contains a syntax error.
Explanation: The specified filter does not conform to the LDAP syntax.
User Action: Check the people (staff) query elements in the human task model and the people assignment criteria (staff verb) mapping XSLT stylesheets for errors.

 

CWWBS0436W: Could not retrieve the display name for the user ''{0}''.
Explanation: Either no display name is defined for the user or the User Registry configuration contains errors.
User Action: Check the people directory (staff repository) and the User Registry configuration for errors.

 

CWWBS0437W: Could not retrieve the security name for user ''{0}''.
Explanation: Either no security name is defined for the user or the User Registry configuration contains errors.
User Action: Check the people directory (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 people directory (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 people assignment criteria (staff verb) and the WebSphere Member Manager directory 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 people assignment criteria (staff verb), the WebSphere Member Manager repository, and the configuration.

 

CWWBS0444W: The search attribute reference value ''{0}'' could not be converted into an object of type ''{1}''. Exception message: ''{2}''.
Explanation: The string with the reference value could not be converted into an object of the required type.
User Action: Check the people assignment criteria (staff verb) and its mapping XSLT stylesheet for errors.

 

CWWBS0445W: Caught an exception while resolving a context variable. Exception message: ''{0}''.
Explanation: An exception occurred during the resolution of context variable data.
User Action: Check the context variable name or XPath expression, and the accessed message definition and content.

 

CWWBS0446W: Could not retrieve the User Registry from the Lightweight Directory Access Protocol (LDAP) directory. Possible cause: Security is not enabled for the WebSphere Application Server. Security must be enabled for business processes with human tasks.
Explanation: To be able to run business processes that contain human tasks, WebSphere Application Server security must be enabled.
User Action: Enable WebSphere Application Server security.

 

CWWBS0447W: People resolution 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: Multiple-value context variables are not supported in query attribute or element ''{0}''.
Explanation: Some people (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: The result of a query had an unknown type class: ''{0}''.
Explanation: Unknown result types are converted to strings using their toString() method. This can lead to subsequent errors if this method returns nonsense.
User Action: Use queries that return values of supported types.

 

CWWBS0452E: A mandatory element ''{0}'' with the attribute ''{1}'' set to the value ''{2}'' is missing.
Explanation: A required element occurrence with a predefined attribute value is missing.
User Action: Add the required element containing the expected attribute set to the expected valued.

 

CWWBS0453E: Cannot access the Virtual Member Manager service. Reason: ''{0}''.
Explanation: Access to the Virtual Member Manager service is denied.
User Action: Check the reason for more information. The user ID or password might be invalid.

 

CWWBS0454W: The Virtual Member Manager (VMM) entity ''{0}'' has no attribute with name ''{1}'' of type ''{2}''.
Explanation: A VMM entity did not contain the requested attribute.
User Action: Check that the entity has the requested attribute of the requested type.

 

CWWBS0455E: The Virtual Member Manager (VMM) ''{0}'' has no attribute with name ''{1}'' of type ''{2}''.
Explanation: A VMM entity did not contain the requested attribute.
User Action: Check that the entity has the requested attribute of the requested type.

 

CWWBS0456W: The Virtual Member Manager (VMM) invocation returned no requested result entities.
Explanation: The VMM invocation returned no requested result entities.
User Action: Check the VMM invocation parameters and the contents of the people directory.

 

CWWBS0457W: The Virtual Member Manager (VMM) entity could not be found. The VMM message is ''{0}''.
Explanation: The VMM entity could not be found.
User Action: Check the VMM invocation parameters and the contents of the people directory.

 

CWWBS0458E: The Virtual Member Manager (VMM) entity could not be found. The VMM message is ''{0}''.
Explanation: The VMM entity could not be found.
User Action: Check the VMM invocation parameters and the contents of the people directory.

 

CWWBS0459E: The Virtual Member Manager (VMM) entity type ''{0}'' could not be applied. The VMM message is ''{1}''.
Explanation: The VMM entity type could not be applied to use an entity data object.
User Action: Check the entity type parameters.

 

CWWBS0460E: The Virtual Member Manager (VMM) search expression ''{0}'' could not be applied. The VMM message is ''{1}''.
Explanation: The VMM search expression could not be applied to perform a VMM search operation.
User Action: Check the search expression.

 

CWWBS0461E: The substitution policy ''{0}'' was requested for the ''{1}'' people directory (staff) plug-in. Substitution policies other than ''NoSubstitution'' are only supported by the VMM people directory (staff) plug-in.
Explanation: Substitution policies other than 'NoSubstitution' are only supported by the VMM people directory (staff) plug-in.
User Action: Check the substitution policy that is set in the human task model.

 

CWWBS0462E: The group work item feature is not enabled, groupid queries cannot be deployed without it.
Explanation: A groupid query can only be deployed if the group work item feature is enabled.
User Action: Enable the group work item feature.

 

CWWBS0463E: You cannot combine a single attribute specification with a resultObject specification in people (staff) query ''{0}''.
Explanation: You can either use the single attribute specification or the resultObject specification to adapt the people (staff) query to your LDAP schema, but not a mixture of both.
User Action: Use the resultObject specification. The single attribute specification is deprecated.

 

CWWBS0464W: The attribute ''{0}'' in people (staff) query ''{1}'' is deprecated. Use ''{2}'' instead.
Explanation: This attribute has been deprecated.
User Action: Use the alternative attribute or element that is specified in the message text.

 

CWWBS0465W: The element ''{0}'' in people (staff) query ''{1}'' is deprecated. Use ''{2}'' instead.
Explanation: This element has been deprecated.
User Action: Use the alternative attribute or element thiat is specified in the message text.

 

CWWBS0466E: The destination ''{0}'' is not supported for resultAttribute ''{1}'' in this context. You can use ''{2}'' instead. Reason: ''{3}''.
Explanation: Only the specified destination values are permitted in this context.
User Action: Use one of the listed supported values.

 

CWWBS0467E: Another resultAttribute is already registered for this destination. New attribute name: ''{0}'', Attribute destination: ''{1}''.
Explanation: Only one attribute can be registered for a destination.
User Action: Specify only one resultAttribute per destination inside a resultObject.

 

CWWBS0468E: Another resultObject with the same LDAP objectclass ''{0}'' is already registered for this destination. The containing people (staff) query is: ''{1}''.
Explanation: Only one resultObject can be registered for an LDAP objectclass.
User Action: Specify only one resultObject per LDAP objectclass inside a people (staff) query.

 

CWWBS0469W: The specified threshold for the people (staff) query has been reached, no further results will be included.
Explanation: The specified threshold for the people (staff) query has been reached, no further results will be included.
User Action: If you want more results to be returned for the query, increase the threshold values in your XSL transformation file.

 

CWWBS0470E: Substitution is set to be enabled, but VMM (Federated Repositories) is not configured for WebSphere application security.
Explanation: The substitution feature requires that VMM (Federated Repositories) is configured for WebSphere application security.
User Action: Either disable the substitution feature, or configure VMM (Federated Repositories) for WebSphere application security.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009