The server process must be running in order to use the administrative console. For wsadmin, many functions require a connection to the server as well. Verify that the server is running and ready to receive administrative requests. For more information on how to verify that the server is running, see the verify the installation topic.
If the server has not started and you are using wsadmin for an administrative function that does not require the server to be started, ensure that you have specified -conntype NONE when invoking wsadmin.
Use the TCP/IP ping command to test that the hostname is reachable from the system where the browser or wsadmin program is being used. If you are able to ping the hostname, this indicates that there are no firewall or connectivity issues.
If the host where the application server is running is remote, ensure that hostname in the browser URL for the console is correct, or the -host hostname option of the wsadmin command is being used to direct wsadmin to the correct server.
If you are using the wsadmin tool, see the Start and stop applications with wsadmin topic. Check the wsadmin log files located in the logs directory of your instance for errors.
Check the log files for server errors. For information on the log files and where they are located, see WebSphere Application Server - Express log files.
Read the release notes:
- WebSphere
Application Server - Express V5.1.0.X Release Notes
(http://www.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/
express/docs/relnotesexp51.html) - WebSphere
Application Server - Express V5.1.1 Release Notes (http://www.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/
express/docs/relnotesexp511.html)