It seems that community watch is taking a long time to complete. On every run, it takes 4-5 minutes and does not drop to 0 minutes. Is there any way to test whether the connection to the Norton servers is working or it is slow.
It seems that community watch is taking a long time to complete. On every run, it takes 4-5 minutes and does not drop to 0 minutes. Is there any way to test whether the connection to the Norton servers is working or it is slow.
Not an answer - but something I have done. In NIS v 21, Settings > General > Other Settings > Norton Community Watch > switch to OFF and Apply!
yank wrote:
Not an answer - but something I have done. In NIS v 21, Settings > General > Other Settings > Norton Community Watch > switch to OFF and Apply!
Does switching off and on fixes the problem? It seems that the "community watch" items are not sent or changed to send later. They remain with "pending."
From HELP:
Norton Community Watch
The Norton Community Watch feature lets you submit any suspicious security or suspicious application data to Symantec for analysis. Symantec assesses the data to determine the new threats.
The Norton Community Watch view in the Security History window displays a list of files that you have submitted to Symantec for analysis. Files, at various stages of submission, also appear in the list.
So it would appear to me that what you are seeing is “normal” s in “at various stages of submission”
I can’t answer in regards to switching off and back on - I do not have the situation, so you’d have to test it - that has fixed some weird happenings in the past, but I feel you need to answer that question.
I have tried re-installing Norton, but Norton community watch is still not sending of the "statistical submission" or the "Norton commuity watch." It had only sent the IPS Statistical Submission.
How did you reinstall Norton? Did you remove it Via the Control panel, reboot, run the NRT, reboot and then install a clean download? Or did you use the Norton Remove and Reinstall Tool??
Control panel, reboot, NRT, reboot, install 2012, install 2013. That's the procedure for a clean re-install right?
Could a Norton server problem be causing the delays? But if I remember in the past, it simply changes from "pending" to "complete later" (or something like that) if connection to the Norton server fails.
Bump!
Hello
There is no need to install 2012 before you install 2013. You can run Norton Community Watch when ever you want by using the performance portion and then the Norton Tasks. There is a symbol next to the name and it will run the task. When you reinstall your product, then it has to submit everything over again. Also when a new version of the product comes out, it may slow down the task also.My Watch is down to 1 second now, but that depends if I have just installed a lot of new products or programs. I do have a new computer which is about a month old. I think though running the service on your own may speed up the service. Also the type of programs you use or install could slow things down. Thanks for reading...
floplot wrote:Hello
There is no need to install 2012 before you install 2013. You can run Norton Community Watch when ever you want by using the performance portion and then the Norton Tasks. There is a symbol next to the name and it will run the task. When you reinstall your product, then it has to submit everything over again. Also when a new version of the product comes out, it may slow down the task also. My Watch is down to 1 second now, but that depends if I have just installed a lot of new products or programs. I do have a new computer which is about a month old. I think though running the service on your own may speed up the service. Also the type of programs you use or install could slow things down. Thanks for reading...
Well you need 2012 if you want the local ID Safe. And it seems none of the "pending" tasks are sending or changing to "waiting." I cleared the logs and when the new entries come around, it sends. Maybe it's stuck on a file or something. Fingers cross that it does the job.
I think the problem lies with the fact that the "pending" task does not change to "waiting" if they could not be sent.
I typed this up yesterday and got called away for some "real-life activity" and forgot to post it - but better late than never I guess!
Dave20 wrote:Control panel, reboot, NRT, reboot, install 2012, install 2013. That's the procedure for a clean re-install right?
Yes that is the procedure if you are trying to keep your Local Vault.
Could a Norton server problem be causing the delays? But if I remember in the past, it simply changes from "pending" to "complete later" (or something like that) if connection to the Norton server fails.
My understanding is that the submission may not be sent immediately - but could be held (pending) until Community Watch connects to the server. Of course server glitches are always possible andf that's why I tend to wait a couple of hours and check things again - especially with failed LiveUpdates.
Well what I observed in the past is that pending changes to “waiting” if the software cannot upload a particular entry. It then moves on and trys another. If that too fails, the pending status changes to waiting. But now it seems this is no longer the case. The software chokes on a non sending entry and does not change “pending” to “waiting.” It was working that way on September 20 but Symantec must have pushed an update that causes the software to stall on a non-sending entry rather than change it from “pending” to “waiting” and try again later. Do you have the same problem with the 2013 version?
Now there is no “waiting” status and the software chokes on a non sending log.
Is it affecting the operation of our system?
If not, just wait a day or so to see if it runs correctly. If it is a server issue, it is the weekend, so it could take a little longer. This may be on a non critical server, so they may get to it Monday morning.
Not really a big affect other than NCW taking a long time to run. Can you confirm the behavior on your PC?
Basically, from September 20, none of the NCW log change to “waiting” and skipped over to be sent later.
It is now working as expected. Weird.
Glad it is sorted!
Sure sounds like it may have been a server glitch!