C
Chad Harris
On XP Pro SP2 box dual booting with a still congenitally broken Vista whose
SFC can trash the reg, System Restore cannot manufacture Restore Points, and
UAC threatens to be the next pandemic to panic the world. Off hand, I'd bet
that Steve Hiskey, Lead Program Maanager for UAC will take some heat for
this because despite all the regedits, and secpol.msc Run as admin tricks,
people are going to be beating a path to msconfig and disabling UAC in
droves (defeating its purpose)--or at least while they try to install or get
into folders they can't or else getting in touch with their inner parent
child take permissions and security tab in ways they never knew they could.
http://blogs.msdn.com/uac/
But to Outlook's problem which is the reason for posting here:
I have no trouble loading OL 2007 Beta 2 with Vista, but on my XP boot, I
get the multiplying refusing to die in your face
error message, "Managed MAPI Service Catastrophic Failure"-- Could not load
file or assembly CLR 'Iris.Mapi.Message.Store' or one of its dependancies."
The system cannot find the file specified.
This is remeniscent of a problem I had with OL 2003 with BCM because BCM
didn't in that version want to play with .net Framework 2.0. I don't know
what the situation is to have the right setup for OL 2007 on XP, but it is
necessary for me to have .net framework 2.0 for Windows One Care.
Why am I not shocked if this is the case--I know Patricia Cordoza has had a
BCM site up for some time--that if Windows One Care Live's requirement for
for .net framework 2.0 conflicts with OL 2007 these teams couldn't
communicate way prior to now and resolve this issue. I'll ck Patricia's
site and see if she has anything on this.
I followe Sue's directions here:
http://www.pcreview.co.uk/forums/thread-1858724.php
If you don't see the Business Tools menu, BCM probably failed to load when
Outlook started. Run Regedit and go to the
HKLM\Software\Microsoft\Office\Outlook\Addins\Micr
osoft.BusinessSolutions.eCRM.OutlookAddin.Connect. 1
key. If the value for LoadBehavior is something other than 3, make a backup
of the registry, edit LoadBehavior to set it to 3, then restart Outlook. You
can also check Help | About Microsoft Outlook | Disabled Items.
I don't see the path to disabled items in OL 2007 I know is in OL 2003.
Running the Diagnostic Service in 2007 produced nothing.
--
I have read Norton can cause this problem as just one of its panopoly of
endless conflicts with OE and OL, but the day I began with One Care, I
kicked Norton to the curb never to return.
I saw at the end of her post that Sue recommended a Support episode, and
this is a Beta but I'm sure this error occured in Office 2003 although I
never saw it with that and I don't see this problem with Vista and OL 07.
As I think Sue and Patricia and I'll bet Diane Poremsky and the Divine Ms.
Staples are aware, MSFT PSS sub-enterprise is an absolute joke for the main
reason that some accountant non-software engineer at MSFT who calls this
shot outsources PSS to Convergys of Ohio in India minimum wage butts in
seats who 1) Don't know jack about Windows 2) Don't know jack about Office
3) According to my Inidian next door neighbor who grew up here can't speak
English worth a damn.
It's interesting that the NY Times this morning had a front page Business
Page article that Dell slipping in sales chose to spend $100 million on
Support in order to make changes fast. It's clear that as Mr. Gates eases
out from day to day duties, Ballmer and Sinofsky are not about to change
this totally worthless PSS situation for anyone below enterprise level nor
or the support personnel in Dallas who supervise North American support able
to make any changes.
Any suggestions for fixing this would be appreciated.
Ha! As I speak having made the regedit five minutes ago, suddenly these
multiplying error boxes in my face reminding me of the movie classic
"Invasion of the Body Snatchers" have vanished. Maybe it was because I
needed to remember Newton's 3rd Law of Outlook which is that these fixes
only work if you are typing the names Mosher, Cordoza, Staples, and Poremsky
while you do the regedit.
Thanks,
CH
SFC can trash the reg, System Restore cannot manufacture Restore Points, and
UAC threatens to be the next pandemic to panic the world. Off hand, I'd bet
that Steve Hiskey, Lead Program Maanager for UAC will take some heat for
this because despite all the regedits, and secpol.msc Run as admin tricks,
people are going to be beating a path to msconfig and disabling UAC in
droves (defeating its purpose)--or at least while they try to install or get
into folders they can't or else getting in touch with their inner parent
child take permissions and security tab in ways they never knew they could.
http://blogs.msdn.com/uac/
But to Outlook's problem which is the reason for posting here:
I have no trouble loading OL 2007 Beta 2 with Vista, but on my XP boot, I
get the multiplying refusing to die in your face
error message, "Managed MAPI Service Catastrophic Failure"-- Could not load
file or assembly CLR 'Iris.Mapi.Message.Store' or one of its dependancies."
The system cannot find the file specified.
This is remeniscent of a problem I had with OL 2003 with BCM because BCM
didn't in that version want to play with .net Framework 2.0. I don't know
what the situation is to have the right setup for OL 2007 on XP, but it is
necessary for me to have .net framework 2.0 for Windows One Care.
Why am I not shocked if this is the case--I know Patricia Cordoza has had a
BCM site up for some time--that if Windows One Care Live's requirement for
for .net framework 2.0 conflicts with OL 2007 these teams couldn't
communicate way prior to now and resolve this issue. I'll ck Patricia's
site and see if she has anything on this.
I followe Sue's directions here:
http://www.pcreview.co.uk/forums/thread-1858724.php
If you don't see the Business Tools menu, BCM probably failed to load when
Outlook started. Run Regedit and go to the
HKLM\Software\Microsoft\Office\Outlook\Addins\Micr
osoft.BusinessSolutions.eCRM.OutlookAddin.Connect. 1
key. If the value for LoadBehavior is something other than 3, make a backup
of the registry, edit LoadBehavior to set it to 3, then restart Outlook. You
can also check Help | About Microsoft Outlook | Disabled Items.
I don't see the path to disabled items in OL 2007 I know is in OL 2003.
Running the Diagnostic Service in 2007 produced nothing.
--
I have read Norton can cause this problem as just one of its panopoly of
endless conflicts with OE and OL, but the day I began with One Care, I
kicked Norton to the curb never to return.
I saw at the end of her post that Sue recommended a Support episode, and
this is a Beta but I'm sure this error occured in Office 2003 although I
never saw it with that and I don't see this problem with Vista and OL 07.
As I think Sue and Patricia and I'll bet Diane Poremsky and the Divine Ms.
Staples are aware, MSFT PSS sub-enterprise is an absolute joke for the main
reason that some accountant non-software engineer at MSFT who calls this
shot outsources PSS to Convergys of Ohio in India minimum wage butts in
seats who 1) Don't know jack about Windows 2) Don't know jack about Office
3) According to my Inidian next door neighbor who grew up here can't speak
English worth a damn.
It's interesting that the NY Times this morning had a front page Business
Page article that Dell slipping in sales chose to spend $100 million on
Support in order to make changes fast. It's clear that as Mr. Gates eases
out from day to day duties, Ballmer and Sinofsky are not about to change
this totally worthless PSS situation for anyone below enterprise level nor
or the support personnel in Dallas who supervise North American support able
to make any changes.
Any suggestions for fixing this would be appreciated.
Ha! As I speak having made the regedit five minutes ago, suddenly these
multiplying error boxes in my face reminding me of the movie classic
"Invasion of the Body Snatchers" have vanished. Maybe it was because I
needed to remember Newton's 3rd Law of Outlook which is that these fixes
only work if you are typing the names Mosher, Cordoza, Staples, and Poremsky
while you do the regedit.
Thanks,
CH