Norton\Symantec AV, 2003, Plus NSW Flaw
Straight_Man
Geeky, in my own wayNaples, FL Icrontian
Time Sensitive, Date October 04, 2003-- Ignore after October 12, 2003 unless further thread posts indicate problems still of this sort.
Please note that if you a fatal error on a NSW Common CLient update from LiveUpdate today, the best fix is TO REJECT the Common CLient update offered on 10\03\03 and 120\04\03 as there IS an archive defect-- after reloading NAV in its entirety byb uninstalling and reinstalling NAV and REJECTING the Common Client update on Symantec's LiveUpdate Server. I was kinda disgusted today when I got to install NAV (as part of NSW Pro 2003) 3x to get it running 1X, then went home and got the same thing on my box, got to reload ONLY NAV there also. Needless to say, ATE 4 hours of time as there is no way this is customers fault or billable.
If you get an error while upgrading Common Client, and the message that results has a details button, click the details button and then see if you see a reference to a file path ending with file name Webwnddll.dl^ If so, you can try shutting down windows immediately, though Windows might record the change anyway. If it does, you are likely to get a message from NAV that it is missing components after this upgrade, and Symantec says that with that generic error you can get to reinstall up to all Symantec products. In this case, looks like only NAV needs to be reloaded.
I do not know if this exists as a problem with NAV 2004, or if that archive is offered for that version, but the archive is 483 K apoproximately, so if you manually LiveUpdate I woudl wait a week before accepting a common client update of that size-- NAV 2003 runs FINE without it, and BREAKS with it. This is NOT a NAV specific update, it is Common Client only, so you cAN accept NAV and NAV def updates-- just please uncheck the Common Client update if ti is about 483 K.
Symantec HAS been told this is what is wrong, and I expect by next weekend it will be fixed. They have been asked to replace archive and force a new patching of Common Client without the archive problem. So, if you want to wait a week or so, your NAV might start working again if it does not, but I am too paranoid about viruses right now for that, so Ireloaded my NAV and just rejected the common client update.
Replicated on XP, 98, and 98SE on dialup and braodband internet boxes, one dialup box 3 times to figure out avoidance strategy for this thing.
John.
Please note that if you a fatal error on a NSW Common CLient update from LiveUpdate today, the best fix is TO REJECT the Common CLient update offered on 10\03\03 and 120\04\03 as there IS an archive defect-- after reloading NAV in its entirety byb uninstalling and reinstalling NAV and REJECTING the Common Client update on Symantec's LiveUpdate Server. I was kinda disgusted today when I got to install NAV (as part of NSW Pro 2003) 3x to get it running 1X, then went home and got the same thing on my box, got to reload ONLY NAV there also. Needless to say, ATE 4 hours of time as there is no way this is customers fault or billable.
If you get an error while upgrading Common Client, and the message that results has a details button, click the details button and then see if you see a reference to a file path ending with file name Webwnddll.dl^ If so, you can try shutting down windows immediately, though Windows might record the change anyway. If it does, you are likely to get a message from NAV that it is missing components after this upgrade, and Symantec says that with that generic error you can get to reinstall up to all Symantec products. In this case, looks like only NAV needs to be reloaded.
I do not know if this exists as a problem with NAV 2004, or if that archive is offered for that version, but the archive is 483 K apoproximately, so if you manually LiveUpdate I woudl wait a week before accepting a common client update of that size-- NAV 2003 runs FINE without it, and BREAKS with it. This is NOT a NAV specific update, it is Common Client only, so you cAN accept NAV and NAV def updates-- just please uncheck the Common Client update if ti is about 483 K.
Symantec HAS been told this is what is wrong, and I expect by next weekend it will be fixed. They have been asked to replace archive and force a new patching of Common Client without the archive problem. So, if you want to wait a week or so, your NAV might start working again if it does not, but I am too paranoid about viruses right now for that, so Ireloaded my NAV and just rejected the common client update.
Replicated on XP, 98, and 98SE on dialup and braodband internet boxes, one dialup box 3 times to figure out avoidance strategy for this thing.
John.
0