An issue with Windows Live Local for Outlook and MS CRM for Outlook client

I got the following email last night about an issue with Windows Live Local for Outlook and MS CRM for Outlook client.

I looked in the Windows Live Local for Outlook Readme file to see if this was mentioned, but there was nothing there.

I've spent a while looking for a way to contact someone who can assist, and have failed, SO if anyone from the product team (either on the Live Local for Outlook team or the MS CRM team) is watching - drop Stephen a line.

-----Original Message-----
From: stephen.friend AT
Sent: Wednesday, 21 June 2006 6:06 PM
To: Frank Arrigo
Subject: (frankarr - an aussie microsoft blogger) : Windows Live Local for Outlook....
Importance: High

Windows Live Local for Outlook

Not sure where to post this, but saw your posting recently on this product...

Just to let you know that the new Live Local addin has serious issues co-existing with the Microsoft CRM for Outlook client.

We have found after installing the new addin on machines running both the Laptop and Desktop CRM clients, we would get a lot of "There is a problem communicating with the Microsft CRM Server" errors and would also find that appointments that where linked in CRM (Track in CRM) would lose their link although the appointment synchronised and existed in Microsoft CRM as expected.

We have ended up uninstalling this addin and found now that all of the Microsoft CRM appointments are still correctly linked.

Appreciate it if you could please pass this on..

Any feedback to stephen.friend AT would be appreciated.


Comments (4)
  1. Maybe I can shed some light on this. I have reported this to the product team and have not heard anything back.

    Windows Live Local add-in for Outlook forces .NET 1.1 into the Outlook process. If the new MS CRM is using .NET 2.0 for its Outlook integration, then it will be broken by LEO.

    I have no idea if that is the same problem Stephen is seeing, but it is a problem that I encountered. He can try putting an outlook.exe.config file in Outlook’s installation directory with a <supportedRuntime> tag specifying 2.0.50727.

    It’s doubly frustrating for me because not only did they copy the feature idea from my product, but the bug actually disables my add-in, TEO, which relies on .NET 2.0.

  2. Hi there Frank…. I’ll take a look at this one for you and see what the problem might be.

  3. jbarbieri says:

    How do I uninstall this?

Comments are closed.

Skip to main content