Possible OpsCenter console access issues
Table: OpsCenter console access issues, causes, and solution describes possible OpsCenter console access issues and their solution.
Table: OpsCenter console access issues, causes, and solution
Issue and Cause | Solution |
|---|
You cannot connect to the Web interface. Your Web browser displays a "page cannot be displayed" or "connection was refused."message. This issue happens when the OpsCenter Web interface (the OpsCenter console) is not running or is inaccessible on the network.
| To connect to the Web interface Verify that the OpsCenter Web server Service is running. You can check the status of all OpsCenter processes on UNIX by entering the following command: <INSTALL_PATH>/SYMCOpsCenterServer/bin/opsadmin.sh monitor Verify that a Web browser on the OpsCenter server can connect to the OpsCenter console by using the following address: https://localhost/opscenter By default, OpsCenter tries to run on port 443 (HTTPS). If port 443 is not available,
OpsCenter can use a different port. To learn more about the HTTPS ports that
OpsCenter uses, run the configurePorts utility. Run
the following command: On Windows: <INSTALL_PATH>\OpsCenter\gui\bin\goodies\configurePorts.bat -status On UNIX: <INSTALL_PATH>/SYMCOpsCenterWebGUI/bin/goodies/configurePorts.sh
-status
|
The OpsCenter Web interface is running, but the OpsCenter console is not available. Your Web browser displays an HTTP STATUS 404 error. This issue happens when the OpsCenter console application is not loaded.
| To resolve an HTTP STATUS 404 error on Windows Locate the opscenter.war file in the following directory to verify that the OpsCenter application is installed: INSTALL_PATH\OpsCenter\gui\webserver\webapps
Verify that all the OpsCenter server services are running. Start all the OpsCenter Server services by using the following command: INSTALL_PATH\OpsCenter\server\bin\opsadmin.bat start
To resolve an HTTP STATUS 404 error on UNIX: Locate the opscenter.war file in the following directory to verify that the OpsCenter application is installed: <INSTALL_PATH>/SYMCOpsCenterGUI
To verify that all OpsCenter Server processes are running, use the following command: <INSTALL_PATH>/SYMCOpsCenterServer/bin/opsadmin monitor Start all the OpsCenter Server processes by using the following commands: <INSTALL_PATH>/SYMCOpsCenterServer/bin/opsadmin.sh start
|
You see a blank page when you try to access OpsCenter using Internet Explorer 7.0 and later versions. | To resolve blank page issues when using Internet Explorer 7.0 and later Open Internet Explorer . On the Tools menu, click . Click the Security tab. Under Select a Web content zone to specify its security settings, click the , icon and then click .
In the Security Settings dialog box, browse to Miscellaneous > Allow META REFRESH and select . Click to confirm that you want to change the security settings for the zone, and then click .
If you do not want to change your security settings, you must manually append /opscenter to the OpsCenter URL. Without the changes to the security settings, the issue recurs every time that you accessOpsCenter, and you must add /opscenter to the URL. |
You get the following error when you access OpsCenter by clicking on Windows: Windows cannot find https://<MACHINE_NAME>:<PORT_NUMBER>/opscenter. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button and then click Search. | To fix the Web user interface login error for Windows XP Open Windows Explorer (or My Computer). Go to . Select Extension: and File Type: Click . In the Edit File Type window, select and click .
Uncheck (the dialog should then hide the lower part). Click for that dialog and the next one (afterwards, the box is still checked but the box will be cleared). Repeat for Extension: File Type: (and any other protocols you want to fix). Repeat for Extension: File Type: . Repeat for Extension: (or ) File Type: .
Note that the File Types user interface that allows you to uncheck the option, as described above, is not available in Windows Vista. You need to edit the registry to remove the ddeexec key.
You need to manually edit the registry in Windows Vista or in cases where
the File Types listing is missing certain entries such as URL:HyperText Transfer Protocol with Privacy
(HTTPS). Editing the registry incorrectly can damage your system. Do not attempt
these steps if you are inexperienced or uncomfortable using the Registry Editor. Use the following resolution on Windows Vista or in cases where
the File Types listing is missing certain entries such as URL:HyperText Transfer Protocol with Privacy
(HTTPS): Go to , then type regedit and click . Use the directory tree hierarchy to navigate to . Delete the ddeexec registry key. Repeat for (and any other protocols you want to fix). Repeat for . Repeat for .
|
