Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: rider5512 on June 29, 2012, 01:58:21 PM
-
The new release of avast has created a problem with Outlook 2010 calendar.
If you try to open an appointment in the calendar outlook will crash.
Opening outlook again comes up with a message that the avast outlook add-in is creating a problem, do you want to disable this add-in. Not disabling Outlook will crash again when opening an appointment. Once the add-in is disabled then appointments will open OK.
The problem also occurs with Outlook 2007 on another machine.
Build details are: 1. Win 7 Ultimate x64 and Outlook 2010 and 2. Win 7 Home Premium x64 and Outlook 2010
-
Same problem.
-
I was using the "Find a Contact" search box in the ribbon when outlook crashed on me. The reason for the crash was the avast plug in isn't compatible.
-
Same here, oddly never had an issue with previous plug in this seems very incompaible?
Windows 7 64 bit /outlook 2010 64 bit.
-
I have solved the problem with a installation from scratch.
-
Installed from scratch, but still outlook not connecting even...
-
Mine was a clean install anyway!
-
Hello,
thank you all for your feedback. We have fixed this issue.
To fix it on your computer please download AsOutExt.dll and AsOutExt64.dll from:
http://public.avast.com/~kurtin/AsOutExt.dll
http://public.avast.com/~kurtin/AsOutExt64.dll
Then disable avast! selfdefense module in Avast Settings - Troubleshooting and
copy these files into your Avast directory (usually C:\Program Files\AVAST Software\Avast).
Your problem should be fixed.
Regards,
Ivan.
-
now that is fast!
-
Hi,
could you please report us whether the probem with Outlook calendar was fixed by mentioned patch?
We apologize for any inconvenience.
thanks,
Pavel
-
I think it would be smart to make such patches automated installers that are digitally signed and don't require user to disable self-defense. Not all are willing to go through process of searching for install folder and manually disabling self-defense. Mostly because most users aren't that skilled.
-
Wouldn't this be just the thing the Emergency Update tool (scheduled task) should be used for ?
-
Hi Avast team,
Avast was not working since yesterday evening after i updated. I have paid more then a 1K and what i get is that that i cannot connect using my outlook, my network is down for almost 10+ hours after i have upgraded. Avast team, please put some real testers in your team, and test scenarios using various OS. This is a ridiculous way of pushing update and making the whole system unstable. This is really a bad experience from the avast team. .
-
why was this update or fix not sent through the
emergency update sequence sector??
-
why was this update or fix not sent through the
emergency update sequence sector??
[/quote
+1
-
Wouldn't this be just the thing the Emergency Update tool (scheduled task) should be used for ?
+1
Good way to solve this I think. We can test its functionality before major trouble happens.
-
Sorry, I have already made a new topic.... :( As you can see in http://forum.avast.com/index.php?board=2.0
-
Wouldn't this be just the thing the Emergency Update tool (scheduled task) should be used for ?
Actually no. avast! Emergency Update is designed to update avast! in case if avast! service itself fails to work because of some fault in the update.
For example if they released an update which turned out to cause horrible avast! problems where no avast! interface loads up (including tray icon), avast! service fails to run and updater fails to operate. In such cases avast! Emergency Update will still work because it's a standalone app being triggered by a Windows Task Scheduler.
I'm assuming this app works a bit different and they have some sort of server trigger. If this emergency updater detects it on their servers it will roll over the files and data found on the server, potentially recovering avast! to its operational state again.
What we have here is just a crash problem with one of its components, you still have avast! and internal updater working so a normal program update can be released. I also know they can enforce the program update if they want so that users get it right away if needed without weekly waiting to spread out the load on servers or to ask user for confirmation.
-
Machine: MS Windows 7 Ultimate SP1 (x64) and MS Office Professional Plus 2010 (x64).
- Manual update from AIS 7.0.1426 to AIS 7.0.1451 using the GUI.
- Reboot
- Error opening MS Outlook: see picture error_ais.jpg
- Problems with calendar
- Fix applied
- Reboot
- Same error opening MS Outlook
- Problems with calendar
- Uninstall AIS 7.0.1451 using Control Panel -> Software
- Reboot
- Used aswclear.exe
- Reboot
- Deleted entry in registry using regedit: Current user -> Software -> Avast Software (Why aswclear.exe don't delete this entry in the registry?)
- Reboot
- Install AIS 7.0.1451 from scracht
- Reboot
- Error opening MS Outlook: see picture error_ais.jpg
- Problems with calendar
- Fix applied
- Reboot
- Error opening MS Outlook: see picture error2_ais.jpg
- Reboot
- Error opening MS Outlook: see picture error_ais.jpg
- Something rare: see picture error3_ais.jpg
- Disabled the avast addin complement in MS Outlook. see picture error4_ais.jpg
- MS Outlook is working with the avast addin complment disabled
Waiting for a solution!
-
The new release of avast has created a problem with Outlook 2010 calendar.
If you try to open an appointment in the calendar outlook will crash.
Same here with 2007.
Opening outlook again comes up with a message that the avast outlook add-in is creating a problem, do you want to disable this add-in. Not disabling Outlook will crash again when opening an appointment. Once the add-in is disabled then appointments will open OK.
Same here with 2007.
-
Wouldn't this be just the thing the Emergency Update tool (scheduled task) should be used for ?
Where is it on the interface... I've dig everything...
-
It's here Tech in the scheduled tasks
-
What we have here is just a crash problem with one of its components, you still have avast! and internal updater working so a normal program update can be released.
Yes, that's pretty accurate (including the rest of the post). An ordinary program update will be released in this case, but first it's needed to know whether the prepared patch actually solves the problem.
-
It's here Tech in the scheduled tasks
Well... I do not particularly love the scheduling and on each logon... I've relaxed somehow the scheduling...
-
Updated to 7.0.1451 and had even more problems with Outlook (the previous 7.0.1426 version would allow Outlook to open but Outlook would freeze after receiving or sending e-mails and I had to use Windows Task Manager to close and reopen). Followed the instructions by IvanM above and downloaded the patches: AsOutext.dll and AsOutExt64.dll. Copied and replaced them in the avast folder after inactivating the Avast self defence as instructed. Checked that both files are dated 30/06/2012 instead of 28/06/2012, 8.51 am.
Still does not work and I have to allow Outlook to disable Avast add-ins before I could even open Outlook 2007 (Outlook crashes and would not even open if I do not allow it to disable the Avast add-ins). I then checked and saw that both "avast!Add-in" and "avast! Antispam add-in" had been disabled by Outlook.
I am running Outlook 2007 (12.0.6607.1000) SP3 MSO (12.0.6607.1000).
-
It's here Tech in the scheduled tasks
Well... I do not particularly love the scheduling and on each logon... I've relaxed somehow the scheduling...
avast! Emergency Update task is delayed for 2 minutes on system boot, so it shouldn't interfere with the boot process itself (speed or compatibility wise).
-
avast! Emergency Update task is delayed for 2 minutes on system boot, so it shouldn't interfere with the boot process itself (speed or compatibility wise).
It's not enough to me. I'm loading other things at 2 minutes...
-
These same DLLs also cause Outlook 2000 to crash on exit on my machine. Disabling them (via the program OfficeIns) stops the crashes. Replacing the DLLs with the updated ones that fix the Calendar issue doesn't stop the crashes.
What functionality am I losing by disabling these add-ins? Is there a fix planned for the Outlook 2000 crash issue? I realize this is an old version of Outlook, but it worked flawlessly until Avast! updated itself this morning.
Thanks,
David
Hello,
thank you all for your feedback. We have fixed this issue.
To fix it on your computer please download AsOutExt.dll and AsOutExt64.dll from:
http://public.avast.com/~kurtin/AsOutExt.dll
http://public.avast.com/~kurtin/AsOutExt64.dll
Then disable avast! selfdefense module in Avast Settings - Troubleshooting and
copy these files into your Avast directory (usually C:\Program Files\AVAST Software\Avast).
Your problem should be fixed.
Regards,
Ivan.
-
Hi,
I installed the two *.dll files that you said, and now I can open MS Outlook 2007 Calendar tasks; but when I close the program, appears a messaje saying that MS Outlook stopped working.
Any suggestion will be appreciated. Thanks!
-
The same of noelrojasc happened for me...
-
I had an issue with Outlook 2003. Messages that were read would not be marked as read.
You could not manually mark them as read.
You could mark the folder as read.
I moderate 4 Yahoo groups and get a lot of email Big Isuue wit me.
I downloaded the "mentioned" fixes.
After turning off safety features I still could not load the files because they were in use.
I tried copying them in a command window , same problem.
I had to go to msconfig and stop Avast from loading and the copy the files and then redo msconfig.
I had also changed Avast to load last.
The problem does SEAM to be fixed
DELL 400SC Win XP SP3
I am running Foxfire on the Laptop and Windows 7 so I will see haw that goes.
Jim B.
-
Had the same problem Outlook 2010 and the fix was fast. avast should of had this update to set to auto. :D
-
I'm running Outlook 2007, on Windows 7 (64 bit), and had the same calendar crashing problem for the past several days since the last Avast update.
I disabled the Settings>>Troubleshooting>>Self-Defense mode, then copied the 2 DLL's into the Avast5 folder (replacing the 2 existing dll's there with the same name).
Outlook is now running correctly, no crashes from opening calendar appointments, and Outlook did not crash upon closing it either. Turned the Self-Defense back on.
Should have been an auto-update but glad there was an easy enough fix I could find by googling.
-
A better way to solve the problem now is to update to version 7.0.1456 (released yesterday), which already contains the fix.
Thanks
Vlk
-
Did same as Nbot.
I'm running XP PRO and using Outllook 2007. Replacing DLL files as instructed in Forum fix seemed to have worked.
I dunno, who do AVAST think they are, RBS?
;)
-
A better way to solve the problem now is to update to version 7.0.1456 (released yesterday), which already contains the fix.
Thanks
Vlk
For me, it has the calendar solution but the contacts fails: when open a contact, the plugin crashes and Outlook is closed.
I'll try to upload the dump.
http://forum.avast.com/index.php?topic=100528
-
Opening contacts was also causing MY Outlook to crash. The DLL fix helped solve both problems.
However, I am still having a problem that wasn't solved by the new dll's, nor the latest upgrade (I'm running: 7.0.1456)
If I hit send on an email, but realize I forgot something, and go into the outbox to open it and edit it (I have my send/receive set on a 4 minute delay for times like this), the email will not re-send after I edit it while in the outbox. :( So, I have to create a new email, or copy & paste my response into a new reply, as the initial email waiting in the outbox cannot be edited and sent again.
This is definitely a problem since this last major Avast upgrade.
This is the specific error message that pops-up: THE MESSAGING INTERFACE HAS RETURNED AN UNKOWN ERROR. IF THE PROBLEM PERSISTS, RESTART OUTLOOK.
Avast, can you please look into this? I should be able to edit emails that are in the outbox waiting to be sent. I believe the new software version somehow gets lost scanning an email again already in the outbox?