WebSphere Server Runtime messages |
WSVR0001I: Server {0} open for e-business
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0002I: Server {0} open for e-business, problems occurred during startup
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0003E: Server {0} failed to start
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0004E: The server name, {0}, is not a valid name.
Explanation:
There is a mismatch between the name of the server speicified and the server name in the corresponding server.xml.
User Response:
Make sure that the server name specified matches both the directory name for the server and the server name in the corresponding server.xml.
WSVR0007E: Could not find the {0} object in {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0008E: Error encountered reading {0}
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0009E: Error occurred during startup
{0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0016W: Classpath entry, {0}, in Resource, {1}, located at {2} has an invalid variable
Explanation:
A variable used in the classpath definition of the resource is not defined or does not contain a valid value.
User Response:
Define the missing variable or provide a valid value for the missing variable.
WSVR0017E: Error encountered binding the J2EE resource, {0}, as {1} from {2}
{3}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0018W: Unable to create CustomService, {0}
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0019W: CustomService, {0}, failed to initialize.
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0020W: CustomService, {0}, failed to shutdown.
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0021W: Native path entry, {0}, in Resource, {1}, located at {2} has an invalid variable
Explanation:
A variable used in the native path definition of the resource is not defined or does not contain a valid value.
User Response:
Define the missing variable or provide a valid value for the missing variable.
WSVR0022W: The value, {0}, with Resource ID, {1}, located at {2} has an invalid variable
Explanation:
A variable used in the resource is not defined or does not contain a valid value.
User Response:
Define the missing variable or provide a valid value for the missing variable.
WSVR0024I: Server {0} stopped
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0025I: Creating temporary product license
Explanation:
None
User Response:
None
WSVR0026I: Error occurred while validating product license
Explanation:
None
User Response:
None
WSVR0027I: The product will expire in {0} days.
Explanation:
None
User Response:
None
WSVR0028I: The product has expired.
Please re-install or purchase the product.
Explanation:
None
User Response:
None
WSVR0030E: ORB not initialized
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0031E: Unable to load container
{0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0032E: Object Adapter created already
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0033E: Unable to load security collaborator, {0}
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0034W: Invalid passivation directory specified: {0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0035E: Failure to initialized the container: {0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0036E: Failure to obtain initial naming context: {0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0037I: Starting EJB jar: {0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0038I: No JNDI name found for {0}, binding home name as {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0039E: Unable to start EJB jar, {0}: {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0040E: addEjbModule failed for {0}
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0041I: Stopping EJB jar: {0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0042E: Unable to stop {0}: {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0043E: Unbind failed for {0}: {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0044E: Unable to stop EJB jar, {0}: {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0045E: Unable to create sub-context {0}: {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0046E: Unable to bind, {0}: {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0047E: Batch naming operation failed : {0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0048W: Binding {0} failed, no JNDI name found
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0049I: Binding {0} as {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0051W: Attempted to register a URL Provider, {0}, with a null protocol
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0052W: Attempted to unregister URLProvider with null protocol
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0062E: Unable to start EJB, {0}: {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0064W: Minimum threads for pool {0} was less than 0; changing from {1} to 0
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0065W: Maximum threads for pool {0} was less than 1; changing from {1} to 1
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0066W: Maximum threads for pool {0} was less than the minimum; changing from {1} to {2}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0100W: An error occurred initializing, {0}
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0101W: An error occurred starting, {0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0102E: An error occurred stopping, {0}
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0103E: An error occurred destroying, {0}
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0104E: No type or class defined in {0} at line {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0105E: Both type, {0}, or class, {1}, are defined in {2} at line {3}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0106E: Invalid startup value {0} at line {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0107W: Duplicate component, {0}, in file {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0120E: An error occurred processing {0}
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0150E: Missing entry for {0} in {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0200I: Starting application: {0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0201E: Application, {0}, failed to initialize
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0202E: Application, {0}, failed to start
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0205E: Module, {0}, of application, {1}, failed to initialize
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0206E: Module, {0}, of application, {1}, failed to start
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0207I: Preparing to start EJB jar: {0}
Explanation:
Preparation includes reading deployment descriptors and loading classes.
User Response:
No action is required for this status message.
WSVR0208E: Unable to prepare EJB jar: {0}
{1}
Explanation:
An EJB jar can fail preparation due to incorrect deployment descriptors.
User Response:
Look for messages that appear between this message and the preceeding WSVR0207I message. If you find one, it may be related to the cause of this message. If none is found, use the exception that appears as part of this message as a possible cause of this message.
WSVR0209E: Unable to prepare EJB jar {0}, enterprise bean {1}
{2}
Explanation:
An EJB can fail preparation if the container required classes have not been generated for the EJB.
User Response:
Verify the EJB jar that contains the failed EJB {1} has been deployed.
WSVR0210W: No modules defined for application, {0}, on server, {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0211W: Duplicate library, {0}, defined in {1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0212W: Library, {0}, defined in {1} does not exist
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0213W: Classpath entry, {0}, in library, {1}, located at {2} has an invalid variable
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0214W: Application, {0}, already installed
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0215W: Starting application, {0}, failed. The application is not installed.
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0216W: Stopping application, {0}, failed. The application is not started.
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0217I: Stopping application: {0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0218W: No modules defined for application, {0}, on server, {1}, in cluster, {2}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0219I: Application, {0}, is disabled
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0220I: Application stopped: {0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0221I: Application started: {0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0300I: Problems found in {0}
Explanation:
Parse errors or warnings were found.
User Response:
Fix the errors and warnings.
WSVR0301W: Invalid value type, {0}, expecting {1} at line {2}
Explanation:
The type specified in the XML file was not expected.
User Response:
Fix the XML file such that the appropriate type is used.
WSVR0302W: Invalid value, {0}, at line {1}
Explanation:
The value specified was not valid.
User Response:
Change the value to valid value.
WSVR0303W: Invalid element tagname, {0}, at line {1}
Explanation:
There is no implementation class for the tag.
User Response:
Contact IBM Support
WSVR0304E: Unsupported encoding, {0}
Explanation:
The file encoding is not supported
User Response:
Using an encoding that is supported by Java.
WSVR0305W: Invalid attribute, {0}, at line {1}
Explanation:
The attribute is not valid.
User Response:
Remove the attribute.
WSVR0306E: Unsupported XMI version
Explanation:
The XMI version is not supported
User Response:
Update the file to XMI 2.0
WSVR0307W: Invalid namespace, {0}, at line {1}
Explanation:
The namespace is not valid.
User Response:
Contact IBM Support
WSVR0308W: Unknown package, {0}, at line {1}
Explanation:
The package is not valid.
User Response:
Contact IBM Support
WSVR0309E: No packages have been registered
Explanation:
No packages are registered
User Response:
Contact IBM Support
WSVR0310W: Unable to resolve reference for, {0}, at line {1}
Explanation:
The reference could not be resolved.
User Response:
Contact IBM Support
WSVR0311W: Unknown exception
{0}
Explanation:
An unexpected problem occurred.
User Response:
Contact IBM Support
WSVR0312E: Unknown exception
{0}
Explanation:
An unexpected problem occurred.
User Response:
Contact IBM Support
WSVR0313E: The Message Driven Bean listener service could not be started, message driven beans will not be able to receive messages.
Explanation:
The message listener service may be disabled.
User Response:
Verify the message listener service is enabled.
WSVR0313E: The Message Driven Bean listener service could not be started, message driven beans will not be able to receive messages.
Explanation:
The message listener service may be disabled.
User Response:
Verify the message listener service is enabled.
WSVR0314E: Failed to parse {0} at line {1}, column {2}
{3}
Explanation:
The XML file does not have a valid XML structure
User Response:
Correct the XML file.
WSVR0400W: Unable to register the {0} MBean
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0401W: Unable to deregister the {0} MBean
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0402W: Invalid MBean name {0}
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0500E: Unable to parse {0} at line {1}, column {3}
{4}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0501E: Error creating component {0}
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0600W: No thread context
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0601W: javaURLContext object missing for J2EEName {0}, caught exception
{1}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0602W: Attempt to access javaNameSpace from a ComponentMetaData that does not support a javaNameSpace.
Explanation:
Only Web-Components and EJB-Components support access to the javaNameSpace.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0603E: ComponentMetaDataAccessor beginContext method received a NULL ComponentMetaData.
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
WSVR0604I: Attempt to register EJBContainer MBean: caught exception
{0}
Explanation:
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.