Update in Nod 3.0.669 is not working

Automatic Update in Nod 3.0.669 is not working

Hi all,

Nod is nagging me about "wrong username and/or password", that while iam using the same username and password for almost 2 years now.

When i perform a manual update, everything works fine.

Any ideas ?

Thanks,
Martin

 

I am having the exact same problem. I have a ticket open with ESET support but so far we have not solved the problem. I am in touch by email with ESET at least once daily and will post back if my problem is fixed. In the meantime I will also watch this thread to see if anyone else has a solution.

 

Thanks puff-m-d, iam hoping it will be fixed soon.

regards,
Martin

 

Well, i'am changing back to V 2.7

I'am getting tired of manual updating.

regards,
Martin

 

Please PM me your username so that I can check it. I for one haven't ever had a problem updating my ESS automatically.

 

Re: ESET NOD32 Antivirus v3.0.669.0 released

Couldn't it be that you have tempered with the update profile settings? It'd be of interest to check your registry values from the ESET key.

 

"Update"

Installed version 3.0.650, but the same thing happened, Nod keeps nagging me about "username and/or password", it's driving me nuts
Plus: the scheduled updates won't work either

So, at the end of the day, that is yesterday, changed back to 2.70 and the problem is solved, rather strange huh.

 

Me too,

I haven't been using NOD for a while and last week I decided to re-install and give the most recent release of 3.0.669 AV a try. No problem setting up and I "Copied and Pasted" my info into the license area and it activated fine.

The problem for me was exactly as previous posters are describing. MANUAL updates would execute without problem, but Scheduled updates would not execute without the invalid "username and/or password", or they would only work until the next restart.

I re-entered my user info so many times that i lost count, and I finally gave up and removed it.

My license has about 5 months left and I probably would have stayed with NOD this time around if it were not for this very aggravating problem with this release.

JJ

 

JJ, thanks for your post.

So it isn't just me, i hope Eset will do something about it.

I had to get back to V 2.70, which is working like a charm.

I hope more people will post a reply.

 

I thought with all of the different problems with updating that I would bump this thread. I have had this invalid username/password problem on automatic updates for the last two builds (same problem on NOD32 or ESS) 3.0.667 and 3.0.669 dated June 17, 2008 and July 7, 2008 respectively. As you can see June 17 to date is a long time to go with this problem being unresolved.

I have an open ticket with ESET support but have not had a reply back from them since July 22 (not even a status report). They were in contact with me at least every other day (excluding weekends) with several hopeful fixes but so far nothing works. It worries me that it has been right at a week now without any more response from ESET.

I hope this problem is resolved shortly as a user since version 1 days is about to jump ship after many years and with several years on his license. To me an anti-virus must has a update system in place with no flaws as with the bad guys releasing stuff several times a day, you need the same from the good guys. Having to remember to always update manually in not an acceptable option.

 

I'm also experiencing this problem with 5 of our machines. We need to manually re-import the xml files to be able to get away with this error. But with most corporate setup is, users are extremely busy to be bothered by our helpdesk to do this.

Clearing the cache manually is not a good thing to do on a corporate setup. Everything must be silently deployed without bothering users. Hope this gets resolved soon!

 

The problem is that a very large, so-called base update with more than 100,000 new signatures has been generated for v2 users which, due to a high number of v2 users, currently affects also v3 users even though not in such an extent as v2 users. We are trying to find a way how to notify the user in the case of server overloads instead of giving a message that the program is up to date, which I understand is not correct.

 

I have the same problem, and now it is November 2008, and that problem is STILL not solved.
C'mon Eset, take the finger out and DO something useful!

 

As you can see, no one has posted since July, because no one has had the problem. As you have not given me any useful information to help you at all, all I can say is make sure you have have .672

 

I'd suggest uninstalling EAV and installing v. 3.0.672. Don't change anything, just enter your username and password. If you still cannot update, there must be something wrong with your license. In such case, please PM me your username so that I can check your license.

 

Thanks.
I D/L'd the latest version 3.0.672 a few days ago and installed it OVER the 669 that I had, but I guess that was worong.
I will now UNinstall everything, try to clean the registry, delete all folders etc. and then re-install 672.
I'll post back in 2 days with hopefully better results.
If not, I will send Marcos my EAV number.

I have a ticket going, Case #189685, and all they did suggest after 9 days deliberation (!!) was to re-enter Username and Password.
I am terribly UNimpressed!

 

I uninstalled it completely, deleted any leftovers, and installed .672.
Lo and behold, it now works!

Makes me wonder why the program itself does not automatically get updated, only the virus definitions...
NOD is good, but there is still lots of room for improvement!

 

Where might one obtain the URL for this build?

 

http://www.eset.com/joomla/index.php?option=com_content&task=view&id=4971&Itemid=2