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.
MelodicWynd wrote:hi fortnotes - i'm guessing that we are still in the configuration mentioned in this thread:
http://community.norton.com/norton/board/message?board.id=nis_feedback&thread.id=496
is this scheduled liveupdate done through the program or via the Windows task scheduler? when i schedule it from within the program, it shows up in the log. i haven't tested via the Windows task scheduler.
do you should see quick scans listed almost daily, as they are kicked off after LiveUpdate brings down new defs.
mel
No, I'm not talking about the LiveUpdate case here. I'm talking about a full system scan, which I have scheduled through the program. If I initiate a scan through the program (or from Windows Explorer to scan a specific file), I see these scans show up in the Log Viewer. However, the automatically scheduled full-system-scan never seems to show up in the log viewer.
hi fortnotes - sorry for the confusion on the other thread - i was referring to it in terms of OS configuration, which i should have just come out and ask... the reason for asking about it was due to other threads that appear to have found a problem with Vista-based scheduling. as you are using the program scheduler, i understand that there is no longer a dependency on the Window scheduler.
so to confirm - program log viewer displays all scans except for the automatically scheduled scans. the quick scans, individual programs scans, all show up properly. so it would appear that there is an unknown program scheduler dependency that we're going to need some SYMC help on... bueller?
mel
MelodicWynd wrote:hi fortnotes - sorry for the confusion on the other thread - i was referring to it in terms of OS configuration, which i should have just come out and ask... the reason for asking about it was due to other threads that appear to have found a problem with Vista-based scheduling. as you are using the program scheduler, i understand that there is no longer a dependency on the Window scheduler.
so to confirm - program log viewer displays all scans except for the automatically scheduled scans. the quick scans, individual programs scans, all show up properly. so it would appear that there is an unknown program scheduler dependency that we're going to need some SYMC help on... bueller?
mel
Yes, you are correct in what you are confirming. However, I do see that when I use the program to automatically schedule a full system scan, it does appear in the OS scheduled task list. (I should state that I'm using XP and NIS 2008) So, NIS is putting the automatically scheduled scan in the system task scheduler for me. I have been able to observe that the scan does run, its just that the record of it does not show up in the Log Viewer.
Hi Footnotes,
Please check the Security History to see if the scan appears there. The 2007 and 2008 versions of NIIS have Security History which is another more detailed log then the Activity log. To get to Security History, on the left pane of the program, click View History. You will see the recent history listed and if the scan was run, it should appear there.
Let me know if the scan appears.
Rich
RichC wrote:Hi Footnotes,
Please check the Security History to see if the scan appears there. The 2007 and 2008 versions of NIIS have Security History which is another more detailed log then the Activity log. To get to Security History, on the left pane of the program, click View History. You will see the recent history listed and if the scan was run, it should appear there.
Let me know if the scan appears.
Rich
I checked there, and I do see quick scans showing up which seem to come as a result of LiveUpdates. I'll check again on Saturday morning to see if the automatically-scheduled full-system scan shows up. Thanks for the pointer.
fortnotes wrote:
RichC wrote:Hi Footnotes,
Please check the Security History to see if the scan appears there. The 2007 and 2008 versions of NIIS have Security History which is another more detailed log then the Activity log. To get to Security History, on the left pane of the program, click View History. You will see the recent history listed and if the scan was run, it should appear there.
Let me know if the scan appears.
Rich
I checked there, and I do see quick scans showing up which seem to come as a result of LiveUpdates. I'll check again on Saturday morning to see if the automatically-scheduled full-system scan shows up. Thanks for the pointer.
I looked after my full-system scan ran this morning, and I see a disturbing result.
The scan started at the scheduled time, and apparantely ran to completion, but the record of the scan did NOT show up in the Security History. I went into the Scheduled Tasks of the system control panel, and I showed me that the full system scan was *still* running. There was no system activity happening however. The task manager showed me that navw32.exe was still running (though it was not accumulating any CPU time). When I selected the "running" task in the scheduled tasks window and told it to end the task,
the navw32.exe went away, and all of a sudden the scan information showed up in the Security History window. The information there seemed to be correct, including the amount of time the scan took.
So, why does the scheduled full-system scan not complete on its own? I need to log into the system and kill the scan process before it finishes and tells me what happened. In one case, I have another scheduled scan that runs prior to the system rebooting, and when the system reboots, the scan information gets lost.
This is frustrating! Why is it so hard to get these things running in an unattended manner? I can't afford to have them run during the day when people are on the system, because the system gets unusable when a system scan or live update are happening.
OK, so I have a full system scan schedules to run at a specific time. When that time came along, I can tell the scan started because the disk on the machine got real busy. It lasted about an hour, which is about the correct timeframe, and then stopped. However, when I go into the Log Viewer, and look at the Protection Activities log, I do not see any evidence of this scan having been run. This viewer only seems to show scans that I manually started while I was logged in. Where Can I see the results of an automatically scheduled scan?
hi fortnotes - are there any switch settings on the scheduled scan displayed in the Windows Scheduler? it seems like the scan is gacking on something that is preventing completion - you might try adding a /noresults switch to the navw32 item - there are other switches that you might try (found in help chm file under command lines) to see if you can further narrow the snag.
mel
Hi I am having the same problem with my new laptop running Window Vista. I had a tech install Norton Internet Security 2008 . And have not been able to have a full system scan complete. It comes up with an error 0x800706BE. Even if a scan completes…it will not show ever having been preformed. It only shows quick scans complete. Is there anybody out there that knows how to fix this?
hi misskitty - i recall a post that mentioned a similar problem that recommended using AutoFix, which in 2008 is accessed through the in-product Help / Support link.
if that doesn't work for you, i'd be interested to know whether you have the add-on pack installed, or have added Vista SP1. and if there is anything in the error log. here's how to check:
1. within the program, click the Norton Internet Security tab
2. open the Reports and Statistics section
3. click "View Activity Log".
4. at the bottom will be an Error Messages section.
anything listed there?
mel
MelodicWynd wrote:hi fortnotes - are there any switch settings on the scheduled scan displayed in the Windows Scheduler? it seems like the scan is gacking on something that is preventing completion - you might try adding a /noresults switch to the navw32 item - there are other switches that you might try (found in help chm file under command lines) to see if you can further narrow the snag.
mel
There is one switch setting which was added by NIS: /TASK:"C:\Documents and Settings\All Users\Application Data\Symantec\Norton AntiVirus\Tasks\mycomp.sca"
I assume that this switch points it to the configuration file telling it exactly what to scan.
I will try adding the /noresult switch and see what happens. That could be the issue, since nobody is logged into the system at the time the scan runs.
Hi footnotes,
OK.. so from your description, it appears that the scheduled scan is starting but not finishing.. I would like to verify that you have been able to run a full system scan when the scan is not part of the scheduled scan.. Is that correct? If not, try running a full system scan when you are logged on and let me know if it completes successfully.. include the number of files scanned and the time that the scan took to finish...
You also mention that you are not logged on at the time that the scan is scheduled to run... I did not see in the thread any mention of what to do in this case.. We have seen some problems with the scan running when the user is not logged in. To fix the problem, you should go to Windows task scheduler, right-click the Norton Internet Security - Run Full System Scan entry, choose Properties; on the Task tab, uncheck Run only if logged on and check Enabled. Then click Set Password and enter your user password in the Password and Confirm Password fields and then click OK.
Let me know if this helps.
RichC
RichC wrote:Hi footnotes,
OK.. so from your description, it appears that the scheduled scan is starting but not finishing.. I would like to verify that you have been able to run a full system scan when the scan is not part of the scheduled scan.. Is that correct? If not, try running a full system scan when you are logged on and let me know if it completes successfully.. include the number of files scanned and the time that the scan took to finish...
You also mention that you are not logged on at the time that the scan is scheduled to run... I did not see in the thread any mention of what to do in this case.. We have seen some problems with the scan running when the user is not logged in. To fix the problem, you should go to Windows task scheduler, right-click the Norton Internet Security - Run Full System Scan entry, choose Properties; on the Task tab, uncheck Run only if logged on and check Enabled. Then click Set Password and enter your user password in the Password and Confirm Password fields and then click OK.
Let me know if this helps.
RichC
Yes, I have been able to run a full scan while logged in. It scanned 355,305 items and took 43 minutes 52 seconds. When nobody was logged in, the scan still ran, scanned the same number of items in the same amount of time, but nothing was logged in the Security History until I went in with task manager and terminated the navw32.exe process. After forcing it to terminate, the results show up in the Security History.
I had already unchecked the "Run only if logged on" box, which is what allows the scan to run, but does not allow it to update the history.
I also tried adding the /NORESULT switch to the command line, as was suggested in this thread, and that causes the scan to not run at all, and it exits immediately with a result code of one.
Hi . When I opened up to check for View Log activity. It showed none to view.
In the Errors section…there was nothing to view.
Hi misskitty,
Thanks for the info... did you set up the scan to run when a user is not logged in? I provided those steps to footnotes in an earlier reply:
"To fix the problem, you should go to Windows task scheduler (Start>All Programs>Accessories>System Tools>Scheduled tasks), right-click the Norton Internet Security - Run Full System Scan entry, choose Properties; on the Task tab, uncheck Run only if logged on and check Enabled. Then click Set Password and enter your user password in the Password and Confirm Password fields and then click OK."
Please try those steps and let me know if the scan runs.
RichC
Hi fortnotes,
Scheduled scans will not run if you are not logged in. Can you please try again to run a scheduled scan while you are logged in and see if you see the logs in the viewer?
Thanks!
fortnotes wrote:
Yes, I have been able to run a full scan while logged in. It scanned 355,305 items and took 43 minutes 52 seconds. When nobody was logged in, the scan still ran, scanned the same number of items in the same amount of time, but nothing was logged in the Security History until I went in with task manager and terminated the navw32.exe process. After forcing it to terminate, the results show up in the Security History.
I had already unchecked the "Run only if logged on" box, which is what allows the scan to run, but does not allow it to update the history.
I also tried adding the /NORESULT switch to the command line, as was suggested in this thread, and that causes the scan to not run at all, and it exits immediately with a result code of one.
OK, I think I finally got things working.
First of all, the /NORESULT does not work at all. While it is a documented option, it appears to be unsupported. If I run navw32 /NORESULT from the command line, all I get is a help window saying it does not know how to solve the problem. If this option is really not supported, then it should be taken out of the documentation.
Secondly, I had earlier noticed that if I have the scan run, it hangs at the end, and if I kill the process, then the scan record gets recorded in the log. Well, today I realized that I can not kill that scan from the task manager (no permission). I have to abort the task from the Windows task scheduler window in the control panel.
This discovery lead me to the solution: if I bring up the scheduled scan in the task scheduler window, and go to the settings tab, I can tell it to stop the task if it runs too long. I just set the duration to be approximately half an hour longer than the expected scan time (for safety). I also have the "Wake the computer to run this task" selected. And in the Task tab, I have "Run only if logged on" unchecked.
The end result is that the task scheduler will wake the computer from suspend state, start the scan, and then after a period of time, it will stop the scan. This causes the scan record to get entered into the NIS History log. Now all is fine.
One further note: Somebody else said that the scan will not work if nobody is logged in. This is not true. If you uncheck the box in the task scheduler window, it will run. It makes no sense to have the scheduler try to run something that requires you to be logged in, because you never know when somebody might or might not be logged in. Also, I found that if the scheduler runs a scan that requires you to be logged in, and you happen to be loggedin, the scan will begin running, but you still get no scan record in the log unless you are there to push the "Finish" button on the scan window when the scan is done. Not very usable.
I don't mean to be a nit picker, but I do not think this "Accepted Solution" is a solution at all. Rather it is a "Work Around" for a rather serious problem. While this solution does automate the kill task function and thereby forces an entry in the NIS log, the problem still exists.
If you review the Task Scheduler history, you will see that it contains the message "Task stopping due to timeout reached" with the explanation "Task Scheduler stopped instance "{…}" of task "\Norton Internet Security - Run Full System Scan - EsieB" because it timed out." The NIS task does not run to normal completion and does not allow an method of fixing any problems found. The only way I have found of fixing the problems it finds is to run a manual Quick Scan so that NIS will re-identify the problems and allow me to fix them.
For me, this makes running automated scans a waste of time. I am using the NIS default Internet Security Options, can anyone tell me if there is a setting that will tell NIS to initiate the actions that I have specified in these options?