About Recovering A Corrupted Client System Log On 64-Bit Computers - Symantec 20032623 - Endpoint Protection Small Business Edition Implementation Manual

Implementation guide
Table of Contents

Advertisement

About recovering a corrupted client System Log on
64-bit computers

About recovering a corrupted client System Log on 64-bit computers

3
Add the following line to the hosts file:
xxx.xxx.xxx.xxx localhost #to log on to reporting functions
where you replace xxx.xxx.xxx.xxx with your computer's IP address. You can
add any comment you want after the pound sign (#). For example, you can
type the following line:
192.168.1.100 localhost # this entry is for my console computer
4
Save and close the file.
If the System log becomes corrupted on a 64-bit client, you may see an unspecified
error message in the System logs on the Symantec Endpoint Protection Manager
console. If corrupted, you cannot view the data in the log on the client and the
data does not upload to the console. This condition can affect data in the console
Computer Status, Risk, and Scan logs and reports.
To correct this condition, you can delete the corrupted log file and the serialize.dat
file on the client. These files are located on the client in Drive:\Documents and
Settings\All Users\Application Data\Symantec\Symantec AntiVirus Corporate
Edition\7.5\Logs\date.Log. After you delete these files, the log file is recreated
and begins to log entries correctly.
Troubleshooting reporting issues
329

Advertisement

Table of Contents
loading

This manual is also suitable for:

Endpoint protection small business edition

Table of Contents