Thanks
so really no need for the user to check symantec error reporting log at all, eh?
Since anything in that log, DOES NOT indicate anything that would lessen protection, right?
sorry, trying to do this on my phone and no edit capabilities.
what I was really asking is that items in the symantec error log are NOT an indication that protection is lessened/off, are they?
The Symantec error log is not meant for general user observation. Having entries in this log does mean that protection is lessened.
Cool
Thanks Reese and everyone that helped me understand this.
One tiny last question, more of curiosity
In the symantic error log, these are listed as severity low.
But in the data of the error itself, the severity is listed as high
Why this difference in severity rating in 2 seperate locations?
Reese-
Did I read yor response correctly
Having entries in the Symantec Error Log
DOES mean protection is lessened?
reese_anschultz wrote:
The Symantec error log is not meant for general user observation. Having entries in this log does NOT mean that protection is lessened.
Oops, I mistyped. Having entries in the log does not necessarily mean that protection is lessened. You will be notified more directly if there are actual issues.
reese_anschultz wrote:
reese_anschultz wrote:The Symantec error log is not meant for general user observation. Having entries in this log does NOT mean that protection is lessened.
Oops, I mistyped. Having entries in the log does not necessarily mean that protection is lessened. You will be notified more directly if there are actual issues.
Hi Reese,
I am so happy that you clarified that! 
Had me wondering for a few seconds. 
Best wishes.
Allen
In NIS 2011, many errors that were deemed "high" in 2010 are now deemed "low". In fact, these instances of error reporting were MUCH more frequent in 2010 than in 2011. I have had like 2 or 3 in the past year, I think, while they popped up quite frequently with 2010.
I think I have a better understanding that I need not worry about what shows in the Symantec Error Log
But just when I think it is safe to go back in the water…
I know I need to upgrade to NIS2011, or even 2012, and I will
However for now I have NIS 2010 and these questions
I did take a look at the Symantec Error Log when I got home last night. Well low and behold if there was not another entry
However, this one seems a little different:
Product- NIS
Process Name- iexplore
Module Name- coIEPlg
Error Code- 0x80004005
I found coIEPlg as one of the add-ons in my browser. So I tried to find out what coIEPlg is and it seems like it has to do with the intrusion prevention.
I think I know the answers, but please indulge me this one last time on this issue, as the fact that the process name is not a symantec process, but internet explorer. So these are my final questions on the issue (I numbered them so that I can keep from confusing the answers):
1) Does this error mean that my intrusion prevention Is not working/protecting my browser? Or is the intrusion prevention still protecting me despite the reported error?
2) when the log shows error codes such as 0x8004005, are those symantec error codes or windows error codes? When I look this code up, as a windows error code it has something to do with J script. so are the codes in the log to be fixed by the user as windows error codes?
Thanks and I promise once I resolve these questions, I’ll mark as solved
Reese
I know you are busy, but if possible could you help me resolve the to remaining questions I have in my previous post?
Promise I will mark this resolved after that. Thanks
Calls wrote:
Thanks Reese and everyone that helped me understand this.
One tiny last question, more of curiosity
In the symantic error log, these are listed as severity low.
But in the data of the error itself, the severity is listed as high
Why this difference in severity rating in 2 seperate locations?
In NIS 2011, the Norton Error Reporting log assigns these records a Severity level of 'Info' rather than 'Low'. This confirms and reiterates what you've been told earlier about how much user interaction is required in response to entries like this... Looking closely at the screenshot below, you will see an entry with a 'Medium' Severity level. In NIS 2011, you would typically see an Autofix dialog box if you encountered an error like this:
Calls wrote:
I think I have a better understanding that I need not worry about what shows in the Symantec Error Log
But just when I think it is safe to go back in the water......
I know I need to upgrade to NIS2011, or even 2012, and I will
However for now I have NIS 2010 and these questions
I did take a look at the Symantec Error Log when I got home last night. Well low and behold if there was not another entry
However, this one seems a little different:
Product- NIS
Process Name- iexplore
Module Name- coIEPlg
Error Code- 0x80004005
I found coIEPlg as one of the add-ons in my browser. So I tried to find out what coIEPlg is and it seems like it has to do with the intrusion prevention.
I think I know the answers, but please indulge me this one last time on this issue, as the fact that the process name is not a symantec process, but internet explorer. So these are my final questions on the issue (I numbered them so that I can keep from confusing the answers):
1) Does this error mean that my intrusion prevention Is not working/protecting my browser? Or is the intrusion prevention still protecting me despite the reported error?
2) when the log shows error codes such as 0x8004005, are those symantec error codes or windows error codes? When I look this code up, as a windows error code it has something to do with J script. so are the codes in the log to be fixed by the user as windows error codes?
Thanks and I promise once I resolve these questions, I'll mark as solved
Honestly Calls, the core issue here is your hesitation to upgrade to NIS 2011. Do you update Windows without a thought when patch Tuesday comes around? If you do, then the same update methodology should apply to your chosen Security product as well. Your Norton Internet Security product is your first line of defence in terms of protecting your computer so your reluctance to upgrade your Security software seems odd to me...
Given that, please advise if any of the following Norton Errors presented below by my NIS 2011 machine are of any concern to you:
| Module Name | ccSvcHst | iexplore | nu | (blank) | Grand Total |
| ACCTMGR | 1 | 1 | |||
| asEngine | 2 | 2 | |||
| avModule | 16 | 16 | |||
| AVPAPP32 | 1 | 1 | |||
| avScanUI | 1 | 1 | |||
| ccEraser | 2 | 2 | |||
| ccipc | 3 | 3 | |||
| cowpplg | 1 | 1 | |||
| DuLuCbk | 1 | 1 | |||
| hsui | 2 | 2 | |||
| isDataPr | 5 | 5 | |||
| ISDATASV | 8 | 8 | |||
| mshtml | 1 | 1 | |||
| NAVLogV | 3 | 3 | |||
| NCW | 206 | 206 | |||
| NPCStats | 2 | 2 | |||
| ntdll | 1 | 1 | |||
| NUMEng | 6 | 6 | |||
| NumGui | 1 | 1 | |||
| rpcrt4 | 1 | 1 | |||
| SCANLESS | 4 | 4 | |||
| symhtml | 1 | 1 | |||
| uialert | 1 | 1 | |||
| (blank) | 7 | 7 | |||
| Grand Total | 263 | 6 | 1 | 7 | 277 |
Thanks
I appreciate the help from everyone.
Obviously if I could answer your question about the errors you posted, then I would not have the questions I do.
Yes I need to upgrade to 2011, but am I really one of only a few who still use 2010? Many people I know still use 2010.
Granted I may be one of a few using 2010 that still have so many questions.
But again I do appreciate everyone’s help. I was just asking if perhaps Reece could address my last 2 questions, if he has time
Thanks all
Hi Calls,
I do understand your reluctance. Many who are still on the 2010 version (or even earlier) are there because they don't realize they can upgrade for free to the latest year and don't realize that the newest product year also has additional protection which you won't get with a prior year product. Not to mention bug fixes and improvements in usability, etc.
In your case, you do recognize all of this since you are on the Forum regularly.
Best wishes.
Allen
Hi Calls,
CoIEPlg is the Norton Toolbar, not IPS. I am not sure what the error code relates to but it has no relevance for the user anyway. Are you telling me that you could recognize exactly what the problem was if only you knew whether this error code was specific to Symantec or Windows? I couldn't. The error codes, like the submissions themselves, are for the use of the Symantec team in evaluating the performance of the product - it means something to them. I am not sure why you are asking about this.
c:
> Granted I may be one of a few using 2010 that still have so many questions.
No ... kidding.
You're:
1) using an out of date product,
2) refuse to update to the current product,
3) awfully needy,
4) take the time of the helpful volunteers who could be helping others who have _legitimate_ problems with the _current_ product.
> Many people I know still use 2010.
When you're old enough to take a Logic class you'll understand the error in this. It will be covered under Inductive Reasoning.
> I think I may be finally understanding what is meant in these symantec error reports as it pertains to the product user (Me)
Here's what I don't understand. You're obsessive about minor error messages, demanding multiple, detailed answers
> sorry I'm so dense
which you don't understand, but at the same time _refuse_ to use the current product, for no good reason, which would solve some of those problems.
And, beneficially, you could identify problems with the current product, which would help both Symantec and other users.
am>
> Many who are still on the 2010 version (or even earlier) are there because they don't realize they can upgrade for free
> to the latest year and don't realize that the newest product year also has _additional protection_ which you won't get
> with a prior year product. Not to mention _bug fixes_ and improvements in usability, etc.
Exactly. And calls cannot use that as an excuse, since he's been told this frequently. Perhaps he's just lonely.
Joen, why such an angry and demeaning response?
I think I make it clear that I appreciate the help people offer. I never, I beleive, demeand answers from volunteers.
Never is my question, "Should I upgrade?" If that were my question then I too would be angry that I dont follow the advice. But my question is specific to a product that Norton still maintains support for. Therefore I ask questions.
Perhaps the forums can create another subforum for those who are not using the current product, this way we don't offend those using the current product
I'm sure those who run the Microsoft Forums are constantly shaking their heads about those who continue to use the XP OS even though Microsoft has created two newer OS
I don't want to sound angry, but while I do ask many stupid questions, I do not feel I have ever been disrespectful to those who take the time to answer. At least I hope I have not been.
And again I don't want to sound ungrateful.
Maybe the forum rules need to be clear that if you are using an older product and have a question, do not ask those questions. Just upgrade, but don't ask the questions.
I am really sorry if I have forced people into wasting their time trying to help me.
SendOfJive wrote:Hi Calls,
CoIEPlg is the Norton Toolbar, not IPS. I am not sure what the error code relates to but it has no relevance for the user anyway. Are you telling me that you could recognize exactly what the problem was if only you knew whether this error code was specific to Symantec or Windows? I couldn't. The error codes, like the submissions themselves, are for the use of the Symantec team in evaluating the performance of the product - it means something to them. I am not sure why you are asking about this.
thank you SoJ for your reply
I only asked about the error codes, because earlier in this thread there wqas some speculation that the error codes related to Microsoft error codes. And if that were the case, I was wondering if I should run the microsoft fixes.
However, when I look at some of the error codes and check them as microsoft error codes, they make no sense
But I was just checking on that particular issue.
Once again, thanks.
Calls wrote:
[...]However, this one seems a little different:
Product- NIS
Process Name- iexplore
Module Name- coIEPlg
Error Code- 0x80004005
[...]1) Does this error mean that my intrusion prevention Is not working/protecting my browser? Or is the intrusion prevention still protecting me despite the reported error?
2) when the log shows error codes such as 0x8004005, are those symantec error codes or windows error codes? When I look this code up, as a windows error code it has something to do with J script. so are the codes in the log to be fixed by the user as windows error codes?
Thanks and I promise once I resolve these questions, I'll mark as solved
As SendOfJive pointed out, this is an error in the toolbar. There was a product update on the 20th that introduced this and it is currently being researched. It does not affect your security.
The error codes are Symantec codes but frequently we reuse Microsoft codes so sometimes understanding the Microsoft error code will help understand the Symantec error.
reese_anschultz wrote:
The error codes are Symantec codes but frequently we reuse Microsoft codes so sometimes understanding the Microsoft error code will help understand the Symantec error.
Thank you Reese-
I'll make this real simple for me to understand the answer
So since the error code sometimes is the same a windows error code,
(in this case where the error code is 0x80004005, which for Microsoft error code means something about the jscript.dll)
does one need to follow the microsoft fix for that error code?
OR
Since not ALL of the error codes are exactly the same as the microsoft error codes, in the case of ANY AND ALL of these Symantec errors, the user needs to do NOTHING unless notified by Symantec/Norton directly?
joen wrote:c:
> Granted I may be one of a few using 2010 that still have so many questions.
No ... kidding.
Please let's keep it polite. Calls is obviously reluctant to upgrade for reasons of his own but we're always happy to help out when we can.
Best wishes
Allen