Owners Manual

Troubleshooting Your Application | Troubleshooting
694 OMNM 6.5.2 User Guide
1 Re-apply vmlicense.xml located in the /home/synergy directory
2 Apply the Dell EMC generated SKU license if you received one.
For Non Virtual Appliance:
1 Re-apply the license.xml file located in the ..\OpenManage\Network Manager directory
2 Apply the Dell EMC generated SKU license if you received one.
No valid HA license is found during installation of HA
After installation of the secondary appserver, the primary server goes down (appserver icon changes
from green to red), this most likely happened because incorrect license was applied for HA package.
To check the status why appserver went down, right-click on the appserver red icon and select logs/
server option and search for Beginning Server Shutdown. You will see:
2015-08-05 13:02:59,738 3040923 FATAL [com.dorado.mbeans.OWClusterPeerActiveImpl]
(Timer-8:) APPLICATION SERVER ERROR
2015-08-05 13:02:59,739 3040924 FATAL [com.dorado.mbeans.OWClusterPeerActiveImpl]
(Timer-8:) License Not Found for Clustering Servers in High-Availibility Mode
To resolve this issue, contact Dell EMC support to generate an HA license. Once HA license is
received, place it anywhere where appserver is installed then bring up web client and log into
OMNM. When at home page, select "License Management" and click on "Select File" button.
Navigate to where the license file is located and click on "Open" button. At this stage, after few
seconds, you should receive a popup message stating that license got imported. Restart appserver.
Startup issues for Windows installations
If an application or mediation server goes down ungracefully for any reason the JMS message
database may be corrupt in
$OWARE_USER_ROOT\oware\jboss*\ server\oware\data .
When it becomes corrupted the application or mediation server cannot start.
Workaround: Delete the content of the data directory. This allows application or mediation server
startup.
See
Linux Issues on page 727 for additional information about troubleshooting Linux.
Initial Logon after installation fails
If, after installation, your attempt to logon to the application fails with message Connection to
server failed
in the Logon window.
Solution: The most likely cause is that the application server is not running. (Re)start it.
The icon in the Windows System Tray or the presence of the
java.exe process indicates the
status of the application server.
If the icon is red or yellow, no client can connect (although some portlets appear without the
benefit of application server). If the icon is red, right-click on it and select
Start from the menu.
The icon turns yellow as the application server starts. Wait until the icon is green, and repeat the
logon procedure. If this does not work, contact technical support.
Direct Access Fails Because of Java Security Settings
Some Java installations’ security settings (in v.1.7+) may block self-signed websites, interfering
with Direct Access. The workaround is to provide a security exception for the application server, as
follows:
1 Click Start
2 Type configure java and hit [Enter]