Reply
Visitor
bospenc
Posts: 1
Registered: ‎02-18-2011
Accepted Solution

MEDIUM - Unauthorized access blocked (access process data) Blocked

The below message is being written to the recent history log about 6 times a minute. Can I exclude it and if so.. how? 

 

MEDIUM - Unauthorized access blocked (access process data)  Blocked

Actor: c:\programs files (x86)TIVO\DESKTOP\TIVONOTIFY.EXE
Target: c:\programs files (x86)Norton Utilities 15\tools\disk doctor\disk\doctorSrvProxy.exe

 

 

Thank you in advancve!

SendOfJive
Posts: 9,887
Kudos: 4,189
Solutions: 706
Registered: ‎02-07-2009

Re: MEDIUM - Unauthorized access blocked (access process data) Blocked

Hi bospenc,

 

This is a Norton Product Tamper Protection event where Norton is blocking an outside program from accessing Norton files or processes.  It is not necessary, or possible, to disable the logging for these events.

Symantec Employee
Carlos_Linares
Posts: 81
Registered: ‎09-09-2008

Re: MEDIUM - Unauthorized access blocked (access process data) Blocked

Are you using NIS/NAV/N360 2010 or 2011?  We've addressed extraneous logging with our latest SONAR update (Feb 28, 2011)

Carlos Linares
SQA Analyst
Symantec Corporation
Contributor
NISBOB
Posts: 29
Registered: ‎03-04-2009

Re: MEDIUM - Unauthorized access blocked (access process data) Blocked

I'm still getting this.......running 18.5.0.125....live update current.

 

http://community.norton.com/t5/Norton-Internet-Security-Norton/Unauthorized-Access-Blocked-RoboTaskB...

SendOfJive
Posts: 9,887
Kudos: 4,189
Solutions: 706
Registered: ‎02-07-2009

Re: MEDIUM - Unauthorized access blocked (access process data) Blocked

[ Edited ]

Hi NISBOB,

 

Carlos Linares has been responding in threads dealing with an isolated problem that arose with Norton Product Tamper Protection where Norton was logging a huge number of "Set FIle Attributes" entries by mistake.  Your "Access Process Data" entries are different, and are probably not related to the issue, which is why you are still seeing your events in the logs.  Your situation seems like a normal logging situation rather than something wrong,