Windows 7 general compiler error again

Any solution to the compiler error? I have a couple of Windows XP computers that are getting the error even after upgrading to 4.2.67.10.

I have tried everything mentioned (remove, install, clear update cache, etc.) and no go.

 

there is a fresh Update module: 1032 (20101025) - think it is still beta (pre-release), but since then haven't had this trouble anymore on 7x64

 

Well I hate to report, but I got another compiler error on Monday. So I downloaded and installed the beta update. Just now got another compiler error with the update installed.


After double-checking it appears my update module reverted back to 1031. So I need to re-apply the beta. NEVERMIND. D'OH.

I temporarily changed update to automatic to acquire the beta and afterwards changed back to eras mirror. It must have changed me back when I went back to pulling updates from the mirror.

 

Seems to have made no difference. Just got a compiler error. Computer is set to pull updates automatically and is not pulling updates from eras mirror. This is actually the first error I got with update set to "automatic".

Virus signature database: 5667 (20101202)
Update module: 1032 (20101025)
Antivirus and antispyware scanner module: 1293 (20101110)
Advanced heuristics module: 1115 (20101116)
Archive support module: 1123 (2010110
Cleaner module: 1049 (20100604)
Anti-Stealth support module: 1023 (20101125)
SysInspector module: 1217 (20100907)
Self-defense support module : 1018 (20100812)
Real-time file system protection module: 1004 (20100727)

 

Just wanted to chime in...

I recently started getting this on my XP Pro sp3 (fully updated) box. This is my personal workstation, and the only one out of 50+ workstations (all XP Pro fully updated) that is getting this error.

I have followed the full uninstall reinstall crapola twice now, and it does fix it temporarily for a few days, but now I'm getting it again.

Seeing how long this problem has been ongoing does not give me any confidence that this will be fixed anytime soon, and I can NOT be doing this on my workstation every few days.

ESET... I am the decision maker for what Antivirus runs on our network. What are you going to do to keep my business?

 

at 1221 GMT started to see this error again - Eset could you please check your servers and make sure that the updates are not being delivered corrupted?

W7 64bit / NOD 4.2.71.2

Virus signature database: 5835 (20110131)
Update module: 1032 (20101025)
Antivirus and antispyware scanner module: 1293 (20101110)
Advanced heuristics module: 1115 (20101116)
Archive support module: 1124 (20101214)
Cleaner module: 1050 (20101207)
Anti-Stealth support module: 1024 (20101227)
SysInspector module: 1217 (20100907)
Self-defense support module : 1018 (20100812)
Real-time file system protection module: 1004 (20100727)

 

This has nothing to do with update corruption. Unfortunately, it seems that the latest update module didn't eliminate the error for your completely.

 

throughout the threads related to this issue I cannot trace a single explanation why the updates work stable for days/weeks/months and the sudden occurrences of this phenomena...

it is obvious though that when virus signature updates being fetched and received corrupted at the user's machine this happens. hence begs the question where the corruption is happening

 

I continue to have problems with this as well. I just received another compiler error and my work pc is set to "automatic" now and also receiving pre-release updates.

The strange thing is this seems to come in spurts where I can go days without incident and then it will occur repeatedly for a few days. What I've found is on the days it occurs, clearing the cache and rebooting does not solve the problem on that day.

However when I shut down the pc at the end of the workday the system will acquire the updates properly the next morning when I turn it on. It's become normal for me now when the error occurs on a particular day to clear the cache and don't even bother to reboot because the error will repeat itself until the system has been turned off for an unspecified period of time.

As I originally mentioned my pc had no problems with this for nearly 6 months when I first set up this new system. But for whatever reason it started happening and has been a problem ever since.

I now have 5 or 6 Windows 7 systems on this network and so far only my system and another mentioned previously have this problem. I am keeping my fingers crossed that it doesn't start occurring on the other systems because once it occurs on a system there seems to be no fix.

 

Marcos, I PM'd you my registry key you asked for...

Can you confirm receipt? And is there anything else I can provide to try to nail this?

Thanks

 

After reading https://www.wilderssecurity.com/showthread.php?t=292282

I've decided to disable "enable self defense" option on my work computer and have changed NOD to pull updates from the mirror in order to attempt to accelerate the chance of the compiler error occurring. If it occurs I will report back.

 

It's been a full week now and have not received any compiler errors since removing the check mark from "enable self defense". At this point I won't report again unless I get a compiler error. For now I invite anyone else with the problem to give this a try. Perhaps we can confirm this is causing the update problem.

 

Just received a compiler error......

 

Paging Marcos... still haven't heard back...

The problem was fixed, but has now returned AGAIN...

You have a very unhappy decision maker here for a 70 user license...

 

Oh, well, obviously ESET doesn't have much interest in solving this problem...

I'm even willing to give someone Remote Access *while I'm watching*, to get this resolved, but hey, you can't make the offer if no one is responding to pleas for help.

Guess its time to consider alternatives, seeing as my 70 user license expires in September, and I'm not the kind of person who waits till the last minute.

ESET - either contact me and RESOLVE THIS PROBLEM, or lose a customer.

PERIOD.

 

Not sure what problem you're referring to, whether the one with the last update shown with year 1601 that we discussed via PMs or a problem with error 0x101a occurring during an update. If the latter, I've already provided a few files that are supposed to crash ekrn and generate a dump if a problem occurs during an update to 2 people from Wilders'. If you're willing to install them to help us troubleshoot the above mentioned error, let me know.

 

Marcos I'm game. PM me instructions and file location and I'll be happy to help on the compiler issue.

 

Both problems seem to be related and come and go... ie, currently, it now says the last SUCCESSFUL update was at the last time I tried to update, but the update was NOT successful (General Compiler Error) and the current sig version says '5868 (20110212)'...

The PROBLEM I'm talking about is this whole problem with updates repeatedly going south for no apparent reason, after they are fixed by the time consuming and tedious uninstall process we have to go through.

This has been going on for a long time, although I only got bit by it back in December...

 

Oh, and certainly I'm willing to help troubleshoot... just please provide simple instructions on what I need to do...

 

(crickets chirping here)
I've heard nothing back from Eset.

Also want to add the second computer I originally mentioned received a compiler error last Friday.

On top of that I now have another newly installed windows 7 system with a new problem which after searching I see no fix for either. This new system has been on the network for a few weeks and periodically generates two error messages upon computer boot. Problem occurs about once a week....so far.
The first error is "An error occurred while starting proxy server. Checking of application protocols (POP3, HTTP) will not work."
Followed immediately by "An error occurred while starting services. Analysis of application protocols (POP3, HTTP) will not function."

I did some forum searches for these errors and see they appear to be known issues and have been discussed, but I did not see any solutions to this problem either.

So to review. I started this thread in October of 2010. I now have 5 Windows 7 machines on this network. 2 continue to have the compiler error problem and another now has a new issue. Three out of five with problems......so far.

 

Other than Windows and ESET, do you have *any* other software or drivers that are common to all the computers? Seems odd that you have a 60% problem rate from machines but we have a 0% rate from 122 machines. What do you have installed that we don't, or v-v ?


Jim

 

These machines have only a few things in common.

2 are/were brand new Dell optiplex systems. The new one mentioned (3rd pc) is a new dell e series laptop. Common denominators besides that would be Windows 7, Office 2007, NOD32 v4.2.71.2., adobe acrobat 9. No AV or security software was pre-installed on these systems. All software is fully up to date including flash and java. These machines are on a Windows 2003 active directory network. Machines are using offline files feature, but not using DFS.
These systems do not run the Dell security suite (formerly wave systems) which comes pre-installed on all dell systems as I remove that immediately when I turn on a new system.
I am showing no event viewer errors on my servers, nor on the client pc's in question.

As you can see earlier in the thread I submitted a number of reports to Marcos including wireshark and process monitor. Nothing unusual shown in those reports.

I have 2 windows 7 x64 machines at home and never a problem with either of them. I do not have java or adobe reader on either of those systems for increased security reasons. One is a custom build and the other a dell optiplex 745 sff in which the disk was repartitioned, formatted and clean install of windows 7x64.

Guess I should mention the 2 systems which have not generated any errors yet are also new dell systems. One is an optiplex which has been online for around 3 months now and the other is another e series laptop which has been on the network for around 2 months and same common denominators as the others. That optiplex system is pulling updates from the mirror server while the other 4 are pulling updates "automatically" via the internet. All of these systems I did a manual install of NOD32 and did not use a preconfigured cfg.xml file.

And as I edited this post I see another compiler error has just occurred on my machine...lol..(clearing cache and rebooting).

Update: just finished installing Win7 SP1 on my work pc.....not holding my breath.

 

I have been receiving the following error quite a bit lately on various computers throughout the company

During execution of Personal firewall on the computer GRANTR, the following warning occurred: An error occurred while starting proxy server. Checking of application protocols (POP3, HTTP) will not work

It seems as if this forum has been discussing this issue for a while and I am wondering if there has been any resolution. A reboot seems to clean it up temporarily, but I would like a permenant fix.

All the computers that I am seeing this on are Windows 7, but I haven't seen it from all my Windows 7 computers, which for the most part are a standard issued image, so they should be all the same for the most part. Please let me know if you have any insight on where I could start troubleshoting this or if you need a PM from me.

 

This is a completely different issue than the one this thread is about. Recently I've resolved that error by setting certain system network services to start at system startup. In order for me to tell if it's the same problem I'd need to check a SysInspector log from that computer. Once you have it created, upload it somewhere and PM me the link.

 

Enabling pre-release updates has reduced the compiler errors on my work computer. Ironically I had one today and another earlier this week. Before that I hadn't had any for several weeks.

I'm beginning to ramp up the rollout of Windows 7 in our office. Fortunately this is not occurring with all Windows 7 machines being deployed and keeping fingers crossed that it doesn't start. I'm hoping this is something that continues to be worked on and hopefully resolved in v5 BE. I recently renewed our corporate license for another 2 years with NOD32. So I'm trusting my faith in Eset will be rewarded.