Installation hangs at 35% "Starting Websphere Applicati

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
jstage
Premium Member
Premium Member
Posts: 4
Joined: Tue Dec 27, 2005 9:35 am

Installation hangs at 35% "Starting Websphere Applicati

Post by jstage »

During installation it hangs at 35% "Starting Websphere Application Server" .

I am installing on a 2003 windows server. Here is the log from StartServer.log .

************ Start Display Current Environment ************
Host Operating System is Windows 2003, version 5.2
Java version = J2RE 1.4.2 IBM Windows 32 build cn142-20060421 (SR5) (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = C:\IBM\WebSphere\AppServer
user.install.root = C:\IBM\WebSphere\AppServer/profiles/default
Java Home = C:\IBM\WebSphere\AppServer\java\jre
ws.ext.dirs = C:\IBM\WebSphere\AppServer\java\lib;C:\IBM\WebSphere\AppServer\classes;C:\IBM\WebSphere\AppServer\lib;C:\IBM\WebSphere\AppServer\installedChannels;C:\IBM\WebSphere\AppServer\lib\ext;C:\IBM\WebSphere\AppServer\web\help;C:\IBM\WebSphere\AppServer\deploytool\itp\plugins\com.ibm.etools.ejbdeploy\runtime
Classpath = C:\IBM\WebSphere\AppServer/profiles/default\properties;C:\IBM\WebSphere\AppServer\properties;C:\IBM\WebSphere\AppServer\lib\bootstrap.jar;C:\IBM\WebSphere\AppServer\lib\j2ee.jar;C:\IBM\WebSphere\AppServer\lib\lmproxy.jar;C:\IBM\WebSphere\AppServer\lib\urlprotocols.jar
Java Library path = C:\IBM\WebSphere\AppServer\java\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\IBM\WebSphere\AppServer\bin;C:\IBM\WebSphere\AppServer\java\bin;C:\IBM\WebSphere\AppServer\java\jre\bin;C:\Program Files\Legato\nsr\bin;C:\Program Files\Support Tools\;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\IBM\SQLLIB\BIN;C:\IBM\SQLLIB\FUNCTION;C:\IBM\SQLLIB\SAMPLES\REPL;C:\IBM\SQLLIB\BIN
Current trace specification = *=info
************* End Display Current Environment *************
[4/28/10 10:13:19:729 EDT] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info.
[4/28/10 10:13:19:932 EDT] 0000000a AdminTool A ADMU0128I: Starting tool with the default profile
[4/28/10 10:13:19:932 EDT] 0000000a AdminTool A ADMU3100I: Reading configuration for server: server1
[4/28/10 10:13:23:198 EDT] 0000000a AdminTool A ADMU3200I: Server launched. Waiting for initialization status.


Any thoughts ?
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

Did you use the correct user and priviledges ?

What happens if you try to start WAS manually ?
jstage
Premium Member
Premium Member
Posts: 4
Joined: Tue Dec 27, 2005 9:35 am

Post by jstage »

Yes!

If I kill the installation process and manually run the WAS it starts without any issue.
Post Reply