EMON Add-in error message with Outlook 2007 on Vista

I have just got myself a brand new Dell PC with Windows Vista Ultimate and Microsoft Office Professional 2007 pre-installed. Up to now have been a very satisfied longtime user of AVG Antivirus with no problems ever, but decided I wanted the best possible protection for my new system, so after doing some online reserach decided NOD32 looked like the way to go. Downloaded and installed the trial of v2.7 on Thursday and installed it with ref to recommended setting on this forum.

However, since installing it, while Outlook 2007 is open, every 2-3 hours (usually when I'm not actually doing anything in Outlook) up pops an error window as follows:

(Incidentally, at this point my windows system monitor shows plenty of CPU and memory resources available).

When I then try to close the error message I find have to click OK many, many times before the error message goes away and I can use Outlook. I then completely shutdown and restart my PC again- and all is fine until another hour or so when up pops this error message again.

Does anyone know what might be causing this? As this was pretty much a clean install on a brand new PC, this has severely dented my confidence in NOD32, and I'm glad I'm still running the trail and have not committed yet to a purchase. I therefore hope that someone can help resolve this issue and restore my confidence in NOD32!

Thanks

 

Hi there, welcome to Wilders.

As far as I am aware, this is a known issue with Outlook 2007, and ESET are addressing the issue. For the moment try disabling EMON and rely on IMON for checking your email.

Please let us know if this temporary solution works.

Cheers

 

Thanks. Sounds like a pretty serious flaw to me, if the program does not work with Outlook 2007! Anyway, you say "try disabling EMON and rely on IMON for checking your email". Will this offer me sufficient protection when checking my mail via Outlook?

I must say, this is not a good start for me as it gives an extremely poor impression of NOD32 if it will not work properly with such a major product as Outlook 2007 - particularly as Outlook 2007 has been out for a while now.

I guess I should also contact NOD32 support directly about this. What's the best way to contact them?

 

To update - I just found ESET's UK phone number on their website and phoned them. The guy I spoke to confirmed that "Outlook 2007 is NOT currently supported by NOD32."

This seems quite poor to me, or at least I feel this should be made very clear by them on their website. He could not give me a date when it will be supported, but did state (as you did Blackspear), that EMON offers extra protection but this not required. He said that as I am accessing POP mail accounts, I will still be protected by IMON.

That reassures me, although it kind of contradicts this that when (as instructed) I went to the NOD32 control panel, clicked on EMON, and quit that module, it does warn me that Outlook will not be protected!

Oh well, as I've said, not exactly the best first impressions of NOD32, but I'll persevere for the rest of the trial period before making a decision.

 

No, not at all, it is in testing.

Perfect protection, nothing at all wrong with IMON protecting any POP3 account.

Cheers

 

5 machines, 5 copies of Outlook 2007, 5 copies of NOD32 and ALL function properly. It must be a "Vista thing" since these machines are running XP (3 Pro, 1 Home, 1 MCE).

 

Hi
I am lost (not unusual....lol)with this thread.
Why you ask? (thanks for asking) .... I NEVER knew that Office 2007 and NOD32 did not get along, when installed on Vista.
I was plugging away not knowing
I will say that I have never had Outlook 2007 active for 2-3 hrs, so that maybe why I don't get the error message with Nod32/Office2007/Vista combination.
I am glad that the OP has brought this to the forefront so the rest of us now know about this problem, also sorry to see that the OP had the problem in the first place.

Cheers

 

i'm using outlook 2007. no problem at all with NOD32.

 

Yeah, yeah, very funny. I detect a great deal of cynicism going on here! I'm glad the rest of you have encountered no such problems, but simple fact is I had nothing but problems with the repeated NOD32 Add-in errors popping up in Outlook 2007, AND, on phoning ESET Tech support the guy immediately confirmed there were aware of these issues and they are working to fix them.

So I appreciate your loyalty to the brand, but believe me I'm not gonna waste my time making this up!

 

im using outlook 2007 and nod32 since the release of vista and i never had any problem as the one mentioned.

the error must be something very specifig - not a general problem...

 

@guitareth
I was not being cynical, so you have totally misunderstand my response.
I am NOT denying or disputing that you have the problem, although some of us have not seen that in our setup.
I do use NOD, but I am not tied to NOD. I use other AV's on my other machines.
I was not aware that this anomally existed between NOD & Outlook 2007 (as stated by the NOD rep. you spoke to, and Blackspear's response), so I really do not think you were "making" it up.
I will repeat, that I am sorry you are having that problem, as it would annoy me, if I had it also.
If you ever get a solution, please let us know the results, as I would be interested in knowing what is the cause of such a problem.
Cheers

 

I can confirm that I have the same problem as the author of this thread. I am running Nod32 on Windows XP with Outlook 2007 on 3 computers. Oddly enough, it works absolutely fine on the oldest computer (no problem for over 3 months) but on the 2 new computers, it has happened from the beginning. I have no logical explanation as to why it would happen on 2 of them and not the third other than that the oldest computer was originally installed with version 2.5 and updated naturally through the Nod32 updates. The other 2 were installed with version 2.7. Can anyone confirm these findings?

Uri
Nod32 Reseller
Israel

 

I have the same problem on one Vista machine, but do not have any issues in over 3000 installs of Nod32 on other workstations running Win98-XP and various Linux flavors...and have not had an infiltration on any network running nod32 in 7 years. The issues with Nod32 are few and far between.

Concerning the Outlook 2007... I would like to know what 'else' anyone is running WITH Outlook 2007. Maybe it's a combo of apps before it appears.
In my case... I may go a week without the error....and then I get it constantly. Then.... away it goes again.

My configs are :
Outlook 2007 on Vista Business platform.
I run Microsoft BCM -Business Contact Manager.
I run Active Sync to a WM 5.0 Pocket PC Phone Edition device and sync contacts... including messaging.
I have approx 10 accounts that Outlook checks and they are a mix of pop/smtp and MAPI.

Guitareth... I understand you thinking "So I appreciate your loyalty to the brand"..but for me, it's not about that at all. For me it's about not having to worry about whether my networks are protected or not.
I'll drop Nod32 'in a heartbeat' if I suffer ANY grief at all due to an infiltration... PROVIDED there is another solution that I would consider 'as good or better' than what I have.
IT is hard stuff...... if it were only Outlook 2007 that Eset had to be concerned with it would make it much easier on them. As it is...there are many, many, many email clients that have to be dealt with.
IF there is a solution to this problem...Anton will figure it out. If there's not... I will be sorely surprised. But I certainly won't be disappointed.

 

I don't have any solutions, but I am running Vista Ultimate (32bit), and Office Ultimate 2007 and have had no problems at all with Outlook 2007 and NOD32

 

My configs are:
Vista x64 ultimate + all updates
Outlook 2007 without business contact manager + all updates
2 pop3 accounts
NOD32 2.70.39

No error messages or problems.

 

I used to run NOD32 on Vista Home Premium / Windows XP (3 different computers) and Outlook 2007, no problems then with the Outlook plugin.

 

I have had this error message on and off with Outlook 2007, most notably (and with a LARGE number of repeats of the error message box) when I imported my .pst file that I had been using with Outlook 2003 on my previous PC. My .pst file was quite large -- in the order of a few gigabytes, so I set up the Auto Archive and archived the old messages to reduce the inbox size. This has reduced the problem to a few occurrences of the error message every week or two.
We have a Small Business Server 2003 setup with all the email going through Exchange. I am running Outlook in Cached Exchange mode (no POP3 accesses being done from my desktop PC).