Installation completes but the administrative console does not start
What kind of problem are you having?
If you can bring up the browser page, but the console behavior is inconsistent,
error prone, or unresponsive, try upgrading your browser. Older browsers
might not support all the features of the administrative console.
If none of these steps solves the
problem, see if the problem has been identified and documented by using the
links in Diagnosing and fixing problems: Resources for learning.
If you do not see a problem that resembles yours, or if the information provided
does not solve your problem, see Obtaining help from IBM.
An "Internal Server Error", "Page cannot be found",
404, or similar error occurs trying to view the administrative console
Here
are some steps to try if you are unable to view the administrative console:
- Verify that the application
server that supports the administrative console is up and running. For a base
configuration, the administrative console is deployed by default on server1.
Before viewing the administrative console, you must take one of the following
actions:
- Run the startServer server1 command for the Windows platform or ./startServer.sh
server1 command for a UNIX platform from a command prompt in the install_dir\bindirectory
- Click the Start application server link from the first steps panel
- Start WebSphere Application Server as a service or from the Start menu,
if you are using a Windows operating system.
- If you are using the deployment manager for a multi-node configuration,
run the startManager command from the Network_Deployment_install_dir\bin directory.
- View the SystemOut.log file for the application server or the deployment
manager to verify that the server supporting the administrative console has
started.
- Check the URL you use to view the console. By
default, it is http://server_name:9090/admin.
- If you are browsing
the console from a remote machine, try to
eliminate connection, address and firewall issues by pinging the server machine
from a command prompt, using the server name in the URL.
- If you have never been able to access
the administrative console see Troubleshooting the installation.
An "Unable to process login. Check user ID and
password and try again. " error occurs when trying to access console page
This
error indicates that security is enabled for WebSphere Application Server,
and that the user ID or password supplied is either invalid or not authorized
to access the console.
To access the console:
- If you are the administrator, use the ID defined as the security administrative
ID. This ID is stored in the WebSphere Application Server file security.xml.
- If you are not the administrator,
ask the administrator to enable
your ID for the administrative console.
The directory
paths in the console contain strange characters
Directory paths
used for class paths or resources specified in the , configuration files, or elsewhere
that contain strange characters when they are viewed in the administrative
console might result from the Java run time interpreting a backslash (\) as
a control character.
To
resolve, modify Windows-style class paths by replacing occurrences of single
back slashes to two. For example, change c:\MyFiles\MyJsp.jsp to c:\\MyFiles\\MyJsp.jsp.

Troubleshooting by task: What are you trying to do?
Troubleshooting by component: What is not working?

Troubleshooting installation problems
Searchable topic ID:
rtrb_consoleprobs
Last updated: Jun 21, 2007 4:55:42 PM CDT
WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rtrb_consoleprobs.html