+

Search Tips   |   Advanced Search

Administrative console does not start even though installation completes

This topic discusses problems that we can encounter when you attempt to access the console.

This topic references one or more of the application server log files. As a recommended alternative, we can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM i systems. We can also use HPEL in conjunction with the native z/OS logging facilities. If we are using HPEL, we can access all of the log and trace information using the LogViewer command-line tool from the server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

What kind of problem are you having?

If we can bring up the browser page, but the administrative console behavior is inconsistent, error prone, or unresponsive, try upgrading your browser. Older browsers might not support all the features of the administrative console. For a listing of supported web browsers, see the Supported hardware and software web page.

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 administrative console

Here are some steps to try if you are unable to view the administrative console:


Unable to process login. Check user ID and password and try again. error occurs when trying to access the administrative console page

This error indicates that security is enabled for WebSphere Application Server, and that the user ID or password supplied is either not valid or not authorized to access the console.

To access the console:


The directory paths in the administrative 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 administrative 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.

(zos) To resolve, make sure we have no back slashes in the class paths. Replace any back slashes with forward slashes.


Related tasks

  • Troubleshooting administration

    (iseries) Start and stop the deployment manager