|
Problem(Abstract) |
After federating your WebSphere® Application Server V5.0.1
Base node with a Network Deployment Manager node, the Base application
server will not start even though the nodeagent is running. As a result,
you find the following error in your application server SystemOut.log:
"WSVR0003E: Server server1 failed to start" |
|
|
|
Cause |
Click on the error.txt link at the bottom of this
document to see the full text of the error message. |
|
|
Resolving the
problem |
You will need to make sure your WebSphere Application
Server SDK is J2RE 1.3.1 IBM Windows 32 build cn131-20030329. If
you did not directly change the SDK in WebSphere Application Server, and
this happened after applying fix pack 1, then fix pack 1 failed to install
properly (even if it shows no errors). There are no SDK options during
install to stop the SDK from upgrading when installing WebSphere
Application Server V5.0 fix packs.
To fix this issue, perform the following:
- Remove fix pack 1 from WebSphere Application Server.
- Stop all Java processes.
- Download the latest UpdateInstaller.
- Use the latest UpdateInstaller to install fix pack 1.
- After the install, verify that your WebSphere Application Server SDK
is running at J2RE V1.3.1 IBM Windows 32 build cn131-20030329 by
executing the following command:
$WAS_HOME\java\bin>java -fullversion
If you still have problems, call 800-IBM-SERV and create a problem
management record (PMR) to work with IBM Support. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|