Norton Internet Security / Norton AntiVirus

[Calls]

NIS 2010 17.8.0.5

Vista Home Premium 32 bit with Vista SP2

Ok I know that the symantec error reporting thing is usually nothing for the user to worry about

But this one involves

Process Name ccSvcHst

and

Module Name ccEraser

So This REALLY concerns me

Here are screen shots of what shows in the NIS history under Symantec Error Reporting

 this makes me worry that:

1. My NIS is not functioning correctly

2. That the real time protection may be compromised

3. That the scanning  process might not be working right

[SendOfJive Norton Fighter]

Hi Calls,

The Norton icon in your system tray is showing a green checkmark.  If your product was in an error state the icon would show a red X. 

[Calls]

Thanks SoJ

Like I said, I am much more concerned about this one, due to the fact it involves  ccSvcHst and ccEraser

[Mitka Spam Squasher]

Most likely, I would think that Norton is able to recover from the error condition. However, it logs it and submits it back to Symantec servers as statistics.

Mitka

[reese_anschultz]

Thanks, Calls, for the error report. This is a known issue that is currently being investigated. As indicated in the details, it has a Low severity and isn't reducing your security. Should a fix become available, it will be automatically deployed through regular definitions updates.

[Calls]

so let me see if I'm finally understanding this.

1. It is a glitch or hiccup type error that causes the program to not work in the way it is intended. What does ccEraser do anyway?

2. This glitch has been reported elsewhere? Is it something newly discovered?

3. But the functioning of the product and the security is not effected because the function still is completed, even though there is a hiccup?

4. Does this mean that everytime there is this same hiccup for this module, ccEraser when it runs or just this one time as evidenced by the error report?

5. And if say this were the newest version (2011), then most lilely a fix qould be created to make it work without the periodic hiccup?

6. But in the end, the security and functioning ( as far as security level)  has NOT been compromised and my NIS 2010 is still functioning securely?

[reese_anschultz · Accepted solution]

See my comments inline below...

---

Calls wrote:

so let me see if I'm finally understanding this.

1. It is a glitch or hiccup type error that causes the program to not work in the way it is intended. What does ccEraser do anyway?

Yes, some unexpected/unanticipated behavior was detected within our program and sent to Symantec for further analysis.

2. This glitch has been reported elsewhere? Is it something newly discovered?

Yours isn't the only system to submit this to our servers and people were already looking into it when I started researching it.

3. But the functioning of the product and the security is not effected because the function still is completed, even though there is a hiccup?

 Yes

4. Does this mean that everytime there is this same hiccup for this module, ccEraser when it runs or just this one time as evidenced by the error report?

 I don't know what conditions are required to exhibit this 'hiccup' and therefore don't know the frequency. As indicated by your logs, it doesn't happen all the time.

5. And if say this were the newest version (2011), then most lilely a fix qould be created to make it work without the periodic hiccup?

Assuming that the issue is fixable, a fix can be made for any version although fixes for the current version usually get addressed first while fixes to older versions are generally only made if the issues impact security and/or user experience.

6. But in the end, the security and functioning ( as far as security level)  has NOT been compromised and my NIS 2010 is still functioning securely?

Correct

---

[Calls]

Thanks Reese

I mostly want to make sure that none of this means my security and functioning is compromised in the sense that I'm unsafe. And you have answered that for me.

I have one more question just to help me understand these types of issues.

When an error gets logged, such as this one which involves ccSvcHst and the ccEraser Module, does this mean:

1. that the ccEraser module attempted to run and for some reason was not able to and thus the entry was created on the error log. But then the eraser module ran in an alternative way?

or

2. that the ccEraser module attempted to run and for some reason was not able to and thus the entry was created on the error log. But then the eraser module ran again but in the CORRECT way?

also any easy quick explanation of what ccEraser does?

[Calls]

Guess what I'm wondering that (in this instance) did ccEraser try to run and there was a problem resulting in the error log, then try to run again and worked? Or ran in a different way to work?

I'm thinking ccEraser runs when one does a scan? And have have done many scans since the error was logged, so does that mean these other times it is working correctly and it was just that once that an error happened?

[Bombastus]

The error doesn't happen at any other time that when it is logged.