Problems After Installation

This section describes problems that may occur after successfully installing Sentinel LDK-EMS.

Issue: The Login button on the Login screen does not function

Due to high security settings in the web browser, the Login button on the login screen of Sentinel LDK-EMS does not work.

Solution:

In your web browser, do the following:

1.From the menu bar, go to Tools > Internet Options. A dialog is displayed.

2.Click the Security tab.

3.Click Sites and add the URL of Sentinel LDK-EMS to the list of trusted sites.

4.Apply the changes and restart your browser.

This problem has been seen under Windows Server 2003 and Windows Server 2008.

Issue: Port not available

Given the following situation:

>A user is not able to access the Sentinel LDK-EMS site (localhost/ems)

>In the Services screen, Sentinel LDK-EMS Service has the status Started.

This can be caused by a port conflict. The HTTP/HTTPS port for Sentinel LDK-EMS may be in use by another application.

Check the Sentinel LDK-EMS log file. This can be found at:

%ProgramFiles(x86)%\Thales\Sentinel EMS\EMSServer\webapps\ems\log\)

(For 32-bit machines: %ProgramFiles%\....)

If the log file shows a “JVM binding” issue, this indicates that the port used by the Sentinel LDK-EMS web application run is in use by another application.

Solution:

To resolve a port conflict:

Use the Netstat command to identify which application has occupied the required port. Do one of the following:

>Stop the conflicting application as follows:

a.Enter: netstat -aon | findstr "8080"
The relevant process ID is displayed.

b.Use the Task Manager to cancel the process with this process ID.

c.Restart Tomcat.

>Configure Sentinel LDK-EMS to use a different port.
Modify the port used by Sentinel LDK-EMS in the web_service.xml file and the database.

>Remove and then reinstall Sentinel LDK-EMS (removal does not remove the Sentinel LDK-EMS database).

Issue: Users are not able to access Sentinel LDK-EMS

Solution:

Sentinel LDK-EMS Service may be installed behind a firewall, and it was not added in the exception list for the firewall.