Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
My system is a Vista Business with SP1 installed after uninstalling NIS 2008 ver 15.5.0.23, and reinstalling
NIS on top of SP1.
Kurt
Kurt wrote:Is this a serious error or can I ignore it?
Hi Kurt,
Sorry to hear you are having problems. Your question is brilliant. Hopefully we might arrive at a good answer for you.
I'm guessing that you have checked - no viruses and no other nasties. No bad sectors on your drives - all arrays are working perfectly well etc (basic house-keeping stuff).
Symantec tech support folk advised that the problem was caused by (or the cause of??) problems with updating your virus definitions file.
I have no idea what you mean by "cleared it by using the search function in NIS 2008". Could you please tell me what the function does and where it is? Just curious ....
If you can see that auto-protect is on (NIS panel - settings / basic security) then that should answer your question about whether or not this issue is a continuing real time problem. I'm guessing that auto-protect will be on. It it's not, see if you can turn it on.
.NET is used extensively throughout windows now (all flavours). Programs (including DLL's) can throw exceptions for a variety of reasons. Some are fatal and cause the system or program to fall over - as in "RUN AND HIDE - NIS 2008 is about to go nuclear" Some cause errors in passing - think in terms of threads. On first run an error is generated and the thread either concludes, branches or iterates (repeats) until a condition is reached (success / failure / loop).
Without knowing precisley what was said in your discussion with the Symantec support person - I am worried about the potential for your virus definitions to be out of wack. Can't tell until you look. Run liveupdate until there is nothing more to update. You probably know that there is an alternate way to update the definitions file - intelligent updater.
Below is what you see ... note the files are large executables and you need to pick the one which is appropriate for your product.
At least this way you will know that your definitions are OK.
The remaining issue is what to make of the error itself. I guess it depends upon your level of curiosity and patience. When previously happy systems break I like to know why. We all know that there have been large changes to Symantec products as well as FireFox, Windows (XP & VISTA). Miscrosoft and other vendors (CISCO for example) have released a plethora of patches to sort out a problem in the internet. All of these updates / patches may not be playing well together.
If you just want to sort this out as conservatively as possible (as in, don't take any risk that something might not be working properly), then you might consider getting rid of all the Symantec code / files via the Norton Removal Tool . This appears to be a simple process however i would urge everyone to exercise great care. While you might want to remove just one product (eg: NIS2008) the tool will remove ALL traces of every Symantec product on your system. If you have a few then this means a lot of work / downloads etc.
If you do have a number of Symantec products installed, I'd recheck with Symantec support before doing this ... it may be unnecessary. Even if they agree that you should do it there is no guarentee it will resolve the problem.
Gather all of the keys for all Symantec products and write them down. Set a restore point. I have no idea what special precautions might need to be taken with programs like Ghost / Go-Back / Save and Restore / Partition Magic. Tech support help pls :)
Certain products like Winfax *should* be OK if you just copy the data foldersto somewhere nice and safe (perhaps onto a USB stick).
Gird your loins and begin the removal process. This is what you will see - a pretty clear warning that this is serious stuff and a last chance to chicken out.
Follow the instructions ... repeat the process until all traces are really gone.
Then install each product. If you are only re-installing NIS2008 the process is pretty easy - follow your nose. Symantec support folk might have a preference in the order of installation if you have to do a batch install (eg: Winfax, System Works, Partition Magic etc through to NIS2008).
If you would like to see if there is a pattern / sequence causing your grief then give Mike Lin's StartUp Monitor and Startup control panel applet a try. They work perfectly well in XP. The Control panel applet works in Vista ... not so sure about the startup monitor.
The monitor does what it says and alerts you when any program attempts to alter your system startup settings (boot.ini / win.ini etc). Once alerted you can elect to allow the change or not. The control panel applet gives fine control of your start up settings so that you can strip things down to a base position and add things one at a time to see if a particular startup item triggers the error. It requires patience and there is no guarentee you will find the problem.
Still, it's a useful tool / approach to resolve pesky startup issues.
Here is a screen shot of the startup monitor at work:
And StartUp Control Panel applet:
As you can see (above) you have very fine control over almost everything that runs when your system starts up. It's a snap to alter the sequence of start up items and toggle them to see if a particular item is the cause of your problem.
I took the time to walk through this because the basic process can be applied to a range of trouble shooting situations.
Hope it helps ...
Hi Mike,
Thanks for your reply.
It covers most of the alternatives to troubleshoot this error. I will use as many as I need to find a solution
to the error 3035,5.
You wanted to know were I did the search in NIS 2008.
Under "Help & Support" after the connection is confirmed, lower left corner under "Support Resources"
there is the search function which I used.
The solution page ended with "What if this did not work".
Using this link gives you the "Live chat", which is the chat session I mentioned.
Kurt
Kurt wrote:
You wanted to know were I did the search in NIS 2008.
Under "Help & Support" after the connection is confirmed, lower left corner under "Support Resources"
there is the search function which I used.
The solution page ended with "What if this did not work".
Using this link gives you the "Live chat", which is the chat session I mentioned.
Hi Kurk,
Doh! Of course :) <g>