WebSphere Process Server messages     Operating Systems: All supported

WVER

WVER0201E: Unable to determine the history directory; the product directory could not be determined
Problem 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.
WVER0202E: Unable to load the history information
Problem History information could not be loaded from the history file {0}. Particular details are according to the error that occurred.
User response Verify that the history file is readable, and has a correct format.
WVER0203E: An exception occurred while reading {0}
Problem Refer to the nested exception details for further information.
User response Refer to the nested exception details for further information.
WVER0204E: An exception occurred while creating the history directory {0}
Problem Refer to the nested exception details for further information.
User response Refer to the nested exception details for further information.
WVER0205E: An exception occurred while creating a backup for history file {0} to {1}
Problem Refer to the nested exception details for further information.
User response Refer to the nested exception details for further information.
WVER0206E: An exception occurred while writing event history {0}
Problem Refer to the nested exception details for further information.
User response Refer to the nested exception details for further information.
WVER0210I: Copyright (c) IBM Corporation 2002, 2005; All rights reserved.
Problem This is a standard copyright statement.
User response No action is required.
WVER0212I: HistoryInfo Reporter Version {0}, Dated {1}
Problem This is a standard module description statement.
User response No action is required.
WVER0225E: No value was specified for the ''{0}'' argument.
Problem The listed argument requires a value. (Use ''-help'' or ''-usage'' to display usage information.)
User response Specify a value for the listed argument.
WVER0226E: The value ''{0}'' is not a 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''.
WVER0228E: The argument ''{0}'' is not a valid argument.
Problem 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 <text | html> ] [ -file <output file> ] [ -maintenancePackageId <maintenancePackageId> ] [ -component <componentName> ] ) | ( [ -help | -? | /help | /? | -usage ] )
Problem This informational message describes the arguments to the historyInfo utility program. The historyInfo utility program accepts five optional keyword arguments: one that specifies the output format; one that specifies an output file; one that displays only those events associated with a specified maintenance package; one that displays only those events associated with a specified component; and one that is used to display usage information. Use ''-usage'' or ''-help'' to display additional information.
User response No action is required. The usage information message displays upon request.
WVER0231I: Use the -format argument to specify an output format of either ''text'' or ''html.'' Use the -file argument to specify an output file and provide a file name. Use the -maintenancePackageId argument to specify the maintenance package ID that restricts the events displayed. Use the -component argument to specify the name of a component that restricts the events displayed. Use the -help argument to display version information. The -usage argument is used to display this information message.
Problem The message describes the valid arguments to the versionInfo utility program.
User response No action is required. The usage information message displays upon request.
WVER0240E: Error writing version report to {0}: {1}
Problem Corrective action depends on the specifics of the error that occurred. The specified error occurred while writing the history report to the specified file.
User response Verify 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.
Problem 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 Retry the requested operation, or contact IBM WebSphere Application Server Support. Web page at http://www-3.ibm.com/software/webservers/appserv/support.html
WVER0242E: An exception occurred while processing history information.
Problem Refer to the nested exception details for further information.
User response Refer to the nested exception details for further information.
WVER0243E: Exceptions occurred while processing history information.
Problem Refer to the nested exception details for further information.
User response Refer to the nested exception details for further information.
WVER0261E: Unable to record the application of fix {0} on component {1} in file {2}.
Problem The named file could not be saved.
User response Verify 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 fix {0} on component {1} in file {2}.
Problem The named file could not be saved.
User response Verify 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 fix {0} on component {1} stored in file {2}.
Problem The named file could not be removed.
User response Verify that the target file can be removed.
WVER0264E: Unable to record the removal of the application of fix {0} on component {1} -- no application is on record.
Problem The component has no record of an application of the specified fix. The product information might be corrupt, or an internal error might have occurred.
User response Contact IBM WebSphere Application Server Support. Web page at http://www-3.ibm.com/software/webservers/appserv/support.html
WVER0265E: Unable to remove fix driver {0} stored in file {2}.
Problem The named file could not be removed.
User response Verify that the target file can be removed.
WVER0266E: Recoverable errors occurred while parsing maintenance package driver information.
Problem The errors, a list of which follows, occurred while parsing maintenance package information.
User response Refer to the listed errors for suggested user actions.
WVER0267E: Unable to record the removal of the application of maintenance package {0} on component {1} in file {2}.
Problem The named file could not be saved.
User response Verify 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 maintenance package {0} on component {1} stored in file {2}. The named file could not be removed.
Problem The named file could not be removed.
User response Verify that the target file can be removed.
WVER0269E: Unable to record the removal of the application of maintenance package {0} on component {1} -- no application is on record.
Problem The component has no record of an application of the specified maintenance package. The product information might be corrupt, or an internal error might have occurred.
User response Contact IBM WebSphere Application Server Support. Web page at http://www-3.ibm.com/software/webservers/appserv/support.html
WVER0270E: Unable to remove maintenance package driver {0} stored in file {2}.
Problem The named file could not be removed.
User response Verify that the target file can be removed.
WVER0271E: Unrecognized product history file extension ''{0}''.
Problem History information is stored in files having specific extensions. The extensions determine the type of information stored in each file. Valid extensions are .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 error indicates an internal problem.
WVER0272E: An exception occurred while reading {0}
Problem Refer to the nested exception details for further information.
User response Refer to the nested exception details for further information.
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.history.WASHistoryNLS.html

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