Automatic Update Error?

Hello Everyone

We are using NOD32 v2.0 and set for automatic update. Usually everything runs just fine but as we were scanning the Wilders update forum we noticed there is version 1.758 just out.

Just for fun we opened the Control Center to see which update was installed and we noticed it said 1.753 and upon checking the NOD32 update site we verified that version 1.758 was out. Does anyone know why the automatic update did not happen?

We use the computer several times each day, are on a cable broadband connection (with no service interruptions lately), Automatic Update is scheduled and server is set to choose automatically. In startup we have both nod32kui and NOD32kernal checked to run at startup.

Is there a way to check to see if somehow the Automatic updater file is corrupted?

 

This is precisely why I don't allow full auto update. I have NOD32 set to "offer" when there is an update. I too have cable modem and never turn off my computer and am on it about 10 hours a day most days. It takes only a couple of seconds to update usually (unless there are program upgrades) and I can continue with what I was doing if I wish while it is updating. Since it is so fast, I don't mind the interruption.

If I don't see an update offer popup window for a more than a day, I manually check and look at the logs to see how many times it has tried to update and had server failure. You might consider a similar setup so as to avoid something like this in the future. This way, if you don't see the offer window at least once in a 24 hour period. and it is not the weekend (although there are updates sometimes on the weekends also). you can suspect a problem and manually try to update and look at the logs too.

 

There is a good possibility that perhaps an aplication is in conflict with the updater on this machine. For a long time there was absolutely no problem with the Updater but since we have just added some new applications we seem to be where we are now.

We will further check to see if one of the new programs is causing this to happen.

Edit: Just checked and the 1.759 has got updated automatically! So perhaps it is related to the problem of too many programs trying to startup upon reboot on this 98SE! They perhaps have a conflict with each other.

 

check what is set to TRIGGER the update. it is of great importance.

 

AMRX - the NOD32 scheduler is set to check every day when the computer is turned on or at 0800 hrs whichever is first.

 

Maybe you could post here the latest records from your Event log which might shed a little light on it.

 

Why don't you set it to the recommended hourly check? Sometimes I get 3 updates in 24 hours. You don't want to miss any because you have it set to check only once every 24 hours.

 

Having gone back into the setup for updates we discovered that indeed the setting was just for once every 24 hours or every time computer was rebooted which is often due to constant testing of other applications.

When attempting to "copy selected" in the event log the selected lines can be highlighted but neither the right-click>Copy Selected nor the "Copy Selected" button work properly. Both give a result that shows two   and that is all.

The log showed three failed attempts a few days ago but all else looks normal. This could have been an error on the part of the service providers' connection. It said "Error connecting to server".

