Users Guide

Troubleshooting Your Application | Troubleshooting
OMNM 6.5.3 User Guide 695
3 Select the Security tab.
4 Click Edit Site List
5 Click Add
6 Type the OpenManage Network Manager URL (example: http://192.168.0.51:8080/
. Best practice is to use the IP address of the application server, not
localhost or
127.0.0.1 )
7 Click OK and Continue.
8 Apply this change, and/or click OK.
Logon Fails with Invalid Logon Message
When you enter your User Id and Password in logon dialog and click Logon, an Invalid Logon
message appears.
Solution: Ensure you are entering the correct User Id and Password and click Logon. If you have
forgotten the User Id or the Password, or if another user has changed the Password for the User Id,
you may have to re-install the software.
Mediation Server on separate machine fails
Distributed mediation server failures to start can occur when multicast is disabled on your network.
The workaround is to this property in
owareapps\installprops\lib\installed.properties
oware.application.servers= [application server IP address]
Correct this on all mediation server machines.
Unsynchronized Clocks in Clustered Installations
All machines in a cluster, or distributed system, must have synchronized system clocks. If this is not
true, systems may start, but will not work correctly.
Other Failures on Startup
• Another instance of appserver/medserver may be running on one host. Common error
contents:
2005-06-25 08:47:51,968 ERROR [org.jboss.web.WebService] Starting failed
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
Solution: Stop and if necessary restart application server(s).
Starting and Stopping Servers
Best practice in Windows installations is to start or stop application server with the process
monitor icon (installed by the application), when it is installed as a service. Stopping, starting or
restarting the service through operating system’s Service Manager is not recommended. If the
status icon in the tray is green and you restart procman (“process manager”) from Windows’
Control Panel services, an error message appears saying the service did not stop properly. The tray
icon then turns white. Since the application server is still running, when you try to restart the
service again, the icon turns red.
To restore the Process monitor icon to function correctly and show status, stop all Java and WMI
processes in the process manager. A system reboot also re-initializes the OWProcMan (process
monitor). Note that the service name may be different if your package has been specifically
branded. The executable path for the service is
\....\oware\bin\owprocman.exe.