webspher管理节点启动不了解决方法

最新推荐文章于 2021-03-08 10:01:45 发布

原创最新推荐文章于 2021-03-08 10:01:45 发布 · 438 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#操作系统

java 专栏收录该内容

16 篇文章

订阅专栏

这篇博客主要讨论了WebSphere管理节点启动时遇到的问题，即在尝试启动Windows服务时失败，出现‘Timed out waiting for service to respond to command’的错误。建议参照IBM官方文档（http://www-01.ibm.com/support/docview.wss?uid=swg21368020）进行故障排查，检查服务日志以获取详细信息。

：

[10-12-13 10:27:10:328 CST] 0000000a AdminTool A ADMU7704E: 在尝试启动与服务器相关联的 Windows 服务时失败：dmgr；
在执行 WASService.exe 时可能发生了错误：Starting Service: MICROSOF-E2A16FCellManager01
Timed out waiting for service to respond to command, after 60 seconds.Failed to start service, or timed out while waiting for start to complete. Check the logs for details.

http://www-01.ibm.com/support/docview.wss?uid=swg21368020

Problem(Abstract)

Attempts to start IBM WebSphere Application Server (WAS) v6.1.x through Rational Application Developer (RAD) v7.0.x results in the error ADMU7704E: Failed while trying to start the Windows Service associated with server.

Symptom

Complete error while starting WebSphere Application Server (WAS) v6.1.x:

ADMU7704E: Failed while trying to start the Windows Service associated with server: server1; probable error executing WASService.exe: Starting Service: [service name] Timed out waiting for service to respond to command, after 60 seconds.Failed to start service, or timed out while waiting for start to complete. Check the logs for details.

Resolving the problem

The server was configured as a Windows Service.
If this was unintentional, create a new server profile that does not run the application as a Windows Service.

Steps describing how to do this can be found in the Related URL section.

Alternatively, you can do the following:

解决问题的方法如下：

Open Windows Services Control Panel (Start > Settings > Control Panel > Administrative Tools > Services).
Look for the service name of WAS V6.1:

"IBM WebSphere Application Server V6.1 - [service_name]".
Open a command window and go to [RAD_Installation]\runtimes\base_v61\bin
Run the command:

WASService.exe -remove [service_name]

You should see a message "Successfully removed service".

Restart RAD and you should now be able to successfully start your WASv6.1.x server.