WebSphere Process Server messages     Operating Systems: All supported

WVER

WVER0001E: Unable to determine the version directory; the ''was.install.root'' Java system property must be set.
Problem The version directory is located according to the ''was.version.dir'' Java system property, or as ''<root>\properties\version'', where <root> is a directory from the ''was.install.root'' Java system property. The error indicates that ''was.install.root'' Java system property is not set, with the consequence that the version directory cannot be determined.
User response Verify that the ''was.install.root'' Java system property is set. The Java system property must be set either through process configuration or as an option to a process that is launched from the command line.
WVER0002E: Unrecognized product version file extension ''{0}''.
Problem 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'', ''.ptf'', 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 <text | html> ] [ -file <output file> ] [ -long ] [ -maintenancePackages ] [ -maintenancePackageDetail ] [ -components ] [ -componentDetail ] ) | ( [ -help | -? | /help | /? | -usage ] )
Problem 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 fixes to be displayed, one which causes fix 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}
Problem 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
Problem 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.
Problem 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.
Problem 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 maintenance package and component information to be displayed. The ''-maintenancePackages'' option causes maintenance packages to be displayed. The ''-maintenancePackageDetail'' option causes maintenance package 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.
Problem 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.
Problem 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, 2005; All rights reserved.
Problem This is a standard copyright statement.
User response No user action is required. This is an informational message.
WVER0012I: VersionInfo reporter version {0}, dated {1}
Problem 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}
Problem 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}
Problem 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
Problem 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
Problem 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.
Problem 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.
Problem 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.
Problem 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 fix information.
Problem The errors, a list of which follows, occurred while parsing fix 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}
Problem 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.
Problem 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}
Problem 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 fix {0} stored in file {2}.
Problem The named file could not be removed.
User response Ensure that the target file can be removed.
WVER0030E: Recoverable errors occurred while parsing maintenance package information.
Problem The errors, a list of which follows, occurred while parsing maintenance package 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 maintenance package {0} on component {1} in file {2}. The named file could not be saved.
Problem 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 maintenance package {0} stored in file {2}.
Problem 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.
Problem 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.
Problem 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.
Problem 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.
Problem 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
Problem 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.
Problem 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
Problem 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.
Problem 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.
Problem 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.
Problem The product directory is not a directory.
User response Ensure that the specified directory is a valid product directory.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.websphere.product.WASProductNLS.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)