Adminserver dies after while

[Jan Simek]

I have problem with adminserver WAS 4.0.4. WS admin service starts and everything seems perfect for a while. Message in tracefile is correct: [12.11.02 7:37:31:531 CET] 2898c542 Server A WSVR0023I: Server __adminServer open for e-business
But after few minutes IBM WS AdminService in dies (status isn't started) and event log contains messages:
Event Type:Error
Event Source:Websphere
Event Category:None
Event ID:0
Date:12.11.2002
Time:7:44:51
User:N/A
Computer:SKDAMBSB2BAP6
Description:
The description for Event ID ( 0 ) in Source ( Websphere ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: IBM WS AdminServer 4.0 status: 997 Service timed out waiting for WebSphere Administration Server to start.

Event Type:Information
Event Source:Websphere
Event Category:None
Event ID:0
Date:12.11.2002
Time:7:44:51
User:N/A
Computer:SKDAMBSB2BAP6
Description:
The description for Event ID ( 0 ) in Source ( Websphere ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: IBM WS AdminServer 4.0 status: 997 WebSphere Administration server is shutting down.
Event Type:Error
Event Source:Websphere
Event Category:None
Event ID:0
Date:12.11.2002
Time:7:44:51
User:N/A
Computer:SKDAMBSB2BAP6
Description:
The description for Event ID ( 0 ) in Source ( Websphere ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: IBM WS AdminServer 4.0 status: 10049 Stop: error in connect 10049
.
Event Type:Information
Event Source:Websphere
Event Category:None
Event ID:0
Date:12.11.2002
Time:7:44:51
User:N/A
Computer:SKDAMBSB2BAP6
Description:
The description for Event ID ( 0 ) in Source ( Websphere ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: IBM WS AdminServer 4.0 status: 6 Stopping AdminService...
Applications are up and running, only adminserver is down.
Any ideas?
Thanks.
Jan Simek

[Kyle Brown]

Does this happen if you start the adminserver at the command line and not as a service?
Kyle

[Jan Simek]

WAS AE 4.0.4, W2K SP3
Everything works fine if I start adminserver from comand line but I have found that administrative console starts if i start adminserver at the command line and as service too. Now it seems that adminserver is running even if I start adminserver as service and event log contains messages about service shutdown,error in connect and IBM WS AdminService isnt't in "Started" status.
Application servers in running startup status are starting for very long time cca 8 minutes but CPU is idle for most of time. I don't know why. This problem have occured for first time after complete server reinstall and fixpack 4 update. Maybe long starting time of application servers causes IBM WS AdminService time out during startup. Is it possible?
Jan Simek