Sue Mosher: Nuking System 32\IrisM32.dll. cures my Mapi Catastropic Error

[Chad Harris]

Sue--

The culprit for me was C:\Windows\System 32\IrisM32.dll which is directly
associated with BCM 2003.

1) I used to have BCM 2003 in Add/Remove and it wouldn't remove. Finally it
disappeared. I am not sure however if uninstalling Office 2003 had any
impact on this, because in order to get in Outlook 2007 of course, I had to
uninstall Outlook 2003 in the first place. I realized this when Outlook
2007 would not install so I selectively uninstalled OL 2003 and reinstalled
Outlook 2007 with no trouble.

I had uninstalled Office 2003 which I had in concomitantly with Office 2007
(for comparison purposes) after your message. When I went looking for BCM
2003's files, .dlls I couldn't find them in the Office folders, and I had
used the Windows Installer Cleanup Utility. When I installed the Office
2007 trial it does not contain BCM in its Office plus package, although they
do offer it as a Beta separately according to the listings of Beta 2007
installs from the Office site.

I posted some addiitional info in a folloup to you back in June,

Finally after being able to use Outlook but getting these IMAPI IRIS
catastropic failure boxes in my face about 16 at a time since I posted on
6/16 (I could kill them but any folder Inbox, ect. calendar--essentially
anything I tried to open in Outlook would bring them back in force.

The best analogy I can make is they reminded me very much of a spyware box
that keeps popping up and won't quit.

After many googles and reading many associations of this with anything from
Norton often to Quick Books, and several other 3rd party apps, I found an
association of this with C:\Windows\System 32\IrisM32.dll. After checking
the properties of this .dll , and seeing that it was associated with BCM
2003, (and since I had no need for that and you suggested that obviously BCM
any component 2003 was likely to cause problems with BCM 2007and setting a
restore point just in case, I deleted it and the problem vanished.

So for me Sue, nuking that .dll did the trick for what it's worth. I would
extend this premise that in my experience any component or remnant of BCM
2003 does not play well with Office 2007 because unless there are shared
..dlls that you or Patricia or others may know about with BCM 2007, the
Office Plus 2007 that MSFT is offering for Beta public use does not contain
BCM 2007. You have to download and install that separately from their Beta
offerings.

Thanks for your help and patience.

Chad Harris

 

[Sue Mosher [MVP-Outlook]]

Thanks for sharing this!

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Chad Harris]

Sue--

At first thought it seems to be a .dll tailored to using with BCM only--I'll
have to research this further--because with .dlls I'm never sure they can't
be shared--but all my Office apps seem to be working fine and I just put
Outlook through a number of its "features paces and no problems at all."
This would suggest that when Office 2003 was uninstalled, that this .dll
should have gone with it but was left behind. I'm always left with the
impression of Add/Remove programs as a work in progress and not always a
clean, complete remover. That's why there are a number of manual installs
associated with Antiviral programs, and possibily could be needed with some
Office apps. I don't know how often Outlook or BCM needs to be manually
uninstalled.

I also got help from my idea from this post after googling "iriis MAPI
message store catastropic failure."
http://www.pcreview.co.uk/forums/thread-1859085.php

Also I realized I didn't have this "IMAPI message catastropic failure box"
problem on Vista--and that's consistent with this since I had never
installed BCM 2003 onto Vista--just onto my XP boot.

I'm thinking that BCM older remnants would not only conflict with a newer
version of BCM--particularly if they had key functionality, but also with
another Version of Office or at least it's Beta even if a newer BCM weren't
part of the newer Office version as in this situation.

CH


Thanks for sharing this!

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

It's definitely a BCM .dll. Bottom line: Remove BCM before installing Outlook 2007.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Chad Harris]

Yes of course--I got into trouble when I kept Office 2003 not because of
keeping two versions of Office, but because you have to make sure you have
every file and .dll associated with BCM 03 uninstalled before you bring in
Office 2007 and one that hung around even after an uninstall caused that
jam.

Office 2007 and Office 2003 will keep previous apps easily in setup if you
want no problem there. However, the big asterisk is BCM. Office 2007
wouldn't install Outlook 2003 of course because one Outlook only can exist.
At that point with Outlook 2007 and Outlook 2003 with BCM there were no
problems. When I realized I had forgotten I had to get rid of OL 03 to get
in OL 07 and I did uninstall OL O3 which should have taken care of BCM 03,
it obviously didn't get at least one key.dll that spelled trouble later. I
used Add Remove to selectively uninstall OL O3 and then OL 07 installed
(although it wouldn't let me install stand alone OL 07 that MSFT offers as a
Beta as well. It made me uninstall OL 07 and reinstall it all over again.

Interesting, (a little though), that at the point that OL 07 wasn't in yet,
but Office 2007 and OL 03 with BCM were in, OL O3 with BCM was working just
fine. The hassle began when I installed OL 07 and a remnant or .dll from
BCM 03 didn't like that at all. The culprit was apparently the \System 32
IrisM32.dll that got left behind.

From now on I'll be more sensitive to checking for it should BCM any version
be on a box.

Thanks,

CH

but I tried Sue by conventional means which was to remove Office 2003. "Sue
It's definitely a BCM .dll. Bottom line: Remove BCM before installing
Outlook 2007.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

I did uninstall OL O3 which should have taken care of BCM 03,

That was my point for anyone else running into this issue. BCM is a separate application. Removing Outlook 2003 does not remove BCM.

FWIW, creating a new mail profile that didn't include the BCM data store might also have resolved the problem. Creating a new mail profile is always a good, nondestructive first troubleshooting step.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers