Endpoint Protection

 View Only
  • 1.  Issues with Content Monitor Tool on 12.1 (IO Issue)

    Posted Sep 27, 2011 03:21 PM

    Hello there,


    I have discovered the SEPM Content Monitor Tool and I am really liking its functionality in telling me issues about status with GUPs, etc..

     

    However, after having it running for the day, I am running into issues with it during launch.

     

    I get many errors like this in the console before the UI comes up:

    INFO: There is an IO issue while reading line 63722 in file C:\Program Files (x8
    6)\Symantec\Symantec Endpoint Protection Manager\apache\logs\access-2011-09-27.l
    og, so restarting from 63722

     

    I believe I made all the changes to the apache conf as specified in the text file.



  • 2.  RE: Issues with Content Monitor Tool on 12.1 (IO Issue)

    Posted Sep 27, 2011 03:34 PM

    Suggest you to put the path as \\localhost(or IP/HostName)\C$\......



  • 3.  RE: Issues with Content Monitor Tool on 12.1 (IO Issue)

    Posted Sep 27, 2011 03:42 PM

    The path where? All I have done is unzip the files into the tools folder and make the changes in the apache conf.



  • 4.  RE: Issues with Content Monitor Tool on 12.1 (IO Issue)

    Posted Sep 27, 2011 03:52 PM

    When you launch the the Tool and click on Config you get the Apache conf.

    There you must have given path for SEPM and IIS the same path should be put as \\localhost\C$\Program Files(x86)\Symantec\Symantec.......



  • 5.  RE: Issues with Content Monitor Tool on 12.1 (IO Issue)

    Posted Sep 27, 2011 04:50 PM

    I have changed this path but I still get the same error, now with a new path of \\localhost\C$\..etc



  • 6.  RE: Issues with Content Monitor Tool on 12.1 (IO Issue)

    Posted Sep 28, 2011 11:50 AM

    Are you able to go to start - run and put the path to open the location ?

    Also make sure to add "\" at the end of the path specified.



  • 7.  RE: Issues with Content Monitor Tool on 12.1 (IO Issue)

    Posted Oct 04, 2011 11:00 AM

    OK I think I see what's going on...

     

    It's not able to open the most RECENT access log file because it is locked (being written to by SEPM I suppose).

     

    Is this standard behavior with this tool?



  • 8.  RE: Issues with Content Monitor Tool on 12.1 (IO Issue)

    Posted Oct 04, 2011 02:51 PM

    I would think so..Best place to ask questions about this tool would be here

    https://www-secure.symantec.com/connect/downloads/sep-content-distribution-monitor