I had none of the major bugs encountered by others until tonight(?) when I turned on PC and subsequently connected to the web. LiveUpdate was the first order of business.
Web protection failed to update. Error: 8920, 223. I followed what seemed like the intuitive protocol and the NIS 2012 claimed Autofix repaired 1 item with Installation :: Success.
Norton Internet Security 19.1.1.3 Error: 8920, 223 Windows 7 Home Premium 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Norton Autofix Results: 1 item(s) Installation :: Success
I ran LiveUpdate again with the same failed result. This time, autofix wasn't offered and a reinstall was.
Before I go through the hassle of a reinstall, is the error simply a disconnect with the web protection server? There have been times these past two weeks when LiveUpdate would not even begin the process.
Is there a central source of info for error codes available to the users?
After I composed the above, I ran LiveUpdate again(!) and this time, there were no failures. Imagine the wasted time and bandwidth if I had gone through with the reinstall!
The issue is the lack of information for me to make an informed decision to act intelligently.
From what was limitedly presented to me by the user-interface, if I had taken the leap-of-faith that NIS 2012 knows best, I would have went with a reinstall. While a reinstall is not life-altering, it was nevertheless unnecessary.
You can enter the error code into the Symantec site search box located in the upper right corner of most Norton web pages. In this case, you would have been referred to a support article stating:
"This error can appear due to a temporary problem with the LiveUpdate servers. You can be assured that this problem will be fixed quickly. Please wait for 24 hours and then run LiveUpdate again..."
It was rather odd that when I first encountered the failure/error code, the link(s) ought to have sent me to the link SendOfJive provided. Certainly, the output I received NIS2012 could have just as easily parsed. Instead, it autofixed something(?). When the sequence was repeated, clearly, NIS2012 recognized a prior attempt or prior fix was no solution. Again, the output error code was still available to parse and branch to the appropriate link. Instead, a reinstall was the ONLY solution offered, the panacea to cure all problems.
I must revoke the solved for this thread! There was no support at the other end!
A new error code, 3048,3, has appeared recently for others, but not for me. The alleged solution for this thread would have applied for the new one. I went to the support link and input the error code. The support solution was the same as I received for my error code-- i.e. restart, uninstall, remove, reinstall. As we know from my error code encounter, the only solution(s) offered was not applicable! I just had to wait for the server(s) to be fixed. Thank goodness I didn't go through the generic panacea.
If there was a central database of error codes and a short descriptions of what might be involved in the causation of error, ...