BrigitteW
June 15th, 2003, 05:17 AM
Hi all,
When I learned Nod32 v. 2 had been released I immediately purchased a licence. Great work ESET!
I've run into a problem, however, which I think may be related to an issue with task scheduler on my machine (no other symptoms), but before turning Windows upside down, I'd like to check whether it could be an issue with Nod32.
I'm running Windows 2000 SP3, the task scheduler service is set to automatic, I'm on cable so I let Nod32 update every hour (default setting). Not using any proxy, Kerio PF is set to allow access to all addresses via port 80.
Every once in a while, however, I'm getting this "System Agent Com Window" window pop up which can't be closed normally and has to be shut down through task manager. My event log then shows that the task scheduler service closed abnormally.
This happens when Nod32 is scheduled to update, but not all of the time. At first I thought it occured only when Nod32 couldn't find the server, but after changing servers the problem came back.
Even though it doesn't happen every hour, it's quite annoying. There is no option to update via commandline, is there? If there were, I could simply include it in my batchfile which updates Boclean every day.
Any ideas?
Tnx.
Brigitte
When I learned Nod32 v. 2 had been released I immediately purchased a licence. Great work ESET!
I've run into a problem, however, which I think may be related to an issue with task scheduler on my machine (no other symptoms), but before turning Windows upside down, I'd like to check whether it could be an issue with Nod32.
I'm running Windows 2000 SP3, the task scheduler service is set to automatic, I'm on cable so I let Nod32 update every hour (default setting). Not using any proxy, Kerio PF is set to allow access to all addresses via port 80.
Every once in a while, however, I'm getting this "System Agent Com Window" window pop up which can't be closed normally and has to be shut down through task manager. My event log then shows that the task scheduler service closed abnormally.
This happens when Nod32 is scheduled to update, but not all of the time. At first I thought it occured only when Nod32 couldn't find the server, but after changing servers the problem came back.
Even though it doesn't happen every hour, it's quite annoying. There is no option to update via commandline, is there? If there were, I could simply include it in my batchfile which updates Boclean every day.
Any ideas?
Tnx.
Brigitte