NIS 2010 v 17.8.0.5
Vista Home Premium 32 bit with Vista SP2
I know generally the items under the Symantec Eror Reporting are not serious issues. Howevere the most recent entry shows
the module name as
avModule
wondering what that means as far as the error and does it mean that my antivirus portion of NIS is messed up?
error ID is
E6F5A9BF-FDF8-4749-BC4A-CCB7E3F99F3C
Error Code
0x8000FFFF
Just want to make sure this DOES NOT mean that my AV portion of NIS is not working
Thanks
If Norton is showing green check marks and says it's secure or OK (I forget exactly how NIS 2010 indicates its status), then it is working. Again, Norton will inform you if it is not working properly by displaying a big red X somewhere. I am not sure about the specifics of this log entry, but as long as Norton shows green, you do not have to worry about whether the program is working or not. If the error had disabled your protection, Norton would alert you.
0x80000FFF is a Windows error to do with Windows or Microsoft updates. Check the support article to see if it applies to you.
delphinium wrote:0x80000FFF is a Windows error to do with Windows or Microsoft updates. Check the support article to see if it applies to you.
http://support.microsoft.com/kb/946414
Del, Thanks for the link. I read that and it seems to say something about problems downloading updates.
I have had no problems downloading updates, from Norton or Microsoft.
And if it is a windows updating issue, how does that effect NIS and the avModule?
Also- If I understand the whole symantec error reporting logging, I've been told that these are not anything that I need to do anything with.
But then the link you gave me seems to indicate tha I need to fix some microsoft issue, So how do Microsoft error codes have to do with Norton products?
So Now I'm somewhat confused. When one gets these symantec error reporting log entry, does one need to run a fix?
While that error code is used by Microsoft, I am certain that other companies also use it for their products. The fact that this code showed up in a Symantec Error report and pointed to a Norton component (avModule) shows that this is not related to Microsoft or Windows Update, but to NIS.
The last few times this issue came up, there were also a few Windows errors that were involved in the issue. Calls ran sfc /scannow and corrected some of them. Some of the others were Symantec related.
We still have an older product that he refuses to update to a version that has had the tweaks and corrections that cause some of these questions.
First let me say again that I always appreciate the help I receive here. Yes, I’m still using NIS 2010. But so are many other people I know. Even in these forums I see people using much older products.
I’’ just asking questions to try and understand things. I’m not ticked that 2010 has issues nor am I demanding answers.
I just sometimes have questions
and I post here because everyone has been helpful.
so when an issue comes up such as this one, I just try to see if anyone can help me understand better
As answered by SendOfJive, as long as you have the green light, there is no problem. Norton will tell you promptly if you need to worry. All systems and apps throw the occasional error. The only issue here is that it is being reported.
We also recommend updating to everyone, especially in the case of older products because much has been fixed in them. Continuing to use an older program and wondering about the errors is futile.
Hi Calls,
We are only a few months away from the 2012 version being released. Don't you think it is time to take the plunge and upgrade to 2011? 
Best wishes.
Allen
Calls, it looks like your machine encountered this problem twice on the 22nd. These are the only two errors reported from your system in the past month. Unfortunately, there wasn't enough data submitted to us for me to get a clear understanding of what happened but this issue doesn't appear to be very common and isn't seen at all in the 2011 products. Since the issue hasn't reoccurred you're probably fine.
Reese- Do these two images of the error report help any with getting additional information to explain what the error is and what the error means??
Basically- Does it mean that my AV portion of NIS is not working?
And do I need to do anything like run the microsoft SFC/scan now?
OR
Is MY NIS still protecting me as it is designed to even with this hiccup, that is- that the error may have happened, but NIS is still protecting me fully (as NIS 2010 is suppose to)?
I can say that I have been able to run Norton full system scans, quick scans, and idle quick scans as well as get def updates.
Calls wrote:
[...]
would these two screen images of the symantec error reporting help any?
[...]
Yes, they do.
The 'Severity' of this error in your older version is 'High'. In NIS 2011, the 'Severity' was only considered 'High' in the initial release. The severity has been Low in all subsequent revisions to NIS 2011:
| Date & Time | Error ID | Product Version | Module Name | Module Version | Error Code | Severity |
| 13/11/2010 06:03 | {A50C7C61-EDA4-49DD-A502-1EF1AAFF58F8} | 18.1.0.37 | avModule | 18.1.0.37 | 0x80040509 | High |
| 30/12/2010 23:15 | {69846BC7-2B63-43AA-B4E9-AD7113AED22D} | 18.5.0.125 | avModule | 18.5.0.125 | 0x80004005 | Low |
| 01/01/2011 14:03 | {7631E90D-9C14-42F2-BA1B-26CBE130DC45} | 18.5.0.125 | avModule | 18.5.0.125 | 0x80004005 | Low |
| 03/01/2011 18:27 | {301C3900-4A06-4F6D-AEB9-37FDFE6C52C7} | 18.5.0.125 | avModule | 18.5.0.125 | 0x80004005 | Low |
| 24/02/2011 19:54 | {07F6B485-6AB0-40FF-8D00-58531093DCA6} | 18.5.0.125 | avModule | 18.5.0.125 | 0x80004005 | Low |
| 06/03/2011 13:01 | {467FE1FC-CAA8-4394-B339-C4E428596B18} | 18.5.0.125 | avModule | 18.5.0.125 | 0x80004005 | Low |
| 08/03/2011 07:02 | {95D120D4-46E9-43CF-91B5-856A8E733D7C} | 18.5.0.125 | avModule | 18.5.0.125 | 0x80004005 | Low |
| 09/03/2011 06:58 | {526D2F86-7A5D-4B8A-8E0F-63B022133A3A} | 18.5.0.125 | avModule | 18.5.0.125 | 0x80004005 | Low |
| 10/04/2011 10:43 | {9A28A59A-41EB-4BB8-9DE4-B6F250A797DA} | 18.5.0.125 | avModule | 18.5.0.125 | 0x80004005 | Low |
| 11/04/2011 18:03 | {EB01AAF5-AB9F-46C9-AC24-5EBD2AE6A71A} | 18.5.0.125 | avModule | 18.5.0.125 | 0x80004005 | Low |
| 22/04/2011 18:36 | {8D8C4F9E-E947-4406-878A-71D3B74300C2} | 18.5.0.125 | avModule | 18.5.0.125 | 0x80004005 | Low |
| 25/04/2011 12:46 | {4D881694-0B04-4EAA-BAE8-FAD4D60DE897} | 18.5.0.125 | avModule | 18.5.0.125 | 0x80004005 | Low |
| 03/05/2011 14:21 | {925DBBFC-2722-44E0-A5FB-E2823B2E3F1D} | 18.5.0.125 | avModule | 18.5.0.125 | 0x80004005 | Low |
| 11/05/2011 23:47 | {767EFED2-6C60-4F46-AA82-9C2D05533C7A} | 18.6.0.29 | avModule | 18.6.0.29 | 0x80004005 | Low |
| 12/05/2011 16:27 | {39984B58-E98A-4480-A950-33F7401B3ED6} | 18.6.0.29 | avModule | 18.6.0.29 | 0x80004005 | Low |
| 13/05/2011 16:42 | {AE43BE54-FB50-4EEC-B50E-BE107B0922B3} | 18.6.0.29 | avModule | 18.6.0.29 | 0x80004005 | Low |
The error IDs above could be investigated, however, would the outcome actually be of any relevance to you? Despite both modules having the same name, it may be case of comparing apples with oranges, given that there are two different product versions involved here.
At the end of the day, you should still be protected though. I think that's the point of having two instances of ccSvcHst.exe running at all times.
Thanks
Reese-
Does this additional data I gave help you further?
Also is tha avModule referenced in the error log, the scanning function of NIS, like for the quick scan and idle quick scan?
Calls wrote:
Thanks
Reese-
Does this additional data I gave help you further?
Also is tha avModule referenced in the error log, the scanning function of NIS, like for the quick scan and idle quick scan?
All of the information in the screenshots you posted is also sent to us so there was nothing there that I hadn't seen before. Frequently when submissions are sent to us there are enough data to figure out exactly what was going on but in this case there just was enough information to be very useful. The problem was a non-fatal issue that the Norton detected on its own and recovered from automatically.
elsewhere wrote:
Calls wrote:
[...]
would these two screen images of the symantec error reporting help any?
[...]
Yes, they do.
The 'Severity' of this error in your older version is 'High'. In NIS 2011, the 'Severity' was only considered 'High' in the initial release. The severity has been Low in all subsequent revisions to NIS 2011:
[...]
The error IDs above could be investigated, however, would the outcome actually be of any relevance to you? Despite both modules having the same name, it may be case of comparing apples with oranges, given that there are two different product versions involved here.
At the end of the day, you should still be protected though. I think that's the point of having two instances of ccSvcHst.exe running at all times.
elsewhere, thanks for helping! There are a lot of factors (found in the advanced details) that go into determining whether one error is the same as another. The first and last items in the list that you provided are different from Calls' errors.
Your last item has to do with 'remembering' where to resume scanning when a scan gets interrupted and has already been resolved. The first item was a problem within a definitions package that has already been resolved as well.
Thanks Reese and all.
Between my questions and the answers that I received, I think I may be finally understanding what is meant in these symantec error reports as it pertains to the product user (Me)
Reese- If I may run by you my understanding, and you can tell me if am correct or off base?
I’ll use this most recent error reporting of the avModule
1. Am I correct to assume that avModule is the security scan function of NIS2010?
2. So in this example the avModule is suppose to run a certain way, but in this instance it did not run the proper way and was thus reported?
3. but for me the user, it started, did its job and was completed
(initied quick scan, scanned files, noted tracking cookies, and completed)?
4. but because it stuttered somewhere along the process, it was noted for the symantec folks to check out, but not a problem for the user (me) to be worried about?
Kind of like if I took a plane flight from NY to Los Angles. Maybe the pilot had to take a slighty different course or change altitudes a few hundred feet higher than originally planned, etc.
For the airline, they might need to know why the route did not go as planned or maybe took a llittle longer. But me as the passenger, I made my destination and it really didn’t stop me from arriving near on time, thus no need for me to be concerned?
Yes, Calls, I believe that you understand this correctly.
thanks, sorry I’m so dense.
So going forward, anytime some module, service, process or whatever part of NIS shows in the symantec error log, we the user need not be concerned. because despite the item being logged in the error log, it is still working and protecting, right?
Because whatever it is, it started, ran, and completed as far as me, the user is concerned?
I guess that always is the part that confuses/worries me, is the function, or module, etc still protecting me despite the “error”
Calls wrote:
thanks, sorry I'm so dense.
So going forward, anytime some module, service, process or whatever part of NIS shows in the symantec error log, we the user need not be concerned. because despite the item being logged in the error log, it is still working and protecting, right?
Because whatever it is, it started, ran, and completed as far as me, the user is concerned?
I guess that always is the part that confuses/worries me, is the function, or module, etc still protecting me despite the "error"
Unless the tray icon is missing, you will get a notification of any problems that you should be concerned about. If the tray icon is missing, you should restart your system.
