Seen a few similar issues but no response yet. Whenever anything "BCM" is
opened in Outlook (open an Account, a BCM-specific contact), Outlook crashes
and error reporting dialog is displayed. Can't recall what's in the dump but
I think it's mso.dll. At the time, no Googling of the error/.dll returned
anything meaningful.

On another machine, it works fine. Both are using a shared SQL 2005 Express
database on a SBS 2003 server.

I tried logging in using a different profile on the machine in question (as
domain administrator), and BCM works fine. However, repairing Office/Outlook
and reinstalling does not resolve the issue with the one profile, which makes
me think that something unsavory is being left behind in the profile even
after reinstalling (something in doc...settings/%userprofile%/App...Data
maybe?).

I really don't want to have to blow away the domain user's profile and
reinstall all his applications so I was thinking of running the Microsoft
Installer Cleanup Utility after uninstalling Office and trying again. Anyone
have any suggestions?

Thanks

Gravyface

So nice to find someone with the same problem. I have the same problem as
you describe here.

Unfortunately I don't have answers :-(
Have you managed to overcome the problem?

Please advise if you have.

Many thanks
Nigel
"gravyface" wrote:

> Seen a few similar issues but no response yet. Whenever anything "BCM" is
> opened in Outlook (open an Account, a BCM-specific contact), Outlook crashes
> and error reporting dialog is displayed. Can't recall what's in the dump but
> I think it's mso.dll. At the time, no Googling of the error/.dll returned
> anything meaningful.
>
> On another machine, it works fine. Both are using a shared SQL 2005 Express
> database on a SBS 2003 server.
>
> I tried logging in using a different profile on the machine in question (as
> domain administrator), and BCM works fine. However, repairing Office/Outlook
> and reinstalling does not resolve the issue with the one profile, which makes
> me think that something unsavory is being left behind in the profile even
> after reinstalling (something in doc...settings/%userprofile%/App...Data
> maybe?).
>
> I really don't want to have to blow away the domain user's profile and
> reinstall all his applications so I was thinking of running the Microsoft
> Installer Cleanup Utility after uninstalling Office and trying again. Anyone
> have any suggestions?
>
> Thanks

On Nov 29, 10:06 am, Nigel-70 <Nigel...@discussions.microsoft.com>
wrote:
> Gravyface
>
> So nice to find someone with the same problem. I have the same problem as
> you describe here.
>
> Unfortunately I don't have answers :-(
> Have you managed to overcome the problem?
>
> Please advise if you have.
>
> Many thanks
> Nigel
>
>
>
> "gravyface" wrote:
> > Seen a few similar issues but no response yet. Whenever anything "BCM" is
> > opened in Outlook (open an Account, a BCM-specific contact), Outlook crashes
> > and error reporting dialog is displayed. Can't recall what's in the dump but
> > I think it's mso.dll. At the time, no Googling of the error/.dll returned
> > anything meaningful.
>
> > On another machine, it works fine. Both are using a shared SQL 2005 Express
> > database on a SBS 2003 server.
>
> > I tried logging in using a different profile on the machine in question (as
> > domain administrator), and BCM works fine. However, repairing Office/Outlook
> > and reinstalling does not resolve the issue with the one profile, which makes
> > me think that something unsavory is being left behind in the profile even
> > after reinstalling (something in doc...settings/%userprofile%/App...Data
> > maybe?).
>
> > I really don't want to have to blow away the domain user's profile and
> > reinstall all his applications so I was thinking of running the Microsoft
> > Installer Cleanup Utility after uninstalling Office and trying again. Anyone
> > have any suggestions?
>
> > Thanks- Hide quoted text -
>
> - Show quoted text -

If user A installs BCM, user B uses BCM, and user A uninstalls BCM,
then BCM will not get removed from user A's profile. Thats a problem,
but there are security reasons why you don't want user A tampering
with user B's data.

That said, user B can manually remove BCM from their profile using the
Control Panel Mail applet. Then they can create a new BCM store in
their mail profile and see if that resolves their problem.

Note that a mail profile is specific to Outlook and not Windows, so a
user can delete their mail profile, without having to create a new
Windows user or reinstall all their software.