WebSphere Application Server Product History Information messages |
WVER0001E: Unable to determine the version directory.
Explanation:
The version directory is located according to java system property ''was.version.dir'', or as ''
User Response:
Make sure that one of the listed java system properties is set. The java system property must be set either through process configuration or as an option to a process launched from the command line.
WVER0002E: Unrecognized product version file extension ''{0}''.
Explanation:
When loading product version information, this information is stored in files having specific extensions. The extensions determine the type of information stored in each file. Valid extensions are ''.websphere'', ''.component'', ''.product'', ''.efix'', and ''.extension''. An attempt was made to load a file containing version information where the extension of the file is not one of the valid extensions.
User Response:
This indicates an internal error.
WVER0003I: Usage: versionInfo ( [ -format
Explanation:
This informational message describes the options to the versionInfo utility program. The versionInfo utility program accepts optional keyword options, one which specifies the output format, one which specifies an output file, one which causes efixes to be displayed, one which causes efix details to be displayed, one which causes components to be displayed, and one which is used to display usage information.
User Response:
No user action is required. The usage information message is displayed upon request.
WVER0004E: Error writing version report to {0}: {1}
Explanation:
The specified error occurred while writing out a version report to the specified file.
User Response:
Corrective action depends on the specifics of the error which occurred. In particular, make sure that the specified file is writable and that sufficient space is available for the report.
WVER0005E: No value was specified for the ''{0}'' option
Explanation:
The listed option requires an value. (Use ''-help'' or ''-usage'' to display usage information.)
User Response:
Specify a value for the listed option.
WVER0006E: The value ''{0}'' is not valid format value.
Explanation:
The valid format values are ''text'' and ''html''. The value specified is not one of these values. (Use ''-help'' or ''-usage'' to display usage information.)
User Response:
Change the format value to one of the valid values, ''text'' or ''html''.
WVER0007E: The option ''{0}'' is not valid.
Explanation:
The specified option is not valid. (Use ''-help'' or ''-usage'' to display usage information.)
User Response:
Change to use a valid option.
WVER0008I: The ''-format'' option specifies the output format, either ''text'' or ''html''. The ''-file'' option specifies an output file. A file name must be provided with the ''-file'' option. The ''-long'' option causes all efix, ptf, and component information to be displayed. The ''-efixes'' option causes efixes to be displayed. The ''-efixDetail'' option causes efix detail to be displayed. The ''-ptfs'' option causes PTFs to be displayed. The ''-ptfDetail'' option causes PTF detail to be displayed. The ''-components'' option causes components to be displayed. The ''-componentDetail'' option causes component detail to be displayed. The ''-help'' option causes help text to be displayed. The ''-usage'' option causes this usage text to be displayed.
Explanation:
The message describes the valid options to the versionInfo utility program.
User Response:
No user action is required. The usage information message is displayed upon request.
WVER0009E: Error writing version report to {0}. The text of the error cannot be displayed, but is of type {1}. A second error, of type {2}, occurred while retrieving the error text.
Explanation:
An error occurred while writing out a version report to the specified file. A second error occurred while retrieving the text of the error.
User Response:
No user action is available. Please retry the requested operation, or contact support for further assistance.
WVER0010I: Copyright (c) IBM Corporation 2002; All rights reserved.
Explanation:
This is a standard copyright statement.
User Response:
No user action is required. This is an informational message.
WVER0011I: WebSphere Application Server Release 5.0
Explanation:
This is a standard product description statement.
User Response:
No user action is required. This is an informational message.
WVER0012I: VersionInfo reporter version {0}, dated {1}
Explanation:
This is a standard module description statement.
User Response:
No user action is required. This is an informational message.
WVER0013E: An exception occurred while reading {0}
Explanation:
Please refer to the nested exception details for further information.
User Response:
Please refer to the nested exception details for further information.
WVER0014E: An exception occurred while reading {0}
Explanation:
Please refer to the nested exception details for further information.
User Response:
Please refer to the nested exception details for further information.
WVER0015E: An exception occurred while processing version information
Explanation:
Please refer to the nested exception details for further information.
User Response:
Please refer to the nested exception details for further information.
WVER0016E: Exceptions occurred while processing version information
Explanation:
Please refer to the nested exception details for further information.
User Response:
Please refer to the nested exception details for further information.
WVER0017E: Unable to determine the update logs directory.
Explanation:
The logs directory is located according to the java system property ''was.version.log.dir'', or as the 'log' directory of the version directory. Neither the ''was.version.log.dir'' property nor the version directory is set.
User Response:
Ensure that the version directory is set, or set the java system property ''was.version.log.dir''.
WVER0018E: Unable to determine the update backups directory.
Explanation:
The backups directory is located according to the java system property ''was.version.backup.dir'', or as the 'log' directory of the version directory. Neither the ''was.version.backup.dir'' property nor the version directory is set.
User Response:
Ensure that the version directory is set, or set the java system property ''was.version.backup.dir''.
WVER0019E: Unable to determine the DTD directory for product version information.
Explanation:
The DTD directory is located according to the java system property ''was.version.dtd.dir'', or as the 'dtd' directory of the version directory. Neither the ''was.version.dtd.dir'' property nor the version directory is set.
User Response:
Ensure that the version directory is set, or set the java system property ''was.version.dtd.dir''.
WVER0021E: Recoverable errors occurred while parsing efix information.
Explanation:
The errors, a list of which follows, occurred while parsing efix information. Refer to the listed errors for additional information.
User Response:
Refer to the listed errors for suggested user actions.
WVER0022E: An error occurred while reading product information. The error is recoverable; parsing was continued. The error occurred in the entity with system ID {0} and public ID {1}, on line number {2} and column number {3}: {4}
Explanation:
The specified entity has structure which is not valid, as described by the specified error. However, the error was not fatal and parsing was continued.
User Response:
The specified file should be reviewed and, if possible, corrected.
WVER0023E: Warnings occurred while parsing product information.
Explanation:
The warnings, a list of which follows, occurred while parsing product information. Refer to the listed warnings for additional information.
User Response:
Refer to the listed warnings for suggested user actions.
WVER0024E: A warning occurred while reading product information. The warning occurred in the entity with system ID {0} and public ID {1}, on line number {2} and column number {3}: {4}
Explanation:
The specified entity has structure which is not valid, as described by the specified warning. However, the warning was not fatal and parsing was continued.
User Response:
The specified file should be reviewed and, if possible, corrected.
WVER0029E: Unable to remove efix {0} stored in file {2}.
Explanation:
The named file could not be removed.
User Response:
Ensure that the target file can be removed.
WVER0030E: Recoverable errors occurred while parsing PTF information.
Explanation:
The errors, a list of which follows, occurred while parsing PTF information. Refer to the listed errors for additional information.
User Response:
Refer to the listed errors for suggested user actions.
WVER0031E: Unable to record the application of PTF {0} on component {1} in file {2}. The named file could not be saved.
Explanation:
The named file could not be saved.
User Response:
Ensure that the target file is writable, and that space is available for a new file.
WVER0035E: Unable to remove PTF {0} stored in file {2}.
Explanation:
The named file could not be removed.
User Response:
Ensure that the target file can be removed.
WVER0040E: The specified version directory ''{0}'' does not exist.
Explanation:
The version directory does not exist.
User Response:
Ensure that the specified directory is a valid product version directory.
WVER0041E: The specified version directory ''{0}'' is not a directory.
Explanation:
The version directory is not a directory.
User Response:
Ensure that the specified directory is a valid product version directory.
WVER0042E: The specified DTD directory ''{0}'' does not exist.
Explanation:
The DTD directory does not exist.
User Response:
Ensure that the specified directory is a valid product DTD directory.
WVER0043E: The specified DTD directory ''{0}'' is not a directory.
Explanation:
The DTD directory is not a directory.
User Response:
Ensure that the specified directory is a valid product DTD directory.
WVER0044E: The specified log directory ''{0}'' could not be created
Explanation:
The DTD directory is not a directory.
User Response:
Ensure that the specified directory is a valid product DTD directory.
WVER0045E: The specified log directory ''{0}'' is not a directory.
Explanation:
The DTD directory is not a directory.
User Response:
Ensure that the specified directory is a valid product DTD directory.
WVER0046E: The specified backup directory ''{0}'' could not be created
Explanation:
The DTD directory is not a directory.
User Response:
Ensure that the specified directory is a valid product DTD directory.
WVER0047E: The specified backup directory ''{0}'' is not a directory.
Explanation:
The DTD directory is not a directory.
User Response:
Ensure that the specified directory is a valid product DTD directory.
WVER0048E: The specified product directory ''{0}'' does not exist.
Explanation:
The product directory does not exist.
User Response:
Ensure that the product directory is a valid product directory.
WVER0049E: The specified product directory ''{0}'' is not a directory.
Explanation:
The product directory is not a directory.
User Response:
Ensure that the specified directory is a valid product directory.
WVER0101E: An exception occurred while loading document {1}, using DTD directory {0}
Explanation:
The noted exception caused the load of the specified document to fail.
User Response:
Particular user action depends on the exception which occurred. In particular, make sure that the specified file is available and has proper format. Contact support for additional information.
WVER0102E: An exception occurred while loading document {1}, using DTD directory {0}. A system ID of {2} and a public ID of {3} was set. The error occurred at line number {4} and column number {5}
Explanation:
The noted exception caused the load of the specified document to fail.
User Response:
Particular user action depends on the exception which occurred. In particular, make sure that the specified file is available and has proper format. Contact support for additional information.
WVER0104E: An exception occurred while creating a root document element of type {0}
Explanation:
The noted exception occurred creating a root document element.
User Response:
Particular user action depends on the exception which occurred. Most often, the configuration of the XML parser is invalid. Make sure that the java system properties do not create an invalid parser configuration. Contact support for additional information.
WVER0105E: An exception occurred while creating an XML model object (of type {0})
Explanation:
The noted exception occurred while attempting to create an XML model object.
User Response:
Particular user action depends on the exception which occurred. Most often, the noted type is not available along the set class path. Contact support for additional information.
WVER0106E: An attempt was made to place an element into an object having simple type {0}
Explanation:
This is an internal error.
User Response:
Constact support for additional information.
WVER0107E: An exception occurred while attempting to write version information to file {0}
Explanation:
The noted exception occurred while attempting to write the specified file.
User Response:
Particular user action depends on the exception which occurred. In particular, make sure that the noted file is writable and that sufficient space is available for the noted file.
WVER0108E: An exception occurred while performing entity resolution, with public ID {0}, system ID {1}, and mapped file name {2}
Explanation:
The noted exception while resolving DTD information while parsing product information. The noted DTD could not be resolved.
User Response:
Particular user action depends on the exception which occurred.
WVER0201E: Unable to determine the history directory; the product directory could not be determined
Explanation:
The history directory is a subdirectory of the product directory. See the explanation for the error that occurred when determining the product directory for more information.
User Response:
Follow the instructions that appear with the version error.
WVER0201E: Missing Attribute ''{0}'' within element of type ''{1}''
Explanation:
The named attribute is not a valid attribute of the specified type of element.
User Response:
Update the XML file to correct the attribute information.
WVER0202E: Unable to load the history information
Explanation:
History information could not be loaded from the history file {0}. Particular details are according to the error that occurred.
User Response:
Make sure that the history file is readable, and has a correct format.
WVER0202E: Unbalanced element structure: Extra element closures.
Explanation:
An XML file containing product information has faulty element structure.
User Response:
Update the XML file to correct the element structure.
WVER0203E: An exception occurred while reading {0}
Explanation:
Please refer to the nested exception details for further information.
User Response:
Please refer to the nested exception details for further information.
WVER0203E: Unbalanced element structure: Missing element closures.
Explanation:
An XML file containing product information has faulty element structure.
User Response:
Update the XML file to correct the element structure.
WVER0204E: An exception occurred while create history directory {0}
Explanation:
Please refer to the nested exception details for further information.
User Response:
Please refer to the nested exception details for further information.
WVER0204E: Element ''{0}'' is not valid as a root element
Explanation:
An XML file containing product information has faulty element structure.
User Response:
Update the XML file to correct the element structure.
WVER0205E: An exception occurred while creating a backup for history file {0} to {1}
Explanation:
Please refer to the nested exception details for further information.
User Response:
Please refer to the nested exception details for further information.
WVER0205E: Element ''{0}'' is not valid within element ''{1}''
Explanation:
An XML file containing product information has faulty element structure.
User Response:
Update the XML file to correct the element structure.
WVER0206E: An exception occurred while writing event history {0}
Explanation:
Please refer to the nested exception details for further information.
User Response:
Please refer to the nested exception details for further information.
WVER0206E: Attempt to close element ''{0}'' while within element ''{1}''
Explanation:
An XML file containing product information has faulty element structure.
User Response:
Update the XML file to correct the element structure.
WVER0210I: Copyright (c) IBM Corporation 2002; All rights reserved.
Explanation:
This is a standard copyright statement.
User Response:
No user action is required. This is an informational message.
WVER0211I: WebSphere Application Server Release 5.0
Explanation:
This is a standard product description statement.
User Response:
No user action is required. This is an informational message.
WVER0212I: HistoryInfo Reporter Version {0}, Dated {1}
Explanation:
This is a standard module description statement.
User Response:
No user action is required. This is an informational message.
WVER0225E: No value was specified for the ''{0}'' argument
Explanation:
The listed argument requires an value. (Use ''-help'' or ''-usage'' to display usage information.)
User Response:
Specify a value for the listed argument.
WVER0226E: The value ''{0}'' is not valid format value.
Explanation:
The valid format values are ''text'' and ''html''. The value specified is not one of these values. (Use ''-help'' or ''-usage'' to display usage information.)
User Response:
Change the format value to one of the valid values, ''text'' or ''html''.
WVER0228E: The argument ''{0}'' is not a valid argument.
Explanation:
The specified argument is not valid. (Use ''-help'' or ''-usage'' to display usage information.)
User Response:
Change the argument to a valid argument.
WVER0230I: Usage: historyInfo ( [ -format
Explanation:
This informational message describes the arguments to the historyInfo utility program. The historyInfo utility program accepts five optional keyword arguments, one which specifies the output format, one which specifies an output file, one which displays only those events which are associated with a specified efix, one which displays only those events which are associated with a specified component, and one which is used to display usage information. (Use ''-usage'' or ''-help'' to display additional information.)
User Response:
No user action is required. The usage information message is displayed upon request.
WVER0231I: The ''-format'' argument is used to specify the output format, which must be specified as one of ''text'' or ''html''. The ''-file'' argument is used to specify an output file. A file name must be provided. The ''-updateId'' argument is used to specify the ID of an update, which will restrict the events which are displayed. The ''-component'' argument is used to specify the name of a component, which will restrict the events which are displayed. The ''-help'' argument is used to display version information. The ''-usage'' argument is used to display this information message.
Explanation:
The message describes the valid arguments to the versionInfo utility program.
User Response:
No user action is required. The usage information message is displayed upon request.
WVER0240E: Error writing version report to {0}: {1}
Explanation:
The specified error occurred while writing out the history report to the specified file.
User Response:
Corrective action depends on the specifics of the error which occurred. In particular, make sure that the specified file is writable and that sufficient space is available for the report.
WVER0241E: Error writing history report to {0}. The text of the error cannot be displayed, but is of type {1}. A second error, of type {2}, occurred while retrieving the error text.
Explanation:
An error occurred while writing out a history report to the specified file. A second error occurred while retrieving the text of the error.
User Response:
No user action is available. Please retry the requested operation, or contact support for further assistance.
WVER0242E: An exception occurred while processing history information
Explanation:
Please refer to the nested exception details for further information.
User Response:
Please refer to the nested exception details for further information.
WVER0243E: Exceptions occurred while processing history information
Explanation:
Please refer to the nested exception details for further information.
User Response:
Please refer to the nested exception details for further information.
WVER0261E: Unable to record the application of efix {0} on component {1} in file {2}. The named file could not be saved.
Explanation:
The named file could not be saved.
User Response:
Ensure that the target file is writable, and that space is available for a new file.
WVER0262E: Unable to record the removal of the application of efix {0} on component {1} in file {2}. The named file could not be saved.
Explanation:
The named file could not be saved.
User Response:
Ensure that the target file is writable, and that space is available for a new file.
WVER0263E: Unable to record the removal of the application of efix {0} on component {1} stored in file {2}. The named file could not be removed.
Explanation:
The named file could not be removed.
User Response:
Ensure that the target file can be removed.
WVER0264E: Unable to record the removal of the application of efix {0} on component {1} -- no application is on record.
Explanation:
The component has no record of an application of the specified efix. The product information may be corrupt, or an internal error may have occurred
User Response:
Please contact support for additional information.
WVER0265E: Unable to remove efix driver {0} stored in file {2}.
Explanation:
The named file could not be removed.
User Response:
Ensure that the target file can be removed.
WVER0266E: Recoverable errors occurred while parsing PTF Driver information.
Explanation:
The errors, a list of which follows, occurred while parsing PTF information. Refer to the listed errors for additional information.
User Response:
Refer to the listed errors for suggested user actions.
WVER0267E: Unable to record the removal of the application of PTF {0} on component {1} in file {2}. The named file could not be saved.
Explanation:
The named file could not be saved.
User Response:
Ensure that the target file is writable, and that space is available for a new file.
WVER0268E: Unable to record the removal of the application of PTF {0} on component {1} stored in file {2}. The named file could not be removed.
Explanation:
The named file could not be removed.
User Response:
Ensure that the target file can be removed.
WVER0269E: Unable to record the removal of the application of PTF {0} on component {1} -- no application is on record.
Explanation:
The component has no record of an application of the specified PTF. The product information may be corrupt, or an internal error may have occurred
User Response:
Please contact support for additional information.
WVER0270E: Unable to remove PTF Driver {0} stored in file {2}.
Explanation:
The named file could not be removed.
User Response:
Ensure that the target file can be removed.
WVER0271E: Unrecognized product history file extension ''{0}''.
Explanation:
When loading history information, this information is stored in files having specific extensions. The extensions determine the type of information stored in each file. Valid extensions are ''.efixDriver'', ''.efixApplied'', ''.ptfDriver'', and ''.ptfApplied''. An attempt was made to load a file containing version information where the extension of the file is not one of the valid extensions.
User Response:
This indicates an internal error.
WVER0272E: An exception occurred while reading {0}
Explanation:
Please refer to the nested exception details for further information.
User Response:
Please refer to the nested exception details for further information.