Windows service? Windows service? I spit on the windows service.
The windows service just kicks off the startup batch file. The windows service is good for starting off tiny, insignificant applications like Norton Anti-Virus, or Windows Messaging. But for real applications built by IBM, the windows service is a waste.
The windows service expects everythnig to start up in 10 seconds or something. If your app server has a 500 meg footprint, which is the minimum practially with WebSphere, then just filling that memeory will take longer than the service is willing to wait. As a result, you get a timeout error from the service, despite the fact that WebSphere is starting normally and properly.
Plus, the service only starts server1, which is useless when you go to a federated domain.
Do the startserver server1 thing from the DOS propmt, aka command prompt, and look for errors there.
From that point, if there are problems, look in the log files.
Here's a great link about troubleshooting WebSphere Application Server problems, including info on trace logs, system logs, error logs, activity logs, the service log, and the IBM Log Analyzer tool:
How to TroubleShoot WebSphere Application Server Errors and Problems Good luck!
-Cameron McKenzie