Author Topic: AIS error 153  (Read 4892 times)

0 Members and 1 Guest are viewing this topic.

evcox

  • Guest
AIS error 153
« on: January 19, 2012, 08:06:45 AM »
While working on a friend's computer to resolve an unrelated problem, I noticed that a great many "unp*******.mdmp" were being created. No other visible problems with Avast. Updates, scans, etc appear OK. The Outlook toolbar is present and a selected msg can be MANUALLY marked and unmarked as spam but NO msg's get AUTO marked or sent to junk folder. The AsOutExt.log contains many entries with the following:  "avast! Antispam encountered an error no. 00000153. Returned code: 80040201". As this is not my machine, I prefer to not actually download email but simply opening the Outlook inbox will generate at least one of these log entries. Using the Avast program settings to turn off antispam has no effect --- the addin module flash wndow still appears upon opening Outlook and the log is created. I turned on the debug switch and saved the log and dump files. I hope a simple explanation of the error and return codes will allow me to correct the situation and get this machine quickly back in service.       
 (Paid) AIS version 6.0.1367.0  , MSOutlook version 9  , WindowsXP SP3 

evcox

  • Guest
Re: AIS error 153
« Reply #1 on: January 22, 2012, 10:48:27 AM »
I'm surprised there have been no replies to my question. Even more so that there is so little info on ANY of the myriad error/return codes Avast uses. In the mean time, I've tried to take a few steps to help the experts if/when one does respond. Did a "repair" of AIS through Windows control panel and then set it for debug and rebooted my computer. Upon opening next Outlook the antispam module did not load. I then manually "installed" the addin in Outlook and rebooted. Again starting Outlook, the addin splash appeared and the toolbar was visible. Downloaded 259 emails OK (though it seemed a bit slow). None got marked as spam though many probably should have been. Checked Avast gui which seemed to show the emails had been scanned with 15 flagged as spam. The Avast/junk folder in Outlook remained empty. I MANUALLY selected two and marked them with the toolbar with no problem. Checked the AsOutExt.log and saw 15 instances of the "avast! Antispam encountered an error no. 00000153. Returned code: 80040201". Checked Avast log folder and found about 10 - not 15 - "mdmp" files within the time frame. All files are available for the experts and I have used Notepad to select and create a file containing only the relevant portion of AsOutExt.log as, otherwise, it is quite large. But, I don't know how to provide any data for review - there is no forum option to "attach" (because I don't yet have 20 posts???). Waiting for suggestions. Thank you.

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37561
  • Not a avast user
Re: AIS error 153
« Reply #2 on: January 22, 2012, 10:53:20 AM »
Quote
Even more so that there is so little info on ANY of the myriad error/return codes Avast uses.
List of avast error codes   http://forum.avast.com/index.php?topic=5719.0

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 76035
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: AIS error 153
« Reply #3 on: January 22, 2012, 10:56:30 AM »
But, I don't know how to provide any data for review - there is no forum option to "attach" (because I don't yet have 20 posts???).

"Attach" is available under "Additional Options", when you create a post.
W8.1 [x64] - Avast Free AV 23.3.8047.BC [UI.757] - Firefox ESR 102.9 [NS/uBO/PB] - Thunderbird 102.9.1
Avast-Tools: Secure Browser 109.0 - Cleanup 23.1 - SecureLine 5.18 - DriverUpdater 23.1 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

ady4um

  • Guest
Re: AIS error 153
« Reply #4 on: January 22, 2012, 04:25:08 PM »
As Asyn mentioned, before you select "post", you have on the left side "Additional Options -> attach".

I don't have a solution, as i don't know what is causing the problem, but...

My guess is that Avast Team is working on avast7 beta. I also assume that, if they were to post here, they would ask for you to make a zip of all the info (including a link to this topic, dumps, logs...) and to upload it to the FTP site. Until they request it, I don't think it is worth to upload it in this case (as they probably are still dealing with avast 7, instead of trying to solve specific issues of avast 6. ). (Note: this is all my guess, and I have no concrete info that this is the case; and I'm not saying that this is acceptable either).

