NOD32 2.5 final EMON error

What is this EMON error

18.5.2005 18:25:26 EMON Neúspešný pokus o zavedenie modulu [2]. NT AUTHORITY\SYSTEM
18.5.2005 18:25:26 EMON Neúspešný pokus o zavedenie modulu [2]. NT AUTHORITY\SYSTEM
18.5.2005 18:10:33 Kernel Vírusová databáza bola úspešne aktualizovaná na verziu 1.1100 (2005051.
18.5.2005 15:56:17 EMON Neúspešný pokus o zavedenie modulu [2]. NT AUTHORITY\SYSTEM
18.5.2005 14:08:32 Kernel Štatistické informácie boli poslané do spoloènosti Eset.
18.5.2005 11:12:20 EMON Neúspešný pokus o zavedenie modulu [2]. NT AUTHORITY\SYSTEM
18.5.2005 11:12:20 EMON Neúspešný pokus o zavedenie modulu [2]. NT AUTHORITY\SYSTEM

 

maybe will help u this

 

He's inquiring about the EMON loading failure.

Japao, pošli email na servis@eset.sk, kolegovia poradia. A pridaj aj info o nainštalovanej verzii MS Outlooku.

 

Dear Marcos, I think Stephanos G was referring to the log event posted by me (Cliff)
Regards the issue with EMON.....My problem started with the Beta 2.50.9. It was installed over 2.12.3. everything worked fine except when i used office outlook 2003. Thats when the Log error appears( it will only happen once a day regardless how many times you access your email that day). On friday 13 May NOD32 auto updated to 2.5.16, "problem still occured". I phoned NOD32 technical UK.....They advised me to do a fresh install.
1. Add/remove NOD32
2. Delete ESET folder
3. Check Registry(optional.. advise you only go here if you KNOW what to do..ESET are that good they remove these entry's)
4. Reboot
5. Install NOD32.....suggest you look at Blackspears Brilliant Sticky https://www.wilderssecurity.com/showthread.php?t=37509
6. IF your happy with setup, suggest you delete any windows system restore points before this install date
So far so good....ALL BETA INSTALLS should be removed and a fresh install should be preformed.....Hope this helps!!

 

Yes Cliff, your log error looks like Japao's error.

 

You are right.. "Neúspešný pokus o zavedenie modulu" is slovak.. and you can translate it as "Unable to load EMON module...".

 

Japao, any news?

 

Japao,...Did you find out why this happens and any fix to stop error

 

Hello,

As said in Cliff's topic on the beta forum, I have the nod32 v.2.50.19 and Outlook 2003. But unless him, this message with EMON

Happens once and not once a day, but each time i shutdown outlook. May I precise I've tried many suggestions offered in this thread and the posts about configuring nod32, done the fresh install thing, even mailed the tech support, who said they didn't know about this issue and were working on it. No news since then.

So far as I've found, this has something to do with Outlook's closing time : when it takes too much time (dunno why anyway...) to Outlook to close, more than around 500ms, EMON generates this error (not on the screen but in the event log.)

Thanks for your suggestions,

IcePanther

 

Hello,
I am getting this error too, since first beta of EMON! Now, in the final, this "bug"(?) is still present...

I am using NOD 32 2.50.25 and Microsoft Outlook 2003.

 

Try to re-install your NOD32. And let us know if the problem still persists.

 

I even tried to use latest version 2.50.25, but it was useless. I get this error no matter what.

 

Reinstalled, Error still present.

 

Can everyone with this issue please send an email to support@nod32.com and place a link to this thread. If you do not hear from Eset within 3 days (allows for weekends), please advise us here...

We would appreciate if you could keep us in the loop with your progress, as we all learn this way…

Cheers

 

I'm chatting already with the guys, there is no 3 days delay

 

Me too, at least I WAS, I ot no answer for a moment. They toldme they were trying to duplicate the problem, and then, nothing.

 

Happy Bytes..my event log has gone crazy since the 28/6/05, Before that it was about every 5 days you would get one error.Setup is NOD32 2.50.25 Windows XP home SP2...Outlook 2003

Time Module Event User
01/07/2005 14:35:43 EMON Unable to load module (2). NT AUTHORITY\SYSTEM
01/07/2005 14:27:47 Kernel Statistical information has been sent to Eset.
30/06/2005 23:33:48 EMON Unable to load module (2). NT AUTHORITY\SYSTEM
30/06/2005 21:44:20 Kernel The virus signature database has been successfully updated to version 1.1159 (20050630).
30/06/2005 15:44:15 Kernel Statistical information has been sent to Eset.
30/06/2005 15:44:15 Kernel Statistical information has been sent to Eset.
30/06/2005 14:46:17 EMON Unable to load module (2). NT AUTHORITY\SYSTEM
30/06/2005 14:46:17 EMON Unable to load module (2). NT AUTHORITY\SYSTEM
30/06/2005 14:46:17 EMON Unable to load module (2). NT AUTHORITY\SYSTEM
29/06/2005 20:42:58 Kernel The virus signature database has been successfully updated to version 1.1158 (20050629).
28/06/2005 21:29:24 Kernel The virus signature database has been successfully updated to version 1.1157 (2005062.
28/06/2005 16:26:46 EMON Unable to load module (2). NT AUTHORITY\SYSTEM
28/06/2005 15:28:30 Kernel Statistical information has been sent to Eset.


Is the fault related to the data files (.pst) in outlook 2003 that are shown in Nods scanning targets window ( folders and files)

 

This error could occur with detailed logging enabled, even though there is actually no problem (it's returned by MS Outlook and MAPI itself). Could you check if EMON is actually scanning email?

 

How can I check if EMON is acutally scanning?

 

Hi, Marcos......I received an email regarding this issue from Aspect Systems(ESET)U.K. They confirm the information in your post. This is a copy of the email sent although the NOD32 stamp (NOD32 EMON 1.1160 (20050701) information) must have been in the email sent, i only ever have the stamp shown at the bottom of the email:


Hi Cliff

I have spoken to global support about the EMON error we were discussing on Friday.

They said that the error is actually caused by Outlook/MAPI returning senseless error codes even when everything is working fine, and probably only appears when detailed logging is set for EMON.

So as long as EMON is actually checking emails then it's nothing to worry about. However, if it's annoying you could turn down the logging detail level in EMON setup.





_____________ NOD32 EMON 1.1160 (20050701) information _____________

This message was checked by NOD32 antivirus system
http://www.eset.com



__________ NOD32 1.1160 (20050701) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com




EMON shows 8 files scanned when i retrieved my email