Lately all is well and updates happen automatically (now set to check every hour. Setting in Firewall has NOD32KRN.EXE in Trusted Applications.

If anyone has any ideas about the copying Event log problem please let us know.

Thank you

Be seeing you

 

Hi, QSection

Select copy[this is auto copied to your clipboard] Then make a new text document some where [My Documents]and then open it and select paste.

Hope this helps.
TheQuest

 

I'm glad to hear that it is working properly now and set to check hourly.

I was also a bit confused at first by how copy/paste works for the logs. TheQuest has explained it well. It would be nice if that was explained in the NOD32 help section. (I just read the 100 page KAV 5.0 manual and I am SO IMPRESSED. Best AV manual I've seen).

As for the server connection error, my logs are full of those especially for server number 3. I know Eset says don't set a specific server but in Hawaii I think that is necessary as there is only one server I can reliably use. The others ping way too high. All of them have an excessive number of hops too (except number 3 which has all the failures).

 

It does not work. We selected a few lines and highlighted them, clicked on Copy selected and pasted to Notepad and got the following -

 

Here is Notepad after the paste -

 

I don't recall what OS you have? With XP Pro, I right clicked on the log and selected "copy all" then I opened this reply box and right clicked in it and chose paste. That simple. I can also select one line of the log and copy it the same way (which I did twice at the bottom). I don't see any way though to copy say 5 lines at once. To copy more than one line but less than all, I selected copy all, then I opened notepad and selected paste (notepad was blank when I opened it ...it doesn't automatically copy to notepad). Then I highlighted 5 entries and copied and pasted here.


Time Module Event User
5/15/2004 13:27:39 PM Kernel The virus signature database has been updated successfully to version 1.761 (20040515).
5/14/2004 12:27:30 PM Kernel The virus signature database has been updated successfully to version 1.760 (20040514).
5/12/2004 23:24:17 PM Kernel The virus signature database has been updated successfully to version 1.759 (20040513).
5/12/2004 13:24:17 PM Kernel The virus signature database has been updated successfully to version 1.758 (20040513).
5/11/2004 13:37:17 PM Kernel The virus signature database has been updated successfully to version 1.757 (20040511).
5/11/2004 2:23:19 AM Kernel The virus signature database has been updated successfully to version 1.756 (20040511).
5/10/2004 17:24:35 PM Kernel The virus signature database has been updated successfully to version 1.755 (20040511).
5/9/2004 3:22:08 AM Kernel The virus signature database has been updated successfully to version 1.754 (20040509).
5/7/2004 13:20:20 PM Kernel The virus signature database has been updated successfully to version 1.753 (20040507).
5/6/2004 12:20:01 PM Kernel The virus signature database has been updated successfully to version 1.752 (20040506).
5/5/2004 20:20:00 PM Kernel The virus signature database has been updated successfully to version 1.751 (20040505).
5/5/2004 4:20:14 AM Update Error connecting to server u3.eset.com.
5/5/2004 3:20:14 AM Update Error connecting to server u3.eset.com.
5/5/2004 2:19:14 AM Update Error connecting to server u3.eset.com.
5/5/2004 1:19:15 AM Update Error connecting to server u3.eset.com.
5/5/2004 0:19:15 AM Update Error connecting to server u3.eset.com.
5/4/2004 19:19:15 PM Update Error connecting to server u3.eset.com.
5/4/2004 18:19:15 PM Update Error connecting to server u3.eset.com.
5/4/2004 17:19:15 PM Update Error connecting to server u3.eset.com.
5/4/2004 16:19:02 PM Kernel The virus signature database has been updated successfully to version 1.750 (20040505).
5/4/2004 12:19:15 PM Update Error connecting to server u3.eset.com.
5/4/2004 11:19:15 AM Update Error connecting to server u3.eset.com.
5/4/2004 10:19:15 AM Update Error connecting to server u3.eset.com.
5/4/2004 5:19:15 AM Update Error connecting to server u3.eset.com.
5/4/2004 4:19:15 AM Update Error connecting to server u3.eset.com.
5/4/2004 3:19:15 AM Update Error connecting to server u3.eset.com.
5/4/2004 1:07:55 AM NOD32 An infiltration has been detected. See the on-demand scanner Log for details. MELE\Marilyn
5/4/2004 0:52:03 AM NOD32 An infiltration has been detected. See the on-demand scanner Log for details. MELE\Marilyn
5/3/2004 23:15:58 PM Update Error connecting to server u3.eset.com.
5/3/2004 22:19:15 PM Update Error connecting to server u3.eset.com.
5/3/2004 21:19:15 PM Update Error connecting to server u3.eset.com.
5/3/2004 20:19:15 PM Update Error connecting to server u3.eset.com.
5/3/2004 15:19:15 PM Update Error connecting to server u3.eset.com.
5/3/2004 14:19:15 PM Update Error connecting to server u3.eset.com.
5/3/2004 13:21:32 PM Kernel The virus signature database has been updated successfully to version 1.749 (20040503).
5/3/2004 13:19:15 PM Update Error connecting to server u3.eset.com.
5/3/2004 12:19:01 PM Kernel The virus signature database has been updated successfully to version 1.748 (20040503).
5/3/2004 8:19:15 AM Update Error connecting to server u3.eset.com.
5/3/2004 7:19:15 AM Update Error connecting to server u3.eset.com.
5/3/2004 6:18:16 AM Update Error connecting to server u3.eset.com.
5/3/2004 5:18:16 AM Update Error connecting to server u3.eset.com.
5/2/2004 23:18:16 PM Update Error connecting to server u3.eset.com.
5/2/2004 22:18:16 PM Update Error connecting to server u3.eset.com.
5/2/2004 21:18:16 PM Update Error connecting to server u3.eset.com.
5/2/2004 16:18:16 PM Update Error connecting to server u3.eset.com.
5/2/2004 15:18:16 PM Update Error connecting to server u3.eset.com.
5/2/2004 14:18:16 PM Update Error connecting to server u3.eset.com.
5/2/2004 13:18:04 PM Kernel The virus signature database has been updated successfully to version 1.747 (20040502).
5/2/2004 9:18:16 AM Update Error connecting to server u3.eset.com.
5/2/2004 8:18:16 AM Update Error connecting to server u3.eset.com.
5/2/2004 7:18:16 AM Update Error connecting to server u3.eset.com.
5/2/2004 2:18:16 AM Update Error connecting to server u3.eset.com.
5/2/2004 0:18:16 AM Update Error connecting to server u3.eset.com.
5/1/2004 21:54:18 PM Update Error connecting to server u3.eset.com.
5/1/2004 19:18:16 PM Update Error connecting to server u3.eset.com.
5/1/2004 18:18:16 PM Update Error connecting to server u3.eset.com.
5/1/2004 17:18:16 PM Update Error connecting to server u3.eset.com.
5/1/2004 12:53:49 PM Kernel The virus signature database has been updated successfully to version 1.746 (20040501).
5/1/2004 2:17:02 AM Kernel The virus signature database has been updated successfully to version 1.745 (20040501).
4/30/2004 13:17:04 PM Kernel The virus signature database has been updated successfully to version 1.744 (20040430).
4/29/2004 5:15:05 AM Kernel The virus signature database has been updated successfully to version 1.743 (20040429).
4/28/2004 13:13:17 PM Kernel The virus signature database has been updated successfully to version 1.742 (2004042.
4/27/2004 13:14:14 PM Kernel The virus signature database has been updated successfully to version 1.740 (20040427).
4/26/2004 11:14:13 AM Kernel The virus signature database has been updated successfully to version 1.737 (20040426).
4/25/2004 13:10:09 PM Kernel The virus signature database has been updated successfully to version 1.735 (20040426).
4/24/2004 14:09:22 PM Kernel The virus signature database has been updated successfully to version 1.734 (20040424).
4/22/2004 13:08:23 PM Kernel The virus signature database has been updated successfully to version 1.732 (20040422).
4/21/2004 20:25:16 PM Update Update attempt failed (Server connection failure)
4/21/2004 20:25:15 PM Update Error connecting to server www.nod32.com.
4/21/2004 20:25:12 PM Update Error connecting to server u2.eset.com.
4/21/2004 20:25:09 PM Update Error connecting to server u1.eset.com.
4/21/2004 20:25:07 PM Update Error connecting to server u4.eset.com.
4/21/2004 20:25:06 PM Update Error connecting to server u3.eset.com.
4/21/2004 12:21:35 PM Kernel The virus signature database has been updated successfully to version 1.730 (20040421).
4/20/2004 22:20:53 PM Kernel The virus signature database has been updated successfully to version 1.728 (20040421).
4/20/2004 14:20:54 PM Kernel The virus signature database has been updated successfully to version 1.727 (20040420).
4/19/2004 22:19:49 PM Kernel The virus signature database has been updated successfully to version 1.725 (20040420).
4/19/2004 13:19:45 PM Kernel The virus signature database has been updated successfully to version 1.724 (20040419).
4/19/2004 1:18:45 AM Kernel The virus signature database has been updated successfully to version 1.722 (20040419).
4/16/2004 13:17:46 PM Kernel The virus signature database has been updated successfully to version 1.721 (20040416).
4/16/2004 0:21:03 AM Kernel The virus signature database has been updated successfully to version 1.720 (20040416).
4/15/2004 23:16:51 PM Kernel The virus signature database has been updated successfully to version 1.719 (20040416).

Time Module Event User
5/2/2004 21:18:16 PM Update Error connecting to server u3.eset.com.
Time Module Event User
5/1/2004 17:18:16 PM Update Error connecting to server u3.eset.com.

4/19/2004 13:19:45 PM Kernel The virus signature database has been updated successfully to version 1.724 (20040419).
4/19/2004 1:18:45 AM Kernel The virus signature database has been updated successfully to version 1.722 (20040419).
4/16/2004 13:17:46 PM Kernel The virus signature database has been updated successfully to version 1.721 (20040416).
4/16/2004 0:21:03 AM Kernel The virus signature database has been updated successfully to version 1.720 (20040416).
4/15/2004 23:16:51 PM Kernel The virus signature database has been updated successfully t

 

98SE here. We have absolutely no other problems copying, cutting or pasting anything else. We even tried just one line and "copy all" and opened Notepad, Editpad, Wordpad, and Word with all the same results of those two little boxes!

It is not a big thing but now we would like to have anyone else using 98SE and NOD32 try this.

Anyone?

 

You are correct! On myW98SE box, I have exactly the same problem as you. This is what I get if I try to copy one line and paste in notepad, wordpad or Word97! Wow, this simple function is disabled in all applications. This is what I get if try to paste in any of those applications or here in this reply box.
Edited to say that is what the clipboard viewer is showing also. (Those odd boxes).

Edited: those little boxes don't show when I view this post from my XP box..but they do from the W98SE one. That is strange.

 

 

Am I impressed! I got a response from Eset in less than one hour! Mark said that this bug is fixed in the new beta that is due out anytime now. You should email Eset though so support can help you with your update problem. Mark thought I was the one with the update problem. I explained it was you.

Either I just lucked out...or Eset did hire some new employees...hope it is the latter.