In the meantime, I would suggest 2 actions. One is to use scandisk / checkdisk.

The second suggestion refers to Outlook. In Outlook, there is a function to "compress" the messages (well, the files that represent the "folders" where the messages are stored). I mean, when you delete a message from Outlook, the file behind the email would still be there in the folder. When you "compress" it, Outlook really deletes it. I would suggest preforming this function in Outlook, save, close and reboot. Then test again if the problem persists. In any case, remember first (before the compression) to run scandisk / checkdisk.

As I said, I don't know if this would improve the specific situation, but it shouldn't hurt either.

BTW, have you checked the status of the storage drivers? Are they using DMA or PIO? Are they using AHCI or not? What they are *supposed* to be using (as a comparison to what they are actually using)?

Please report back.

evcox

  • Guest
Re: AIS error 153
« Reply #5 on: January 22, 2012, 08:31:35 PM »
Thanks for the replies. The post referenced by PONDUS is about 8 years old and DavidR had suggested nearly 3 years ago that there was a need for an update. As for other common analysis and maintenance, yes, I have done them. As mentioned, this is not on my personal machine and so I routinely move its drive to one of my computers and check for virus', etc and run a Scandisk (using the old "9x" version as the so-called "error check" within the WindowsXP disk properties seems useless). If the drive appears OK, it goes back on the original machine and I DO check the Device Manager for anomalies and driver problems - including PIO/DMA modes - . I seldom use MSoffice, Outlook/Outlook Express, myself, but am familiar enough to check account properties, etc and to compress folders. Thanks, though, for the suggestions. Since this problem is specific to email antispam, should there be some "rules" created? Avast (AIS) defaults, only, at this time. During the install or repair of AIS, is there an option to NOT include antispam? Thanks.

ady4um

  • Guest
Re: AIS error 153
« Reply #6 on: January 22, 2012, 10:37:17 PM »
Just to be clear, I wasn't talking about compressing folders (meaning, NOT some zip, and NOT some filesystem compression), but about the feature in Outlook itself.

About checking Device Manager storage driver (PIO / DMA, etc.), you must use the original system with the original HDD connected to the original port (and reviewing the original BIOS settings in addition). Connecting the HDD to *another* system and checking the status of the storage drivers there, doesn't mean much.

About using scandisk from Windows 9x on a partition that is used with XP (usually formatted to NTFS), I personally think it is not recommended if the possibility to use the "normal" XP version of scandisk / checkdisk is available. This may even get you into *more* problems.

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37561
  • Not a avast user
Re: AIS error 153
« Reply #7 on: January 22, 2012, 11:25:38 PM »
Quote
Thanks for the replies. The post referenced by PONDUS is about 8 years old
yes it is....but the error codes are the same, only differense is there are a couple of new not on that list but as you see they all begin with 42.....
so the codes you refer to must be windows error codes



here are the new, quote igor
Quote
It's just a few errors for new (corrupted) archives:
40140: ISO
40141: DBX
40142: SIS
40144: OLE
40145: Installer
40147: DMG


« Last Edit: January 22, 2012, 11:29:14 PM by Pondus »

evcox

  • Guest
Re: AIS error 153
« Reply #8 on: January 23, 2012, 01:07:19 AM »
ady4um -- Yes, the PIO/DMA drive access would be more relevant when the HD is connected to my friend's computer and I had stated that was done. Yes, I would prefer to use a version of Scandisk newer than Windows98 but have not found it in WindowsXP. The "error check" available in XP's drive properties or disk management seems of little use (finds few errors and has no user control). The old version does not "see" NTFS so I purpously format most drives to FAT32.
Pondus -- The AsOutExt.log entry is "avast! Antispam encountered an error no. 00000153. Returned code: 80040201". I would have thought that indicated an Avast (AIS) error condition. Also, it seems specifically related to Avast antispam checking. We're willing to live without that feature so, perhaps, I could unregister the DLL ?. Or can I reinstall AIS without the antispam check?. Changing MailShield settings seems to have no effect though I have NOT tried reducing the sensitivity.
Thank you both for your assistance.

