Endpoint Protection

 View Only

  • 1.  LogReaderEvents Error

    Posted Feb 09, 2008 10:55 AM
    Good day all,
    I updated my Antivirus server the other day (to 10.1.6.60 version) and now I have a boat load of errors in my Application log on that server.  Here is the body of the error:

    -----
    Source: LogReaderEvents
    Category: None
    Event ID: 1

    Description:
    The description for Event ID ( 1 ) in Source ( LogReaderEvents ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Label not found for "last FILELOOP" at C:\Program Files\Common Files\Symantec Shared\Reporting Agents\Win32/sub_logreader.pl line 363.
    -----

    Anyone run into this one before?  Any thoughts on how I can remedy this?

    Again, I updated the server (by selecting "Install Symantec AntiVirus" then selecting "Install Symantec AntiVirus Server" then selecting "Update Symantec AntiVirus server" when running the setup.exe).  I also uninstalled the old Symantec System Center Console and installed the newer version, but I don't remember messing with the reporting agents/options.

    Any input would be appreciated.
    Thanks in advance!

    -Paul


  • 2.  RE: LogReaderEvents Error

    Posted Feb 11, 2008 04:30 PM
    I'm having the same issue. It looks like it started for us out all of a sudden on 01-30-08 at around 10pm. Nothing has been changed on the system. I've googled around and do not see anything about this error.
     
    Event Type: Error
    Event Source: LogReaderEvents
    Event Category: None
    Event ID: 1
    Date:  2/11/2008
    Time:  3:17:56 PM
    User:  N/A
    Computer: %computername%
    The description for Event ID ( 1 ) in Source ( LogReaderEvents ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Label not found for "last FILELOOP" at C:\Program Files\Common Files\Symantec Shared\Reporting Agents\Win32/sub_logreader.pl line 363.



  • 3.  RE: LogReaderEvents Error

    Posted Feb 12, 2008 09:14 AM
    That's interesting; same error/line in that PL file.

    I called support last night and the tech I talked with had me try a few things, but we weren't able to get it fixed-up by the time I had to leave for the night.  He wanted me roll-out the updated client across my network, but I can't do that right now; I work at a financial services firm and now is our busy season (Taxes and such), so I can't make ANY changes to my users' systems (as minute as it may be).

    I'm still baffled on this one.  If I get any information I'll pass it along.  Until then...

    Any Symantec mods/employees read this thread yet?  Any ideas???  Thanks!  :-)


  • 4.  RE: LogReaderEvents Error

    Posted Feb 27, 2008 10:02 AM
    Bump
    I'm still having this problem.  I've been in contact with support a few times and they've suggested a few things (including updating the server to 10.1.7, which screwed up EVERYTHING and I had to restore a backup of the PKI folder and edit a handful of registry keys), but I'm still getting this error.

    This is quite annoying that this hasn't been resolved yet.


  • 5.  RE: LogReaderEvents Error

    Posted Jul 22, 2008 02:58 PM
    I am another one having this same issue.  Running 10.1.7.7000.  Log filled with entries.  I too would be very interested in a solution.  Good luck to all.


  • 6.  RE: LogReaderEvents Error

    Posted Jun 24, 2009 03:17 PM
    Try clearing the following directory on the reporting server: C:\Program Files\Common Files\Symantec Shared\Reporting Agents\Win32\Temp.LogReader

    It appears we had some corrupt files and now reporting is working.

    Hope this helps