Tech Support > Microsoft Windows > Windows CRM > Outlook 2007 client for Vista doesn't install
Outlook 2007 client for Vista doesn't install
Posted by Kumar on May 6th, 2008


I am having trouble getting the Outlook 2007 client (online only) for Vista
to install.

During installation, the verification step says that there is a pending
computer restart. I'm sure that this is not the case, since I had not
installed any software or updates since last restarting. Should I perhaps
restart immediately prior to installing the client? And after the
installation is complete?

I did neither and just started Outlook. A dialog appearing saying that
there is an error loading CRM functionality and to try restarting Outlook. I
did that twice and the same error occurred both times. The "Microsoft CRM"
data file only contained a Deleted Items folder during this time.

Then I decided to remove that data file, which worked without error. I then
removed the CRM add-in from Outlook, which also worked without error. Then I
added the CRM add-in again, which worked without error. Then I tried to add
a data file of type "Microsoft CRM" and immediately got the following: "An
unknown error occurred, error code: 0x80040102.

I looked in the folder "C:\Users\{user-me}\AppData\Local\Microsoft\Outlook"
and saw no file containing anything remotely resembling the word "CRM".
Shouldn't there be a CRM data file in there? If so, can I start with some
sort of default, empty data file and go from there?

Posted by Kumar on May 6th, 2008


I should add that I have SP1 for Office 2007 Ultimate, SP1 for Vista and I
want to install the CRM 3.0 client.

"Kumar" wrote:

Posted by Frank Lee on May 6th, 2008


Which CRM 3.0 Client version are you using? Ensure that it is V3C - which
supports Office 2007 and Vista:

Link for more details:
http://microsoft-crm.spaces.live.com...C065!192.entry

Frank Lee, Microsoft Dynamics CRM MVP
http://microsoft-crm.spaces.live.com
http://www.workopia.com/Links.htm

"Kumar" wrote:

Posted by Kumar on May 6th, 2008


I am using what I thought to be the Vista-and-Outlook-2007-compatible client.
However, I opened the Readme in the client's installation directory and I
found that it is dated December 2006. Does this mean that this is not the
V3C edition?

The article you linked uses the word "On-premise". What does that mean?

"Frank Lee" wrote:

Posted by Frank Lee on May 6th, 2008


You can check the setup.exe properties - Product version: 3.0.5300.1361 or
download via:
https://www.microsoft.com/downloads/...DisplayLang=en

On Premise - usually means the Software is installed locally vs. someone
hosting it.


Frank Lee, Microsoft Dynamics CRM MVP
http://microsoft-crm.spaces.live.com
http://www.workopia.com/Links.htm

"Kumar" wrote:

Posted by Kumar on May 7th, 2008


The setup.exe I had used the first time was the correct (V3C) version. In
any case, I downloaded it again, burned it to CD and installed, but I got
exactly the same error.

There is still no CRM data file in the
"C:\Users\{user}\AppData\Roaming\Microsoft\Outlook " directory. Where is the
CRM data file usually located?

I hesitate to install the Update Rollup 2 or 3 because 2 is not uninstallable.

Does anyone really know what is going on here, or will I just need to keep
applying patches and updates without knowing the CAUSE of the problem?


"Frank Lee" wrote:

Posted by Kumar on May 7th, 2008


I also looked in Event Viewer and saw this entry:
"Initialization of the Microsoft CRM UI failed. Try restarting Microsoft
Outlook. HR=0x80040154. Context=. Function=CAddin::HrActivateAddin. Line=521."

"Kumar" wrote:

Posted by Frank Lee on May 7th, 2008


Here is how I would approch it:

1. Setup a baseline PC and see if this is just affecting that PC or others

2. Submit a support case to help isolate the issue


Frank Lee, Microsoft Dynamics CRM MVP
http://microsoft-crm.spaces.live.com
http://www.workopia.com/Links.htm

"Kumar" wrote:

Posted by Kumar on May 15th, 2008


I updated MSXML to version 4.0 SP2 and CRM now works perfectly. I found this
out by googling the initial error message and seeing that someone else solved
the problem that way. Here is the link to the update:

http://support.microsoft.com/kb/927751


"Frank Lee" wrote: