I've tried both Dantz's Retrospect Workgroup Backup Utility, and MS-Backup. I've had some scheduled backups start, and some not--and for no apparent reason. Does anyone know anything about an auto sleep mode that Windows might go into after a certain amount of idle time? I've tried adjusting various variables, yet the problem still seems intermitent.
Another weird occurance dealing w/ this problem is that: We have Norton AntiVirus scheduled to run an hour before the backup, yet when the backup doesn't run as scheduled, NAV BEGINs to run after I close out Retrospect.

Does anyone have any idea what's going on???

My usual reason for finding scheduled backups not working is either the tape has not been changed or the "life time" of the backup on the tape is not setup correctly. The other reason, is that the machine has crashed and rebooted itself or something has gone round and stopped the scheduler service, or even the power to the machine has been stopped.

Don't think you are running something that hibernates the machine.

I also presume that there is no software running that changes the time of the machine e.g. a time sync service ?

Could be a clash of some sort between retrospect and nav.

All this information can be determined from the windows event log. If no indication is given in this log, then uninstall dantz and get the system running with nav first. If you cannot get nav to work (and you are using nav correctly), then something weird is going on with the machine. Verify the machine works correctly without nav or dantz or ms-backup first. Then start adding the new components.

Thanks for the ideas Mr. C. I'll post the results in a few days.

It seems that the Windows Screen Saver Password IS the culprit. We're using Win2000 and Win2000Server. I tested my theory last night. Norton Antivirus was scheduled to run @ 1:00 AM on all computers across our network. Now, I set the screen saver password active on the server and my workstation. NAV ran as scheduled on all computers EXCEPT the server and my computer.

We need a screen saver password, as our server isn't locked up. Does anyone have any suggestions?

Oh, I did check the Event Log (as well as everything else under 'Computer Management'), and nothing about NAV not running or any other scheduled tasks being delayed.

I simply use the windows screen lock and it works fine with nav running. Do you have to have the machine logged in and screenlocked ? If not, then just log out to secure it. Nav runs as a service so does not need a screen to work properly.

Ok, it wasn't a system problem, you should run nav as a service and not a gui application.

??? How do you go about that?

I presume you are using either 2000 or 2002 server version. The normal 2002 will only work on windows workstation.

2000 will work on a server.


When it is installed, it should install a service which you can specified it should start up when windows starts up and not when you login it.

goto options -> auto-protect and there is a checkbox that indicates Start Auto Protect when windows starts. In 2002, there may be slightly different menus but same principle.

Also, ensure that Auto Protect button is enabled - you should get a little norton logo in your system tray.

Do your scheduling incudling live update (daily is recommended) and then close all windows and logout. Open the windows to check the settings have been committed.

It should work and virus reports will be available next time you log in and click on the systray icon. You will also see alerts in the event log.

also, as a final check, look in the windows services list and check that there is a NAV service running and not disabled or stopped or manual.

log out and leave the machine to it.

that should do it.

Well, yesterday morning, my computer didn't have the screen saver passworded, and NAV worked fine. My report states:

-------------------------------------------------------------
Date: 2/19/2002, Time: 1:00:06, SYSTEM on PILSNER
Virus scanning started.
-------------------------------------------------------------

...blah, blah, blah...
Yesterday afternoon, I activated the screen saver password, and didn't touch NAV. When I came in this morning (we leave our computers logged in through the time--the boss likes to copy files to and from computers across the network late @ night [workaholic]), I unlocked the screen saver password, and NAV began to scan, as though trying hurry and finish it's scheduled task.

Apparently, NAV did start, but then it waited until I unlocked the screen saver before performing the scan... the log:

-------------------------------------------------------------
Date: 2/20/2002, Time: 1:00:08, SYSTEM on PILSNER
Virus scanning started.
-------------------------------------------------------------

NAV is registered as a service (right-click on 'My Computer', select 'Manage', and then 'Services and Applications' -> 'Services', right?). NAV is started and its type is Automatic. 'NAV Auto-Protect' has the same properties, but 'NAV Alert' is started:type=manual. It looks like the Services aren't the problem. I've gotten the NAV and Dantz's Retrospect Workgroup Backup to startup at their scheduled times, but if the computer(s) have the screen saver password activated, NAV doesn't begin its scan and Retrospect doesn't begin its backup until until I unlock the screen saver.

Any other ideas Mr. Chunder?
Thanks for being patient and assisting me!!

Can you confirm that the "screen saver" you are using is just the windows one - not some funny application ?

also, which version of nav are you running ?

Also, there is no reason to leave the machine logged in, it will continue to serve while logged out unless you are running gui based apps.

You might also want to set the nav alert type from manual to an auto option. It looks like nav wants to say something to the person logged in but of course there's noone there ! What you want is it to attempt to repair file, quarrantine if fail and then carry on.

also, check all the options within nav - check also the scheduler is running. Make sure the program is closed and in the systray if you must leave the machine logged on but locked. Otherwsie, try logging the machine off.

I have some server that are never logged in and some where there are logged in but locked and I don't have a problem - I used nav 2000. I believe 2002 is at least as good. Either something else odd is going on but I suggest you try the nav support website since it is very comprehensive.