evcox

  • Guest
Re: AIS error 153
« Reply #9 on: January 23, 2012, 07:02:29 AM »
ady4um -- sorry, I forgot to include in my previous post that, yes, I DID understand you had meant compressing the Outlook folder and NOT files. This particular friend is not computer savvy and certainly does use email a lot.

BTW -- I was looking over the post from hrova about printing problems when using "Clik to Run" version of MSWord and Excel along with Avast. You had suggested, as a first step, to check his firewall and disable any rules related to his printers, etc. It seemed to me that he kept trying to explain that there were no rules set and, thus there was nothing he could eliminate.

Not wishing to open a can of worms but I'm eager to learn from you and the other helpers here. So, were you trying to say that, even with no boxes "tic'd" or "exceptions" established by a user that the Windows firewall STILL has some kind of rules set??? The firewall never entered my mind as regards MY current problem so I'll have to fire up my friend's machine and look. I suspect, though, that like the one I'm using right now, the firewall will be pure vanilla. Thanks for any clarification.

evcox

  • Guest
Re: AIS error 153
« Reply #10 on: January 23, 2012, 07:58:35 AM »
Well, since this post is being viewed so much, I'm going to try and paste in some EXCERPTS from the AsOutExt.log created the other day when I downloaded a bunch of my friend's email. To keep it shorter, I will include the portion for when Outlook was opened through where the first couple of errors occurred. Then I will skip over the next several errors as all the entries in each group are quite similar. Lastly will be the portion for when I used the Avast toolbar to MANUALLY mark an email as spam through the closing of Outlook. If posting this is inappropriate, I apologise in advance. Perhaps, though, it will give someone a clue as to what is going on.

