Outlook Automation.

OK we use a program that automates Outlook (it adds calendar appointments). All was fine until about three/four days ago when my machine started reporting errors when trying to add the appointment.

If I close Outlook it works as expected, but if I have Outlook open already it doesn't work anymore.

Rebooted, and it didn't help.

So I disabled NOD32 v.3 (642) as much as I could and it still acted like that. I then uninstalled NOD32 and poof it worked as expected again (ie it would add the appointment when Outlook was opened or closed).

I then reinstalled NOD32, left it in default state, but prevented it from updating.

Tested, and the program still works.

I then applied our usual XML settings to it, continued testing and the program continued to work.

I then allowed it to update to the newest defs and it still worked, so I figured it was some kind of corruption in NOD perhaps.

So now flash forward to today, and it's doing it again, if Outlook is closed it works (creates it's own hidden Outlook instance and makes the appointment), but if Outlook is open already, it won't add the appointment and the program reports it failed to connect to Outlook.

I wrote this program, so I know nothing has changed about the way it works, but still I went over it all with a fine-tooth comb anyway, comparing it to previous versions, etc. and there is NOTHING changed about the (very standard) way it does the Outlook OLE automation.

It also does similar automation to Word, and it still works as expected, whether Word is open or not.

I've found suggestions that it's the anti-virus (not NOD specifically) that blocking the automation against Outlook because it considers it to be threat of some kind, and the solution is to disable script protection (or similar).

It seems that even if I completely disable all the real-time protection, turn all Outlook integrations settings off, etc. it still blocks it.

And I can't find anywhere where it will actually TELL me it blocked it, or any way to tell NOD32 that the action is safe.

So what should I do next?

System specs:
Vista 32 bit
Outlook 2007
NOD32 3.0.642
Virus signature database: 2931 (20080307)
Update module: 1023 (20080229)
Antivirus and antispyware scanner module: 1107 (20080303)
Advanced heuristics module: 1070 (20080212)
Archive support module: 1074 (20080307)
Cleaner module: 1026 (2008022

 

At the beginning it worked , it worked with NOD32 3.0 installed + updated + configured ... Try again to uninstall EAV and to see if your program will work . Experiment.

When ESET program think something is threat , dangerous , it will let you know . No threat will be blocked silently unless you configure the program this way . It must be something else other than NOD32 thinks your "creature" for threat.

 

Hi techie007,

What's the program your using with Outlook please.

When you say "All was fine until about three/four days ago", was anything else changed on the network at all, at or around that time?

Thank you
BFG

 

Re: Outlook Automation woes.

Thanks for the response guys.

HiTech_boy:
I just finished going through the same steps I performed a week ago when it did it the first time, and a reinstall worked, for about an hour. I made a log of what versions were what and such, I'll attach it at the end of this.

I double checked all my notification settings and they are all set to tell me if anything happens, and I do get notices about updates, etc. no problem.

BFG:
The program is a custom application I wrote/write for us to use at work. It helps us create uniform paperwork in Word and then adds appointments to a couple public calendars in Outlook.

Nothing else had changed about this system to make it not work.

Like I said to Hitech_Boy, I just went through it all again and it worked for about an hour after it was all up-to-date, and then it stopped for no apparent reason. Here's the log I made, I saw the same results as the last time I did this:

Weird huh?