WAS v8.5 > Reference > Administrator best practicesAdministrative console does not start even though installation completes
This topic discusses problems that we can encounter when we attempt to access the console.
IBM recommends using the HPEL log and trace infrastructure. With HPEL, one views logs using the LogViewer command-line tool in PROFILE/bin.
What kind of problem are you having?
- Internal Server Error, Page cannot be found, 404, or similar error occurs trying to view the dmgr console
- Unable to process login. Check user ID and password and try again. error occurs when trying to access the dmgr console page
- The directory paths in the dmgr console contain strange characters
If we can bring up the browser page, but the dmgr console behavior is inconsistent, error prone, or unresponsive, try upgrading your browser. Older browsers might not support all the features of the dmgr console.
IBM Support has documents and tools that can save you time gathering information needed to resolve problems. Before opening a problem report, see the Support page:
Internal Server Error, Page cannot be found, 404, or similar error occurs trying to view the dmgr console
Here are some steps to try if you are unable to view the dmgr console:
- Verify the application server that supports the dmgr console is up and running. For a base configuration, the dmgr console is deployed by default on server1.
Before viewing the dmgr console, you must take one of the following actions:
- Run the startServer server1 command for the Windows platform from a command prompt in the install_dir\bindirectory, or the ./startServer.sh server1 command for operating systems such as AIX or Linux.
- Click the Start the server link from the First steps console.
- Start WebSphere Application Server as a service or from the Start menu, if you are using a Windows operating system.
- View the SystemOut.log file for the application server to verify the server that supports the dmgr console started.
- Check the web address we use to view the console. By default, this address is http://server_name:9060/ibm/console, where server_name is the host name.
- If you are browsing the dmgr 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 web address.
- If we have never been able to access the dmgr console see the topic on troubleshooting installation.
Unable to process login. Check user ID and password and try again. error occurs when trying to access the dmgr console page
This error indicates that security is enabled for WAS, and the user ID or password supplied is either not valid 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 WAS security.xml file.
- If you are not the administrator, ask the administrator to enable your ID for the dmgr console.
The directory paths in the dmgr console contain strange characters
Directory paths used for class paths or resources specified in an assembly tool, in configuration files, or elsewhere containing strange characters when they are viewed in the dmgr console might result from the Java run time interpreting a backslash (\) as a control character.
To resolve this problem, 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.
Related
Troubleshooting administration