(Outlook open through first couple errors)
1/21/2012   5:37:19 AM   --- AsOutExt started ---
1/21/2012   5:37:19 AM   9.0.0.2711
1/21/2012   5:37:19 AM   Parsed outlook version:
1/21/2012   5:37:19 AM   9
1/21/2012   5:37:19 AM   Addin version 6.0.1367.0
1/21/2012   5:37:19 AM   DisableOutlookJunkFiltering
1/21/2012   5:37:19 AM   Old outlook - skipped
1/21/2012   5:37:19 AM   OnStartup
1/21/2012   5:37:19 AM   Active Explorer present
1/21/2012   5:37:28 AM   OnSelectionChange (CExplorerWrapper)
1/21/2012   5:37:28 AM   TryCreateToolbar
1/21/2012   5:37:28 AM   CToolbarWrapper(spExplorer)
1/21/2012   5:37:28 AM   CreateGUI
1/21/2012   5:37:28 AM   no bar
1/21/2012   5:37:28 AM   LoadButtonPictureOld1
1/21/2012   5:37:28 AM   PutStyle
1/21/2012   5:37:28 AM   LoadImage
1/21/2012   5:37:28 AM   PutTag
1/21/2012   5:37:28 AM   LoadButtonPictureOld2
1/21/2012   5:37:28 AM   PutStyle
1/21/2012   5:37:28 AM   LoadImage
1/21/2012   5:37:28 AM   PutTag
1/21/2012   5:37:28 AM   LoadButtonPictureOld3
1/21/2012   5:37:28 AM   PutStyle
1/21/2012   5:37:28 AM   LoadImage
1/21/2012   5:37:28 AM   PutTag
1/21/2012   5:37:28 AM   LoadButtonPictureOld4
1/21/2012   5:37:28 AM   PutStyle
1/21/2012   5:37:28 AM   LoadImage
1/21/2012   5:37:28 AM   PutTag
1/21/2012   5:37:28 AM   Bar created
1/21/2012   5:37:28 AM   S_OK
1/21/2012   5:37:28 AM   LoadToolbarPosition
1/21/2012   5:37:29 AM   GetLocalOutboxFolder
1/21/2012   5:37:29 AM   GetRDOSessionFromNamespace
1/21/2012   5:37:29 AM   Old outlook
1/21/2012   5:37:29 AM   ok
1/21/2012   5:37:29 AM   S_OK
1/21/2012   5:37:29 AM   olMail
1/21/2012   5:37:29 AM   GetAvastSpamProperty
1/21/2012   5:37:29 AM   Not marked as spam
1/21/2012   5:37:29 AM   GetLocalJunkFolder
1/21/2012   5:37:29 AM   GetRDOSessionFromNamespace
1/21/2012   5:37:29 AM   Old outlook
1/21/2012   5:37:29 AM   ok
1/21/2012   5:37:29 AM   Default spam folder not found
1/21/2012   5:37:29 AM   Traversing folder to get the root
1/21/2012   5:37:29 AM   QueryInterface failed
1/21/2012   5:37:29 AM   Looking for avast spam folder
1/21/2012   5:37:29 AM   GetJunkFolderStr
1/21/2012   5:37:29 AM   Using custom spam folder
1/21/2012   5:37:29 AM   Not in spam nor outbox folder
1/21/2012   5:37:29 AM   SetSpamButtonEnabled(1)
1/21/2012   5:37:29 AM   SetNotSpamButtonEnabled(0)
1/21/2012   5:37:29 AM   SetSpamAddrButtonEnabled(1)
1/21/2012   5:37:29 AM   SetNotSpamAddrButtonEnabled(0)
1/21/2012   5:41:38 AM   OnSelectionChange (CExplorerWrapper)
1/21/2012   5:41:38 AM   TryCreateToolbar
1/21/2012   5:41:38 AM   GetLocalOutboxFolder
1/21/2012   5:41:38 AM   GetRDOSessionFromNamespace
1/21/2012   5:41:38 AM   Old outlook
1/21/2012   5:41:38 AM   ok
1/21/2012   5:41:38 AM   avast! Antispam encountered an error no. 00000153. Returned code: 80040201
1/21/2012   5:41:38 AM   olMail
1/21/2012   5:41:38 AM   GetAvastSpamProperty
1/21/2012   5:41:38 AM   Not marked as spam
1/21/2012   5:41:38 AM   GetLocalJunkFolder
1/21/2012   5:41:38 AM   GetRDOSessionFromNamespace
1/21/2012   5:41:38 AM   Old outlook
1/21/2012   5:41:38 AM   ok
1/21/2012   5:41:38 AM   Default spam folder not found
1/21/2012   5:41:38 AM   Traversing folder to get the root
1/21/2012   5:41:38 AM   QueryInterface failed
1/21/2012   5:41:38 AM   Looking for avast spam folder
1/21/2012   5:41:38 AM   GetJunkFolderStr
1/21/2012   5:41:38 AM   Using custom spam folder
1/21/2012   5:41:38 AM   Not in spam nor outbox folder
1/21/2012   5:41:38 AM   SetSpamButtonEnabled(1)
1/21/2012   5:41:38 AM   SetNotSpamButtonEnabled(0)
1/21/2012   5:41:38 AM   SetSpamAddrButtonEnabled(1)
1/21/2012   5:41:38 AM   SetNotSpamAddrButtonEnabled(0)
1/21/2012   5:41:59 AM   OnSelectionChange (CExplorerWrapper)
1/21/2012   5:41:59 AM   TryCreateToolbar
1/21/2012   5:42:00 AM   GetLocalOutboxFolder
1/21/2012   5:42:00 AM   GetRDOSessionFromNamespace
1/21/2012   5:42:00 AM   Old outlook
1/21/2012   5:42:00 AM   ok
1/21/2012   5:42:00 AM   avast! Antispam encountered an error no. 00000153. Returned code: 80040201
1/21/2012   5:42:00 AM   olMail
1/21/2012   5:42:00 AM   GetAvastSpamProperty
1/21/2012   5:42:00 AM   Not marked as spam
1/21/2012   5:42:00 AM   GetLocalJunkFolder
1/21/2012   5:42:00 AM   GetRDOSessionFromNamespace
1/21/2012   5:42:00 AM   Old outlook
1/21/2012   5:42:00 AM   ok
1/21/2012   5:42:00 AM   Default spam folder not found
1/21/2012   5:42:00 AM   Traversing folder to get the root
1/21/2012   5:42:00 AM   QueryInterface failed
1/21/2012   5:42:00 AM   Looking for avast spam folder
1/21/2012   5:42:00 AM   GetJunkFolderStr
1/21/2012   5:42:00 AM   Using custom spam folder
1/21/2012   5:42:00 AM   Not in spam nor outbox folder
1/21/2012   5:42:00 AM   SetSpamButtonEnabled(1)
1/21/2012   5:42:00 AM   SetNotSpamButtonEnabled(0)
1/21/2012   5:42:00 AM   SetSpamAddrButtonEnabled(1)
1/21/2012   5:42:00 AM   SetNotSpamAddrButtonEnabled(0)
1/21/2012   5:42:24 AM   OnSelectionChange (CExplorerWrapper)
1/21/2012   5:42:24 AM   TryCreateToolbar
1/21/2012   5:42:24 AM   GetLocalOutboxFolder
1/21/2012   5:42:24 AM   GetRDOSessionFromNamespace
1/21/2012   5:42:24 AM   Old outlook
1/21/2012   5:42:24 AM   ok
1/21/2012   5:42:24 AM   avast! Antispam encountered an error no. 00000153. Returned code: 80040201
1/21/2012   5:42:24 AM   olMail
1/21/2012   5:42:24 AM   GetAvastSpamProperty
1/21/2012   5:42:24 AM   Not marked as spam
1/21/2012   5:42:24 AM   GetLocalJunkFolder
1/21/2012   5:42:24 AM   GetRDOSessionFromNamespace
1/21/2012   5:42:24 AM   Old outlook
1/21/2012   5:42:24 AM   ok

