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>Search


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

Knowledge Base

Clever solve the problem that local cannot access elog server

Publication Date:  2012-11-14  |   Views:  833  |   Downloads:  0  |   Author:  SU1000722738  |   Document ID:  EKB1000019541


Issue Description

Customer feedback elog server has been in used normally for a period of time (a month), but now the server can’t local access to elog server. 

Alarm Information


Handling Process

Solution A:
1. Choose "start > run".
2. Input “services.msc” in the “open” dialog box.
3. Click "ok".
Display "service" window.
4, Find "IIS Admin Service" in the "Service" window.
If cannot find the service, please turn to solve method 2 for operation.
5. Right click in "IIS Admin Service".
6. Select “stop” on the pop-up shortcut menu.
7. click "yes" in the pop-up dialog.
8. Choose "start > program > log management system > stop log server".
9. Choose "start > program > log management system > startup log server".

Solution B:
If didn’t start IIS service, please carry on the following operations:
1. Choose "start > run".
2. Input "CMD" in "open" dialog box.
3. Click "ok".
Display "command line" window.
4. Input netstat-abn.
5. Check the name of the program which occupied the port 80.
6. If the occupancy program is not the "tomcat6.exe", end the process is in task manager.
7. Choose "start > program > log management system > stop log server".
8. Choose "start > program > log management system > startup log server".
If the problem still hasn’t been solve after implement the above steps
At this time should collect the system log of log server at first.

Solution C:
Run “%LOGSERVER_ROOT%\bin\dgn-ls.bat” and “%LOGCOLLECTOR_ROOT%\bin\dgn-lc.bat” files
After pop-up the CMD interface, did not show the acquisition process and many of them will be interrupted (normally a lot of information need to be collected, it will show the collecting process, and need a period of time)
Doubt elog service has not started successfully, after repeated perform the solution method A, it is normal.

If still unable to access after the above reasons are ruled out.

Solution D:
Remove the browser cache, restart your browser and then the problem is solved.

Root Cause

Because in the past can normal access, the installation should be no problem, it may be elog server startup abnormal or the new installed software caused port conflict or influenced by other special reasons. 


Change the kernel impassability browser testing result is obvious, and this method sometimes can solve the problem that WEB log on firewall unsuccessful.