This topic discusses problems that you can encounter when you attempt to access the console.
If you 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
viewing the administrative console, you must run the startServer Qshell script.
For more information on starting the server, see Starting an application server.
D A,L
START appserver_proc_name,JOBNAME=server_short_name, ENV=cell_short_name.node_short_name.server_short_name
START BBO6ACR,JOBNAME=BBOS001,ENV=PLEX1.SY1.BBOS001
START BBO5DCR,JOBNAME=BBODMGR,ENV=PLEX1.PLEX1.BBODMGR
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.
Directory paths that are used for class paths or resources specified in an assembly tool, in 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 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.
To resolve, make sure you
have no back slashes in your class paths. Replace any back slashes with forward
slashes.