(portion of log file for when I manually marked as spam through to close of Outlook)
1/21/2012   5:59:03 AM   Default spam folder not found
1/21/2012   5:59:03 AM   Traversing folder to get the root
1/21/2012   5:59:03 AM   QueryInterface failed
1/21/2012   5:59:03 AM   Looking for avast spam folder
1/21/2012   5:59:03 AM   GetJunkFolderStr
1/21/2012   5:59:03 AM   Using custom spam folder
1/21/2012   5:59:03 AM   Not in spam nor outbox folder
1/21/2012   5:59:03 AM   SetSpamButtonEnabled(1)
1/21/2012   5:59:03 AM   SetNotSpamButtonEnabled(0)
1/21/2012   5:59:03 AM   SetSpamAddrButtonEnabled(1)
1/21/2012   5:59:03 AM   SetNotSpamAddrButtonEnabled(0)
1/21/2012   5:59:05 AM   OnSpamButtonClick
1/21/2012   5:59:05 AM   Handling an spButton event
1/21/2012   5:59:05 AM   Explorer handler
1/21/2012   5:59:05 AM   MarkSubjectAsSpam
1/21/2012   5:59:05 AM   SetAvastSpamProperty
1/21/2012   5:59:05 AM   Setting avast spam property
1/21/2012   5:59:05 AM   done
1/21/2012   5:59:05 AM   GetSpamSubjectPrefix
1/21/2012   5:59:05 AM   *** SPAM ***
1/21/2012   5:59:05 AM   Adding spam prefix
1/21/2012   5:59:05 AM   *** SPAM ***Save up to 50Off! Plus FREE* Shipping!
1/21/2012   5:59:05 AM   put_Subject
1/21/2012   5:59:05 AM   Save
1/21/2012   5:59:05 AM   saved
1/21/2012   5:59:05 AM   GetLocalJunkFolder
1/21/2012   5:59:05 AM   Releasing Junkfolder
1/21/2012   5:59:05 AM   GetRDOSessionFromNamespace
1/21/2012   5:59:05 AM   Old outlook
1/21/2012   5:59:05 AM   ok
1/21/2012   5:59:05 AM   Default spam folder not found
1/21/2012   5:59:05 AM   Traversing folder to get the root
1/21/2012   5:59:05 AM   QueryInterface failed
1/21/2012   5:59:05 AM   Looking for avast spam folder
1/21/2012   5:59:05 AM   GetJunkFolderStr
1/21/2012   5:59:05 AM   Using custom spam folder
1/21/2012   5:59:05 AM   MoveMailItemToFolder
1/21/2012   5:59:05 AM   GetRDOSessionFromNamespace
1/21/2012   5:59:05 AM   Old outlook
1/21/2012   5:59:05 AM   ok
1/21/2012   5:59:05 AM   avast! Antispam encountered an error no. 00000115. Returned code: 80040201
1/21/2012   5:59:52 AM   OnExplorerClose
1/21/2012   5:59:52 AM   SaveToolbarPosition
1/21/2012   5:59:52 AM   DestroyGUI
1/21/2012   5:59:52 AM   ~CToolbarWrapper
1/21/2012   5:59:52 AM   cleanup
1/21/2012   5:59:52 AM   Unhooking app event handlers
1/21/2012   5:59:52 AM   Unhooking other event handlers
1/21/2012   5:59:52 AM   Event handlers unhooked
1/21/2012   5:59:58 AM   OnDisconnection
1/21/2012   5:59:58 AM   cleanup
1/21/2012   5:59:58 AM   --- AsOutExt stopped ---

