Table of Contents
Advertisement
Troubleshooting with Log Files
When setting changes take effect
When setting changes take effect
This section defines the interval between the moment that a log file setting is changed and the
moment the change takes effect.
• When a setting is changed using the registry, the interval is usually a minute or less. The
DWORD registry value that controls logging is: HKEY_LOCAL_MACHINE\SOFTWARE\NETWORK
ASSOCIATES\EPOLICY ORCHESTRATOR\LOGLEVEL.
• When a setting is changed in an INI file or an XML file, the change usually takes effect
immediately.
• In some instances, when a change takes effect upon restarting the system, the user controls
the interval.
Table 6: When log setting changes take effect
Log file name
AGENT_<SYSTEM>.LOG
CORE-INSTALL.LOG
EPOAPSVR.LOG
EPO400COMMONSETUP.LOG
EPO-INSTALL.LOG
EPO400-INSTALL-MSI.LOG
ERRORLOG<CURRENT_DATETIME>
EVENTPARSER.LOG
FRMINST_<SYSTEM>.LOG
JAKARTA_SERVICE_<DATE>.LOG
LICENSING.LOG
LOCALHOST_ACCESS_LOG.<DATE>.TXT
MCSCRIPT.LOG
ORION.LOG
PRDMGR_<SYSTEM>.LOG
REPLICATION.LOG
SERVER.LOG, SERVER_BACKUP.LOG
SQL2K5bCINST.LOG
STDERR.LOG
10
Using Log Files for Troubleshooting in ePolicy Orchestrator 4.0
Setting change takes effect...
Within one minute
Cannot change
Within one minute
Immediately upon saving change to EPO400-DEBUG.INI,
located at <CURRENT USER'S TEMP
DIRECTORY>\NAILOGS
Cannot change
Immediately upon saving change to EPO400-DEBUG.INI,
located at <CURRENT USER'S TEMP
DIRECTORY>\NAILOGS
Upon startup
Within one minute
Upon startup
Upon startup of Tomcat service
Cannot change
Upon startup of Tomcat service
Upon startup
Upon startup of Tomcat service
Within one minute
Within one minute
Upon startup
Cannot change
Cannot change
Advertisement
Table of Contents
Troubleshooting
