Explanation | The server configuration could not be read because there is an error in one of the configuration files. |
Action | Resolve the error in the configuration file, then restart the server. |
Explanation | There was an error parsing the specified configuration. |
Action | Resolve the configuration error then retry the action. |
Explanation | An expected configuration property is missing or unspecified, and has been ignored. |
Action | No action is required. |
Explanation | The specified API is not supported. |
Action | Use a supported API. |
Explanation | An optional configuration file could not be found, and will be ignored. |
Action | No action is required. |
Explanation | The specified resource is not valid and has been ignored. |
Action | Make the resource valid if it should not be ignored. |
Explanation | It was not possible to delete the specified resource. |
Action | Resolve any issues preventing deletion of the resource, then retry the action. |
Explanation | It was not possible to create the specified directories. |
Action | Resolve any issues preventing creation of the directories, then retry the action. |
Explanation | The specified factory configuration did not have an ID. |
Action | Specify an ID for the factory configuration. |
Explanation | A previous initialization error has caused the server to shut down. |
Action | Resolve the initialization error, then restart the server. |
Explanation | The configuration is not valid, because of the specified problems. |
Action | Correct the configuration. |
Explanation | The configuration was not removed from the ConfigurationAdmin service. |
Action | No action is required. |
Explanation | The specified configuration could not safely be removed from the ConfigurationAdmin service, because more than one matching configuration was found. |
Action | No action is required. |
Explanation | The server configuration could not be read because there is an XML syntax error in one of the configuration files. |
Action | Resolve the XML syntax error in the configuration document, then restart the server. |
Explanation | One or more configurations could not be updated in ConfigurationAdmin service. |
Action | No action is required. |
Explanation | The server configuration files were changed and the system is attempting to update the server configuration with the new information. |
Action | No action is required. |
Explanation | The system detected changes to the server configuration files, and has updated the server configuration with the new information. |
Action | No action is required. |
Explanation | The server configuration files were modified but no functional configuration changes were detected. |
Action | No action is required. |
Explanation | Metatype extensions must be enabled to allow for nested configurations. |
Action | Add ibm:supportExtensions="true" to the metatype.xml file. |
Explanation | The parent configuration specified in the ibm:parentPid attribute does not exist. |
Action | Correct the ibm:parentPid attribute in the metatype.xml file. |
Explanation | The configuration of pid and factoryPid attributes must be unique. |
Action | Edit the metatype.xml files so that all pid and factoryPid attributes are unique. |
Explanation | The nested configuration does not have a configuration alias. |
Action | Configure a config.alias attribute in the metatype.xml file. |
Explanation | The configuration must be a factory configuration. |
Action | To define a factory configuration, use a factoryPid attribute instead of a pid attribute. |
Explanation | The server configuration data was not successfully stored on disk. |
Action | No action is required. |
Explanation | The server configuration update events were not emitted. |
Action | No action is required. |
Explanation | Multiple metatype definitions share the same alias value. This can result in unpredictable runtime behavior. |
Action | Report the problem to IBM service. |
Explanation | The system timed out while waiting for components to process the new server configuration. |
Action | No action is required. |
Explanation | The contents of the specified resource will be included in the server configuration. |
Action | No action is required. |
Explanation | ibm:reference extension is required for attributes defined with ibm:type=pid. |
Action | Edit corresponding metatype.xml file and add or fix ibm:reference extension. |
Explanation | The pid reference specified in the ibm:reference extension does not exist or is invalid. |
Action | Edit corresponding metatype.xml file and fix the pid name in the ibm:reference extension. |
Explanation | The value for the specified attribute must be unique but it is already being used. |
Action | Change the attribute value so that it is unique. |
Explanation | The specified value for the property cannot be used. |
Action | Correct the value of the property to use an expected value. |
Explanation | The specified value must be an element in the configuration. |
Action | Change the attribute value to reference a valid configuration element. |
Explanation | The target file must be provided on the command line. |
Action | Retry the command and specify a target file. Try using --help for a list of valid options. |
Explanation | The specified option was not recognized. |
Action | Retry the command using valid options. Try using --help for a list of valid options. |
Explanation | Encountered an error during schema generation. |
Action | Investigate the exception |
Explanation | The location of the config jar is incorrect. |
Action | Check that the config jar is located in wlp/lib. |
Explanation | Cannot register an object class twice. |
Action | Remove duplicate object class. |
Explanation | Cannot register a designate twice. |
Action | Remove duplicate designate class. |
Explanation | The file containing the list of pids to exclude was not found. |
Action | Correct the file name and retry the command. |
Explanation | A value for the argument was not found |
Action | Retry the command with the value specified. |
Explanation | One or more configuration includes create a circular dependency. |
Action | Remove the includes that cause the circular dependency. |
Explanation | The designated class will be used to validate the configuration. |
Action | No action is required. |
Explanation | The designated configuration document does not contain a valid signature, or a portion of the document that is protected by the signature has been modified. This message is preceded by an error message that provides more information on the specific error in the document. |
Action | Correct the error in the configuration document that was identified in the preceding error message. |
Explanation | An exception was thrown while attempting to parse the specified configuration document. |
Action | Correct the error in the configuration document that is causing the exception to be thrown and then retry starting the server. |
Explanation | An exception was thrown while attempting to unmarshal the specified configuration document. |
Action | Correct the error in the configuration document that is causing the exception to be thrown and then retry starting the server. |
Explanation | An exception was thrown while attempting to verify that the designated configuration document contains a valid signature. |
Action | Correct the error in the configuration document that is causing the exception to be thrown and then retry starting the server. |
Explanation | A designated configuration document does not contain a signature. |
Action | Replace the designated configuration document with a version of the document that contains a valid signature and then restart the server. |
Explanation | The signature within the designated configuration document does not contain a KeyInfo element. |
Action | Replace the designated configuration document with a version of the document that contains a valid signature and then restart the server. |
Explanation | The signature within the designated configuration document contains an unauthorized certificate. |
Action | Replace the designated configuration document with a version of the document that contains a valid signature and then restart the server. |
Explanation | The signature within the designated configuration document does not contain an X509Data element. |
Action | Replace the designated configuration document with a version of the document that contains a valid signature and then restart the server. |
Explanation | The signature within the designated configuration document does not contain an X509Certificate element. |
Action | Replace the designated configuration document with a version of the document that contains a valid signature and then restart the server. |
Explanation | The protected section within the designated configuration document has been updated. |
Action | Remove the update to the protected section of the designated configuration document and then restart the server. |
Explanation | The signature within the designated configuration document is not valid. |
Action | Replace the designated configuration document with a version of the document that contains a valid signature and then restart the server. |
Explanation | The designated configuration document contains a valid signature. |
Action | No action is required. |
Explanation | The configuration document(s) used to start an embedded server either did not contain an applicationMonitor element or contained an applicationMonitor element that did not disable drop-ins. |
Action | Specify "dropinsEnabled=false" within an applicationMonitor element within one of the configuration documents. |
Explanation | The new configuration document does not contain a valid signature, so the configuration will not be changed. |
Action | Replace the updated configuration document with a version of the document that contains a valid signature and then retry the update. |
Explanation | The missing attribute is required in the configuration file server.xml or one of its referenced configuration files. |
Action | Add the attribute to the configuration file server.xml or one of its referenced configuration files. |
Explanation | An internal error occurred during an attempt to configure the specified persisted identity failed because it extends another persisted identity that was unavailable. |
Action | Ensure that the feature or bundle that provides the missing persisted identity is available in the run time. This is an internal error. Follow standard WebSphere problem determination procedures. |
Explanation | The attribute is declared final. Any reconfiguration attempt will be ignored. |
Action | Do not attempt to reconfigure an attribute that has been marked final. This is an internal error. Follow standard WebSphere problem determination procedures. |
Explanation | The ibm:extends attribute is only applicable to factory persisted identities. |
Action | Reconfigure the persisted identity to use a factory persisted identity or remove the ibm:extends attribute from the object component definition. This is an internal error. Follow standard WebSphere problem determination procedures. |
Explanation | The ibm:extends attribute is only applicable to factory persisted identities. |
Action | Reconfigure the persisted identity to use a factory persisted identity or remove the ibm:extends attribute from the object component definition. This is an internal error. Follow standard WebSphere problem determination procedures. |
Explanation | An attribute in an extending metatype is attempting to rename a non-existent attribute. |
Action | Correct the rename extension to specify an existing attribute. This is an internal error. Follow standard WebSphere problem determination procedures. |
Explanation | An attribute is attempting to override the type of an extended attribute, but attribute types can not be changed by extension attributes. |
Action | The attribute type will automatically be set to original type. To avoid this error re-occurring, correct the type value on the attribute with the rename extension. This is an internal error. Follow standard WebSphere problem determination procedures. |
Explanation | A non-factory persisted identity is attempting to extend another metatype. Only factory persisted identities can use extensions. |
Action | Change the metatype to be a factory, or remove the extensions from the metatype definition. This is an internal error. Follow standard WebSphere problem determination procedures. |
Explanation | The metatype is attempting to extend another metatype that does not exist. |
Action | Change the metatype extension to specify an existing persisted identity. This is an internal error. Follow standard WebSphere problem determination procedures. |
Explanation | An attribute in an extending metatype is attempting to rename a non-existent attribute. |
Action | Correct the attribute name identified in the rename extension to specify an existing attribute. This is an internal error. Follow standard WebSphere problem determination procedures. |
Explanation | The current metatype has an ibm:rename attribute referring to an attribute definition ID that has already been renamed by an extended metatype. |
Action | Change the ibm:rename attribute to a specify a valid attribute definition ID. This is an internal error. Follow standard WebSphere problem determination procedures. |
Explanation | An attribute in metatype has a localized description, but the message cannot be resolved. As a result, the attribute will not be displayed in the message. |
Action | Either use a non-localized metatype description, or ensure the localizations file contains the localized description. |
Explanation | An attribute in metatype has a localized name, but the message cannot be resolved. |
Action | Either use a non-localized metatype name, or ensure the localizations file contains the localized name. |
Explanation | An attribute in metatype is lacking a description. |
Action | Provide a description for the metatype attribute. |
Explanation | An attribute in metatype is lacking a name. |
Action | Provide a name for the metatype attribute. |
Explanation | The specified jar does not contain the required metatype localization files. |
Action | Contact the bundle author to obtain a bundle with the required localization files. |
Explanation | An exception occurred while attempting to update the configuration. |
Action | Check the configuration for errors and attempt the update again. |
Explanation | Validation of the attribute failed. |
Action | Update the configuration to use a valid value for the attribute. |
Explanation | The update of the configuration element failed, but a previous value will continue to be used. |
Action | No action is required. |
Explanation | This is an internal error where the childAlias attribute is only valid when a parentPID attribute is also specified. |
Action | Define the parentPID attribute in the metatype definition. This is an internal error. Follow WebSphere problem determination procedures. |
Explanation | The feature manifest files associated with the specified product extension were not found. |
Action | Verify that the directory where the feature manifests are located is valid. |
Explanation | The product extension cannot be found at the mentioned location. |
Action | Verify that the product installation location is correctly defined in the properties file for the product installation. |
Explanation | The product extension with the specified name does not exist. |
Action | Verify that the specified product extension name is valid. |
Explanation | Validation of the attribute failed. |
Action | Update the configuration to use a valid value for the attribute. |
Explanation | Validation of the attribute failed. |
Action | Update the configuration to use a valid value for the attribute. |
Explanation | The specified value for the property is not valid and cannot be used. The default value is used instead. |
Action | The system will use the default value or you can correct the value of the property to use a valid value. |
Explanation | The specified configuration file is not valid. Usually, this error indicates that the URL is not well formed or contains an unknown protocol. |
Action | Check the URL to ensure it is valid and uses a well known protocol, such as file, http, or https. |
Explanation | A server element is nested inside the top level server element in the XML configuration document. The content within the nested server will be ignored. |
Action | Update the server configuration document to remove the nested server element. |
Explanation | This is an internal error. The reference filter specified on the attribute definition has an invalid syntax. |
Action | The author of the metatype definition should specify a valid reference filter. This is an internal error. |
Explanation | Multiple elements in the configuration are using the same ID attribute. The server cannot determine which element is intended to match the reference. |
Action | Update the configuration so that each element uses a different ID attribute. |
Explanation | The included configuration resource was configured so that conflicts in configuration elements are resolved by either shutting down the server or not allowing a runtime configuration update to take place. |
Action | Either update the included configuration resource to remove the conflicting element or change the conflict resolution behavior to be merge, replace, or ignore rather than break. |
Explanation | An include configuration element is specified in the server configuration, but the element does not specify the location. |
Action | Add the location attribute to the configuration element. |
Explanation | The resource at the specified location is not available. |
Action | Verify that the location attribute is specified correctly and make sure the resource is available. |
Explanation | The server configuration contains a variable configuration element that does not have a name attribute. |
Action | Add a name attribute to the variable. |
Explanation | The server configuration contains a variable configuration element that does not have a value attribute. |
Action | Add a value attribute to the variable. |
Explanation | The contents of the specified resource will be included in the server configuration. |
Action | No action is required. |
Explanation | The include configuration element specifies a value that is not valid. The valid values are: merge, replace, and ignore. |
Action | Update the server configuration to correct the merge behavior. |
Explanation | The missing attribute is required in the configuration file server.xml or one of its referenced configuration files. |
Action | Add the attribute to the configuration file server.xml or one of its referenced configuration files. |
Explanation | The ibm:extendsAlias attribute is only applicable to factory persisted identities that extend another factory persisted identity. |
Action | Reconfigure the persisted identity to use a factory persisted identity or remove the ibm:extendsAlias attribute from the persisted identity. |
Explanation | When you specify an ibm:extendsAlias attribute you must specify an ibm:extends attribute. |
Action | Specify an ibm:extends attribute. |
Explanation | The metatype indicates that a child-first nested element was partly specified. Child-first nested elements must specify both the ibm:parentPid attribute and the ibm:childAlias attribute. |
Action | If this metatype is intended for a child-first nested element, supply the missing attribute. Otherwise, remove the attribute that was provided. |
Explanation | The ibm:extendsAlias attribute must be unique within a single extends hierarchy. |
Action | Make each ibm:extendsAlias attribute unique within the extends hierarchy. |
Explanation | The server specified on the serverSchemaGen command could not be found. You can find expected location of the directory for the server configuration in the message. |
Action | Ensure that you can find the server configuration in the directory provided by the message. If necessary, modify the WLP_USER_DIR or WLP_INSTALL_DIR variables so that the correct path is used to find the server configuration files. |
Explanation | The server specified on the serverSchemaGen command is not configured to accept local JMX requests. |
Action | Ensure that the server configuration includes the localConnector feature, and that the server is started. The URL required to establish a local JMX connection to this server is located in the WLP_USER_DIR/logs/state/com.ibm.ws.jmx.local.address file. |
Explanation | The server specified on the serverSchemaGen command is not configured to accept local JMX requests. The file containing the URL used to create a JMX connection to the server is empty. |
Action | Ensure that the server configuration includes the localConnector feature, and that the server is started. The URL required to establish a local JMX connection to this server is located in the WLP_USER_DIR/logs/state/com.ibm.ws.jmx.local.address file. |
Explanation | The MBean that generates server schema was invoked, but no results were returned. The requested schema might not have been generated. |
Action | Check the server logs and FFDC directory for a possible error message or exception. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The MBean that generates server schema was invoked, but an error was reported while generating schema. The requested schema might not have been generated. |
Action | Check the server logs and FFDC directory for an error message or exception. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The MBean that generates server schema was invoked, but no response code was returned in the result. The requested schema might not have been generated. |
Action | Check the server logs and FFDC directory for a possible error message or exception. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The MBean which generates server schema was invoked, but the output directory used to write the schema was not provided in the response. The requested schema might not have been generated. |
Action | Check the target server output directory for the generated schema. The output directory is specified in the server process by setting the WLP_OUTPUT_DIR variable. The schema is generated into a schemagen directory in the output directory. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The requested server schema was generated and is located in the directory indicated in the message. |
Action | No user action is required. |
Explanation | A JMX connection was established with the target server, but the server schema generation MBean was not found. |
Action | Check the server logs and FFDC directory for a possible error message or exception. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | An unexpected exception was thrown by the server schema generation command. The exception stack trace is printed to the stderr log file. The utility will stop processing. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |