PDA

View Full Version : ESS Beta2 Error on Update-0x3fff


KaneComputing
August 28th, 2007, 08:08 PM
I recently installed Beta2 and it had been updating normally on my Windows XP machine. Until today. Most recent update is 2488 (20070828). Now it won't update and shows the error message "Undocumented Severe Error 0x3fff".

It appears to happen just after downloading a particular update file (see screen capture).

Anyone else seeing this?

KaneComputing
August 30th, 2007, 06:28 AM
This error fixed itself. I restarted the computer and while I was away, it updated itself normally.

So never mind, ESS Beta2 continues to function normally.

Ven
September 4th, 2007, 02:44 PM
I encountered the same problem.
I updated manually the virusdefinitions. First time it failed. The second time i was succesfull.

So the problem fixed itself (I think, because it functions normally now)

osip
September 5th, 2007, 04:48 PM
I have exactly the same with signs 2505 and manual update...still there after reboot...

Marcos
September 5th, 2007, 05:15 PM
-{ Quote: "I have exactly the same with signs 2505 and manual update...still there after reboot..." }-

What about clicking on the "Update virus sd" link several times? Does it make a difference?

osip
September 5th, 2007, 05:49 PM
-{ Quote: "What about clicking on the "Update virus sd" link several times? Does it make a difference?" }-

No, it does´nt...upd.ver+nup1,nup2 and then the error...What´s the latest signs?

osip
September 5th, 2007, 06:40 PM
restored snapshot to 9.04 with signs 2502...The same picture...It seems as the loading of sd fails in the final stage 75%...
--------------
added: went back to sd 2501...the same! Must be some bug...managed to get update to sd2505 earlier,now from 2501,2502 not able to do that...

VIPOR1
September 6th, 2007, 12:05 AM
I am also having this problem.
Last successful update was to 2505.

osip
September 6th, 2007, 03:19 AM
Made a repair install...still the same but this time with the popup " base file missing "...Is this fixable, if so how?

------
added: seems as the update goes through but is´nt registered within the prog...

crummock
September 6th, 2007, 04:00 AM
I've now got this on 2 machines on separate networks. Also now started getting another warning: 06/09/2007 08:50:19 Antispam: Error writing antispam counters. This last error repeats for each email that Outlook sees. The lack of virus update MUST be fixed NOW or ESS cannot continue to be used.

crummock
September 6th, 2007, 05:39 AM
Seems to be ESS only. The AV only Beta seems to update OK so far.

Come on ESET this is important, let's have a response.

osip
September 6th, 2007, 05:53 AM
The fact is that we are several with exact same problem...I´m sure we will have an answer when this has been sorted out...

crummock
September 6th, 2007, 05:57 AM
Would be nice for ESET to keep people informed though. After all we are helping them perfect teh product and they act as though they are doing us a favour.

MAybe time to look elsewhere if their attitude is so poor.

backspin
September 6th, 2007, 06:48 AM
I had the same problem (signature 2505), tried several time to update manually including reboot but allways the same failure.
So I uninstalled and manually deleted the folder including the updatefiles/logs (4 windows vista -> c:\programmdata\eset\eset smart security). Then made a new install ESS Beta2 and now I could update to signature 2508. But I think w'll see if the next update is working accurate...

Update
...while updating from 2508 to 2509 got a "General Compiler Error" and so I reinstalled 2nd time today. No need to say that I could update now to 2509...I'll keep an eye on it.

Update
...updated successfully from 2509 to 2510

I hope this could help the people from eset to fix this problem.

regards
backspin

Marcos
September 6th, 2007, 08:47 AM
If possible, please compress the content of the "C:\Documents and Settings\All Users\Application Data\Eset\Eset Smart Security\Updfiles" folder, all current modules from the Eset folder (em00*.dat) as well as export the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Eset\Eset Security\CurrentVersion. When done, upload it to an ftp server or PM me for anonymous access to our ftp.

crummock
September 6th, 2007, 10:27 AM
I have all the files ready and have PM's Marcos and am awaiting a reply.

osip
September 6th, 2007, 11:53 AM
The same here...

crummock
September 6th, 2007, 12:52 PM
Files uploaded as requested.

Hopefully we'll get a prompt response as working with outdated definitions is not good.

BTW updates still work on my third machine which is XP. Failing machines are Vista but were OK until 4th/5th September.

osip
September 6th, 2007, 01:37 PM
Uploaded here also...Failing system XP Pro sp2...1st problem since 1a in my case...

crummock
September 6th, 2007, 05:00 PM
Well I got one of my Vista machines using latest definition by copying files fom a working XP machine and rebooting but the failure still comes back when you click to run an update.

2 errors are in the logs:

06/09/2007 21:56:41 Update Updater: retval = 0x1102, failures: 2 NT AUTHORITY\SYSTEM

06/09/2007 21:56:41 Update Base file missing. NT AUTHORITY\SYSTEM

BarneyBadass
September 6th, 2007, 05:35 PM
What's really weird is that ESS finally came back with a "Green" symbol.. indicating all was / is well..

After a couple of re-boots; now I have the "RED" symbol indicating things aren't good any more...

I can't quite sort out why it changes to green then red then green then red..

Does ESS celebrate Christmas and it thinks it's a red / green diode that changes color for the season? ;D

crummock
September 6th, 2007, 05:45 PM
Another interesting development in my testing of trying to understand this:

If I set my XP machine, which updates correctly from ESET, as a mirror and then point the troublesome Vista machines at the XP mirror instead of at ESET it then updates perfectly.

Looks like some issue at ESET end ?

SweX
September 6th, 2007, 08:12 PM
Hi.

I got the same update error ( Undocumented severe error (0x3fff)

Last successful update: 2007-09-05

Version of Virus signature database: 2505 (20070904)

Regards SweX.

BarneyBadass
September 6th, 2007, 08:15 PM
Perhaps someone at ESET can sort this out... Evidently I don't see what's causing the problem.


9/6/2007 3:42:56 PM Kernel Error initializing file submission system.
9/6/2007 3:42:53 PM Kernel Virus scanner initialization failed. Most of Eset Smart Security modules will not function properly.
9/6/2007 3:39:22 PM Kernel Error initializing file submission system.
9/6/2007 3:39:22 PM Antispam: Error loading updated data files.
9/6/2007 3:39:19 PM Kernel Virus scanner initialization failed. Most of Eset Smart Security modules will not function properly.
9/6/2007 12:57:33 PM Kernel Virus signature database successfully updated to version 2510 (20070906). %BUILD="1550"%VERSIONID="2510"%DATE="131533062"%TIME="0"%VERSION="2510 (20070906)"
9/6/2007 10:55:59 AM Kernel Error initializing file submission system.
9/6/2007 10:55:56 AM Kernel Virus scanner initialization failed. Most of Eset Smart Security modules will not function properly.
9/6/2007 10:47:48 AM Kernel Virus signature database successfully updated to version 2509 (20070906). %BUILD="1548"%VERSIONID="2509"%DATE="131533062"%TIME="0"%VERSION="2509 (20070906)"
9/6/2007 9:47:14 AM Kernel Error initializing file submission system.
9/6/2007 9:47:11 AM Kernel Virus scanner initialization failed. Most of Eset Smart Security modules will not function properly.

evilharp
September 6th, 2007, 09:40 PM
Same error here (Beta 2 - Vista x64)

I'm on dial up, so I have the pleasure of watching the files download.

Today I get:
update.ver - ok
em002_32_n6.nup - ok file 1/3
em003_32_n1.nup - ok file 2/3
unknown (status bar, no details)- fail 3/3 ????

Events Log indicates

06/09/2007 9:14:06 PM Update An error occurred while downloading update files. NT AUTHORITY\SYSTEM

Is there a bad file on the server - or - is the update.ver corrupt/pointing to something that isn't there?

dansx6
September 7th, 2007, 12:13 AM
Hi,
I just found this site. Same error here. I am using Vista ult. x64 and Beta 2. It stopped updating 9/4 as best I can tell. I also ran a repair install and the error message changed from "Undocumented severe error (0x3fff)" to the "Base File Missing" error. I wasn't able to get it to update properly so I did an uninstall/reinstall. When I finished I couldn't get the update to work at all. The one thing I didn't do was clean out the registry for the beta keys.

crummock
September 7th, 2007, 02:08 AM
Just an update....

on one of my problem Vista machines I copied the C:\ProgramData\Eset\Eset SmartSecurity\Updfiles folder and all the C:\Program Files\Eset\Eset Smart Security\em*.dat files from a working XP machine and rebooted.

This got me a working version of ESS that was at definition release 2510. That was last night.

This morning the machine has correctly updated to 2511 with no problem.

Maybe the problem is corruption in one of these files ?

I';ve still got one non-updated Vista machine that I'm not applying this fix to until I see if ESET can fix it from there side or need more tests to help them fix it.

osip
September 7th, 2007, 02:41 AM
I even went back to sd2497 and again the same...Because I can go back in time to previous databases, i.e from 2505-to 2497 and then not able to update back to 2505 I have the impression that this has to be on ESET´s end...In the meantime, until this is fixed, I uninstalled ESS in one snapshot and installed Avira premium suite with a 3 month trial key...When the issue is cleared I will for sure return...

deputy963
September 7th, 2007, 09:36 AM
The problem appears to have been corrected.

I manually initiated an update, which resulted in a 7mb download. Nothing changed, so I rebooted. Problem fixed!

The download did not correct the splash screen issue, just the update issue.

OS: Vista Business 32bit

MenosOcho
September 7th, 2007, 09:55 AM
Hi,

I've got the same problem:
Undocumented severe error (0x3fff)
Last successful update: 2007-09-04
Version of Virus signature database: 2505 (20070904)

I rebooted and i tried to do the update manually, nothing fix it.

Regards,
Martin
Vista Ultimate x64

trial and error
September 7th, 2007, 10:11 AM
First off I'm a content three year user of NOD32. I run XPx64 and it was nice to find a beta that would install.
Any rant here is meant to be constructive for the people at Eset.

I think this is a firewall issue.

The "Undocumented Severe Error 0x3fff" with ESS b2 on my XPx64 rig is because the firewall will not allow me to connect to get the updates.
If you look in your firewall logs you will see this too.

The firewall doesn't allow you to easily right click and edit allow/deny, in/out/both like the pre-Sunbelt KPF did. (That is a suggestion)

Even when I made specific rules for each prompt for both ways it would not allow the connection. Interactive mode isn't up to snuff anyway. When I switched out of interactive to "regular" firewall mode it won't allow it either.

Turning the firewall off doesn't help at all.

I uninstalled it and cleared the registry and prefetch of Eset, egui and ekrn. Then reinstalled with a legitimate user name and password for my NOD32. Four different times with different initial configurations.

After September 4th it was impossible to update the virus definitions.

I'll watch out for the next release and try again then maybe.

osip
September 7th, 2007, 10:41 AM
Yes, in interactive mode...but, if the same occurs in the regular mode it means that the firewall has a problem with it´s own server...

trial and error
September 7th, 2007, 12:06 PM
Not only that, but it started after the update I received on Sept 4th. Then regardless of how I configured or disabled the firewall I get this error. I hope Eset can figure this out. First heard of ESS a long time ago. When it's finally ready for prime time I will buy it, despite the candy _ss psychedelic colors.

stueycaster
September 7th, 2007, 12:47 PM
Want a good laugh over this. I tried to do device driver updates on my motherboard. The garbage that I got from MSI (my last MSI hardware) screwed up my system so bad that I ended up having to do a repair installation on my operating system just to get it to boot. After I finally got my system back the last thing that was still giving me a lot of trouble was the ESS update issue. I thought it had to be caused by the driver update fiasco. I've been sitting in front of this #$%^^&* computer since last night trying to get it to work right. Then I finally decided to try checking it out on this forum. It wasn't my computer, it was ESET. Boy do I feel stupid.

Marcos
September 7th, 2007, 12:51 PM
Those who have Windows XP/Vista 64-bit can download a fix from here (http://eset.zftp.com/support/ess/hot_fix_update.exe). You may need to restart the computer for the fix to take effect.

fosius
September 7th, 2007, 12:54 PM
What about XP 32-bit?:)

crummock
September 7th, 2007, 01:14 PM
-{ Quote: "Those who have Windows XP/Vista 64-bit can download a fix from here (http://eset.zftp.com/support/ess/hot_fix_update.exe). You may need to restart the computer for the fix to take effect." }-

Hi,

I assume you mean to run the hot_fix in the C:\Program Files\Eset\Eset Smart Security directory as that is where the files are that need replacing ?

Worth mentioning that if you have Vista with UAC enable it is neccessary to 'run as administrator' for it to replace the faulty files.

Having said all that I can confirm that it has fixed my Vista 64 machine without reboot.

ASpace
September 7th, 2007, 01:35 PM
I am unable to use ESS/EA betas but I would like to know does this update problem is valid for ESET Smart Security only or it affects Eset Antivirus , too .

The fix should be valid for ESS only because of the directory it is in:
-{ Quote: "http:// ... support/ess/hot...." }-

Mercury_22
September 7th, 2007, 03:40 PM
-{ Quote: "I am unable to use ESS/EA betas but I would like to know does this update problem is valid for ESET Smart Security only or it affects Eset Antivirus , too .

The fix should be valid for ESS only because of the directory it is in:" }-

I can confirm that it affects Eset Antivirus too ! but the fix has solved the error (on vista x64)

Mercury_22
September 7th, 2007, 03:43 PM
-{ Quote: "Hi,

I assume you mean to run the hot_fix in the C:\Program Files\Eset\Eset Smart Security directory as that is where the files are that need replacing ?

Worth mentioning that if you have Vista with UAC enable it is neccessary to 'run as administrator' for it to replace the faulty files.

Having said all that I can confirm that it has fixed my Vista 64 machine without reboot." }-

You DON'T have to run the fix in C:\Program Files\Eset\Eset Smart Security directory !!! 8)

crummock
September 7th, 2007, 03:45 PM
-{ Quote: "You DON'T have to run the fix in C:\Program Files\Eset\Eset Smart Security directory !!! 8)" }-

I did for it to work.,

ASpace
September 7th, 2007, 04:21 PM
-{ Quote: "I can confirm that it affects Eset Antivirus too ! but the fix has solved the error (on vista x64)" }-

Thanks! :thumb:

Mercury_22
September 7th, 2007, 05:07 PM
-{ Quote: "I did for it to work.," }-
i run it from drive d: and it work so...:thumb:

stueycaster
September 7th, 2007, 05:36 PM
The Hotfix didn't work for me. :'( I tried everything I could think of. I'm on XP x64. My system may still be messed up from my recent driver update problems. It seems to be working good otherwise though.

MenosOcho
September 7th, 2007, 06:14 PM
-{ Quote: "Those who have Windows XP/Vista 64-bit can download a fix from here (http://eset.zftp.com/support/ess/hot_fix_update.exe). You may need to restart the computer for the fix to take effect." }-


Thank you!

It's working now ;D

osip
September 7th, 2007, 06:32 PM
I can imagine a h*ll of activity in eset´s cellars...An almost full working beta with a sudden major issue...Waitin´ for the solution for 32-bit which I´m sure will be seen in soon...Don´t give up guy´s...I will for sure return...

VIPOR1
September 7th, 2007, 06:47 PM
Thank you, the fix worked for me.

dansx6
September 7th, 2007, 07:28 PM
The fix didn't work here either (I am using the AV beta). I tried everything but I am still getting the base file error message. Any other ideas?

Vista Ultimate x64

stueycaster
September 7th, 2007, 08:05 PM
I put my ESET Username and Password in and it fixed it :D :thumb: . I hope it stays fixed. If it doesn't you will be the first to know.

trial and error
September 7th, 2007, 09:55 PM
;D THANK YOU Marcos!
I did not put my own username in and let the beta do it's thing. I did have to hit the update link three times to jump start it, but it updates. Funny -- the interactive allow/deny window is popping up for me now, and not just to recognize the "new network" . Opening my mail and two program updaters I had to click for each to proceed. That's the way I expect it to act.

stueycaster
September 7th, 2007, 10:03 PM
After it did an automatic update I'm back to the Base File Missing: Error. Now the logo in my system tray is orange.

BarneyBadass
September 7th, 2007, 10:11 PM
I've noticed that if the system crashes and comes back up ... ESS is frequently "red / orange" for some period of time.. sometimes a long time sometimes not so long..

can anyone explain this behavior?

ASpace
September 8th, 2007, 04:05 AM
-{ Quote: "After it did an automatic update I'm back to the Base File Missing: Error. Now the logo in my system tray is orange." }-

Have you tried reinstalling ESS ? Clean install , clean update ?

-{ Quote: "1. Download fresh new ESS from http://www.eset.eu/beta
1. Uninstall your current version from Control Panel -> Add/Remove programs
2. Reboot the computer when prompted
3. Delete manually these three folders

- C:\Documents and Settings\All users\Application data\Eset
- C:\Documents and Settings\your user\Application data\Eset
- C:\Documents and Settings\your user\Local Settings\Application data\Eset

4. Install again ESS beta . Use Typical install and keep essbeta for username/password" }-

Tantawi
September 8th, 2007, 05:56 AM
Same here, AntiVirus Beta 2, Vista x64, Base file missing error, the provided fix didn't work.

Marcos
September 8th, 2007, 08:22 AM
Please try deleting the content of the "C:\Documents and Settings\All Users\Application Data\Eset\Eset Smart Security\Updfiles" folder and updating ESS manually. Should the problem persist, carry on by following the instructions provided here:
http://www.wilderssecurity.com/showpost.php?p=1072174&postcount=15. Also enclose detailed information about your OS, e.g. Windows XP SP2 32-bit

stueycaster
September 8th, 2007, 09:16 AM
It seems to be fixed. :D :thumb: I didn't realize that there was an ESET folder in Documents and Settings/All Users/~ besides the one in ~/my account. After uninstalling ESS I didn't delete the folder in All Users. I guess that's why I couldn't fix it. After deleting both folders, reinstalling and applying the Hot Fix it is working right. Thanks Guys for helping me out. You guys who help people out in forums are awesome. :thumb:

Tantawi
September 8th, 2007, 09:24 AM
-{ Quote: "Please try deleting the content of the "C:\Documents and Settings\All Users\Application Data\Eset\Eset Smart Security\Updfiles" folder and updating ESS manually. Should the problem persist, carry on by following the instructions provided here:
http://www.wilderssecurity.com/showpost.php?p=1072174&postcount=15. Also enclose detailed information about your OS, e.g. Windows XP SP2 32-bit" }-

Thank you but the problem is that I can't access "C:\Document and Settings". it gave me access denied error!

I'm an administrator on Windows Vista x64 with UAC disabled and auto elevation enabled.

UPDATE: Fixed it, the folder is located here instead: "C:\ProgramData\Eset\ESET NOD32 Antivirus\Updfiles", uninstalling, deleting, reinstalling, applying the fix, rebooting, have fixed the problem finally :)

deimos
September 8th, 2007, 10:52 AM
-{ Quote: "Please try deleting the content of the "C:\Documents and Settings\All Users\Application Data\Eset\Eset Smart Security\Updfiles" folder and updating ESS manually. Should the problem persist, carry on by following the instructions provided here:
http://www.wilderssecurity.com/showpost.php?p=1072174&postcount=15. Also enclose detailed information about your OS, e.g. Windows XP SP2 32-bit" }-

Hm, no fix for me. XP SP2 32bit. Folder cannot be deleted as it is locked by ESS...

deimos
September 8th, 2007, 11:41 AM
-{ Quote: "Hm, no fix for me. XP SP2 32bit. Folder cannot be deleted as it is locked by ESS..." }-

Unistalled, removed update folder, installed again, update ok :thumb:

dansx6
September 8th, 2007, 01:42 PM
I have tried everything suggested here and still no luck. It looks like it is back to the stable version for now. Thanks for the suggestions.

sugfry
September 8th, 2007, 02:28 PM
I have tried a clean install & have now gone from a (0x3fff) error to a base file error now. I tried all the fixes mentioned above but still no luck. I hope this is resolved soon cause I like the program......

After the clean install my virus database is 2478 this is worrying cause before I had my first error my VD was 2505 so now I don't have the same protection......

Sk_illed
September 8th, 2007, 03:16 PM
Mid post I downloaded the hotfix, and now it works! (vista64 ess)


I had previously gotten the 3ff error after:

uninstalled
deleting:
C:\Users\me\AppData\Roaming\Eset
C:\Users\me\AppData\Local\Eset
C:\ProgramData\Eset
C:\Program Files\Eset (no eset folder in Prog Files x86)
Deleted all regkeys in hkcu and hklm
reboot / reinstall

harrievaan
September 8th, 2007, 07:01 PM
Had the same problem of not updating. Followed Marcos tip of removing the contents of the update folder. The manual update seemed to work and it updated some files. But still the "virus signature database could not be updated" is still there (0x3fff).

I run XP sp2 32 bit

richardschwarz_oz
September 8th, 2007, 07:14 PM
I also followed Marcos' idea of deleting the c:\documents and settings\all users\application data\eset\updfiles directory and then doing a manual update. It didn't work - after any of the 6 or so attempts (I really like making sure that I've done something right before commenting).

So, I re-downloaded the beta, uninstalled ESET, deleted every ESET folder I could find (mainly just c:\documents and settings\all users\application data\eset, restarted, re-installed and presto! It's working at the moment... We'll see what happens in the coming days. ;D

Hammy
September 8th, 2007, 07:17 PM
I too am having this error I have tried uninstalling and reinstalling also tried the tip of Marcos the removal of the contents of the update folder but still getting the "0x3fff" error.

Hammy

tosbsas
September 8th, 2007, 11:25 PM
had it too, I deleted the allusers\updatefiles folder (its contents) and no change, I restarted and it did the update to 2515 - now all seems fine

Ruben

@Marcos
Thanks for helping so much - do I need to copy the files from the allusers\update folder back there??

sugfry
September 9th, 2007, 03:46 AM
I'm using vista ultimate 32bit & can't find the program data folder i have searched my c: but can't seem to locate it anywhere. Has anybody got any ideas on this one?????

FMKaiba
September 9th, 2007, 07:05 PM
PM system seems to be down, so i through all the asked for information here:
http://www.kipi-fan.com/Nod32%20Files.zip

if an ESET programmer or administrator wants to take a look at it. I am still getting the 0x3fff error

NOTE: i only have the Anti-virus beta, not the security suite one, and the hotfix.exe isn't doing anything (i double click it, it shows a cmd window for a half second and closes)

EDIT: Its working now, (Method of fixing)
Uninstalled, deleted:
C:\Program files\ESET\
C:\Documents and Settings\All Users\Application Data\Eset
restarted
installed Nod32 Beta2
Right after that before doing anything ran the hotfix from: C:\Program Files\Eset\ESET NOD32 Antivirus
Manual Updated

dansx6
September 9th, 2007, 10:49 PM
-{ Quote: "
NOTE: i only have the Anti-virus beta, not the security suite one, and the hotfix.exe isn't doing anything (i double click it, it shows a cmd window for a half second and closes)

EDIT: Its working now, (Method of fixing)
Uninstalled, deleted:
C:\Program files\ESET\
C:\Documents and Settings\All Users\Application Data\Eset
restarted
installed Nod32 Beta2
Right after that before doing anything ran the hotfix from: C:\Program Files\Eset\ESET NOD32 Antivirus
Manual Updated" }-

I am up and running the AV beta also, following this procedure combined with
deleting the ESET entries in the registry under HKCU and HKLM. I am running Vista x64 Ultimate and I had to run the hotfix as administrator for it to work (as previously mentioned in this thread).

Edit: Auto update today (2519) without any problems

osip
September 10th, 2007, 03:54 PM
ATLAST BACK IN BUSINESS!

Uninstalled,deleted all eset folders in doc&settings,cleaned all ESET in registry, reinstalled,rebooted:got an eror message that my licence expired and that a new v has to be installed...Pushed the update button nevertheless and got an update file on 7121Kb,rebooted....AND,went from 2502 to 2519...Seems as the problem is fixed...(in my case that is...)

Clweb
September 10th, 2007, 06:35 PM
Now in addition to the error message for updates I have the antivirus protection disabled (red in systray).
ESS beta 2 running in Vista 32 bits.
???

scegg
September 10th, 2007, 07:57 PM
-{ Quote: "ATLAST BACK IN BUSINESS!

Uninstalled,deleted all eset folders in doc&settings,cleaned all ESET in registry, reinstalled,rebooted:got an eror message that my licence expired and that a new v has to be installed...Pushed the update button nevertheless and got an update file on 7121Kb,rebooted....AND,went from 2502 to 2519...Seems as the problem is fixed...(in my case that is...)" }-

I done this before but: due to bad network connection, the update cannot be downloaded at once. After many times retries, error "base file missing" again.

Clweb
September 11th, 2007, 05:01 AM
Uninstall, delete all remaining files and registry entries. Reinstall, it says license expired. Try to update: a 7MB update is downloaded, but it says base file missing.
I repair and the same game again. It ends up with update failed, it shows license expired. All on Vista 32.
Was a nice program, but for me the beta test ends, at least until release of a Beta3 or RC.
PS:
I retried an install after deleting ALL files (I forgot some before). It seems happy with update (says after that no update necessary), but license expired remains, and that means no more protection: scanning, scans nothing and I think firewall does not work either.

Marcos
September 11th, 2007, 05:48 AM
-{ Quote: "Uninstall, delete all remaining files and registry entries. Reinstall, it says license expired. Try to update: a 7MB update is downloaded, but it says base file missing.
I repair and the same game again. It ends up with update failed, it shows license expired. All on Vista 32.
Was a nice program, but for me the beta test ends, at least until release of a Beta3 or RC.
PS:
I retried an install after deleting ALL files (I forgot some before). It seems happy with update (says after that no update necessary), but license expired remains, and that means no more protection: scanning, scans nothing and I think firewall does not work either." }-

If the system date is actually correct, could you post a screenshot of the error here?

PnP
September 11th, 2007, 09:08 AM
me too cannot update antivirus.. windows vista ultimate x64... thanks

P.S. resolver with hotfix by marcos...

Clweb
September 11th, 2007, 09:58 AM
-{ Quote: "If the system date is actually correct, could you post a screenshot of the error here?" }-
System date is OK. These screenshots are after install (new install to make screenshots).
Other screenshots (after update) available.

Hammy
September 11th, 2007, 04:50 PM
I am now running Virus data base 2522 thanks to all of you for your helpful hints I forund that it was an extra re-boot after deleting all my Eset files ie:
-{ Quote: "1. Download fresh new ESS from http://www.eset.eu/beta
1. Uninstall your current version from Control Panel -> Add/Remove programs
2. Reboot the computer when prompted
3. Delete manually these three folders

- C:\Documents and Settings\All users\Application data\Eset
- C:\Documents and Settings\your user\Application data\Eset
- C:\Documents and Settings\your user\Local Settings\Application data\Eset
" }-
4, Then Re-Boot
5. Install beta (keeping essbeta for username/password)

Hammy

Clweb
September 12th, 2007, 04:16 AM
Strange, strange...
Yesterday after making the screenshots, I rebooted and worked with XP.
Today I reboot on Vista and the Eset icon in the systray is green. And an upgrade of database 2523 from today worked.
Self healing software ? :)

dansx6
September 12th, 2007, 10:01 AM
Another interesting twist. My AV Beta has been updating properly for the last 2 days (after I was able to get past "base file missing" error). Today I updated to 2524 which looks like it is the latest update. Auto update just ran again and I am getting an error that says "Virus signature database update failed -Incompatible modules".

EDIT: Auto update just ran successfully (2525)

EDIT 2: I am now getting the same error message again..."Virus signature database update failed -Incompatible modules".

Zonendr
September 13th, 2007, 06:20 AM
I solved this problem by going to the User name area and re-typing the password: essbeta. It solved this problem for me. I am currently on virus signature 2527.

dansx6
September 13th, 2007, 08:03 AM
I seem to be updating but in between the updates I get the error message. I am using my regular username and password. I have 2527 as my latest update.

Degine
September 13th, 2007, 01:00 PM
-{ Quote: "Another interesting twist. My AV Beta has been updating properly for the last 2 days (after I was able to get past "base file missing" error). Today I updated to 2524 which looks like it is the latest update. Auto update just ran again and I am getting an error that says "Virus signature database update failed -Incompatible modules".

EDIT: Auto update just ran successfully (2525)

EDIT 2: I am now getting the same error message again..."Virus signature database update failed -Incompatible modules"." }-

I have the same problem, check out this topic:

http://www.wilderssecurity.com/showthread.php?t=185255

which is more specific about the incompatible module update error. (no solution yet though)

tosbsas
September 14th, 2007, 02:53 PM
and the bastard is back - xphome sp2

Ruben

Update:
And again, deleting the folder in all users /updfiles/ and restart - with the lag (:-(( worked

Ruben