No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Failing to Access the Secospace eLog at the Local Computer

Publication Date:  2012-07-24 Views:  31 Downloads:  0
Issue Description
When you open the Secospace eLog management interface, if the following figure interface or another interface appears, you need to check whether the IIS service is started on the log server. If the IIS service is not started, see Solution 2 to solve the problem.
Alarm Information
None
Handling Process

Solution 1
1. Choose Start > Run.
2. In the Open dialog box, enter services.msc.
3. Click OK.
   The Services window appears.
4. Find IIS Admin Service.
   If the service is not displayed, go to Solution 2 to continue.
5. Right-click IIS Admin Service.
6. Choose Stop from the displayed shortcut menu.
7. In the displayed dialog box, click Yes.
8. Choose Start > Programs > Secospace eLog > Stop Log Server.
9. Choose Start > Programs > Secospace eLog > Start Log Server.


Solution 2
If the IIS service is not started, do as follows:
1. Choose Start > Run.
2. In the Open dialog box, enter cmd.
3. Click OK.
   The CMD interface appears.
4. Enter netstat -abn.
5. Check the process that occupies port 80.
6. If the process is not tomcat.exe, end the process.
7. Choose Start > Programs > Secospace eLog > Stop Log Server.
8. Choose Start > Programs > Secospace eLog > Start Log Server.

Root Cause
Port 80 for the log server is occupied by another service.
Suggestions
None.

END