I had previously asked if Avast (paid AIS) can be reinstalled WITHOUT the antispam feature.
Thank you and waiting for suggestions.

ady4um

  • Guest
Re: AIS error 153
« Reply #11 on: January 23, 2012, 05:20:12 PM »
I don't know if the spam filter is relevant to the error messages. Avast can be "partially" (un)installed, and so some shields / modules / components are not installed at all.

I think the problem requires some input from Avast Team developers. All other input is just speculation (even if there could be some partial feedback from common users, it won't truly answer the main question here).

IMHO, you have a couple of basic possibilities. You could wait for some developer to come here to help you (and there is no way for us, common users, to know when they would do it, specially while they are currently focused on avast 7 beta).

The other possibility is to save a copy of all the relevant info (dumps, logs, errors, reports, Windows event issues, avast license file,...) and uninstall avast. After the normal uninstall, run the removal utility several times with reboots in between. For each run, you select each version of avast ever installed (or updated to) in that system. http://www.avast.com/uninstall-utility

You could even go beyond the removal utility. After running it several times as described, you could manually search for any (hidden) folder with "avast*" or "alwil*" in its name, and delete it.

Then you could install the latest stable version of avast. If you (or your friend, actually) have AIS, then download AIS TRIAL. Install it, reboot and test it. If it works, then use the copy of your license file (remember above?) to transform the trial into a registered version.

The problem with this option is that it erases all previous traces of the problem, without giving you any indication that the problem will be solved after the clean install, and the developers will have less info available to solve it (hence, I strongly suggest backups of the relevant info, and of the emails and contacts in Outlook).

There is a third "middle ground" possibility. You could wait some more days for an Avast developer to post here, while you wait for avast 7 (instead of reinstalling avast 6 ). It will get out as beta first, and I can't assure you that an avast developer will actually look into this (they should, as a paying customer). Avast 7 (either beta or final gold) "could", potentially, also solve the problem, but as already said, we common users are not in position of helping you (the specific error you get is not listed nor explained.

In any case, you should open a bug ticket report at http://support.avast.com/index.php?_m=tickets&_a=submit.

evcox

  • Guest
Re: AIS error 153
« Reply #12 on: January 23, 2012, 08:23:00 PM »
ady4um -- Thanks. We'll give your suggestions some thought and decide which way forward. In any event, I will make and keep a complete copy of her drive. After clearing all current traces of Avast, I'll try an installation minus the spam feature. If that keeps those dump files from being generated, we can live with it. Or she can just periodically delete them until such time as more assistance becomes available.

I've been learning much from browsing the forum. You folks have mentioned many user procedures and software solutions that I had forgotten or never knew. Thanks again.