Update Rollup 4 for Microsoft Dynamics CRM 4.0

Home rss feed email us Microsoft Dynamics CRM website

Update Rollup 4 for Microsoft Dynamics CRM 4.0

crmblog

14 May 2009 10:28 AM

Comments 31

The Microsoft Dynamics CRM Sustained Engineering team released Microsoft Dynamics CRM 4.0 Update Rollup 4 on Thursday, May 7, 2009.

Below are the links to the release and related information about the Rollup. Please see the Knowledge Base (KB) article for more details about the Update Rollup 4 content and instructions.

Microsoft Download Center: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0ddf8e83-5d9c-4fe7-9ae6-f2713a024071
Microsoft Knowledge Base Article: http://support.microsoft.com/?kbid=968176

Install Details about Update Rollup 4

Update Rollup 1, Update Rollup 2 and Update Rollup 3 are not prerequisites for installing Update Rollup 4
The Update Rollup 4 client can be deployed before the server is upgraded to Update Rollup 4
Update Rollup 4 can be uninstalled

How to avoid a required reboot when installing a patch for the CRM Outlook Client

Before starting the update process, go to Options from the CRM menu. On the “General” tab, uncheck the bottom checkbox that says “Always run the…Host process” and then click “Ok” button.
When manually checking for updates, go ahead and close Outlook by choosing Exit from Outlook’s File menu. This will close Outlook along with the CRM add-in and the Hoster process.
Now check for updates by selecting All Programs from the Start menu. Then select Microsoft Dynamics CRM 4.0 and choose Update.
Restart Outlook after the patch is installed.

Note: If the user doesn’t want to make the permanent change of always having the Hoster process exit when Outlook exits, they can close the Hoster process manually after Outlook has been closed by right clicking on the Dynamics icon in the Notification Area of the Task Bar.

Making Update Rollup 4 available to your clients via AutoUpdate

You can find more information about AutoUpdate in Eric Newell’s blog entry at http://blogs.msdn.com/crm/archive/2008/05/08/crm-client-autoupdate.aspx and the Microsoft Dynamics CRM 4.0 Operating and Maintaining Guide, part of the Microsoft Dynamics CRM 4.0 Implementation Guide.

If you have a direct internet connection from your client machines, you can avoid some of the configuration steps and use the LinkId directly. Below are the necessary steps to configure the AutoUpdate for Update Rollup 4.

Note: These are steps 5, 6 and 7 of Eric’s blog.

Steps for the English version of the product

The PatchId and LinkId values will be different for every localized version of CRM 4.0. The IDs can be found in the KB article at http://support.microsoft.com/?kbid=968176.

1. Create the configuration XML file and save it.

        1: <ClientPatches>

       2:     <Create>

       3:         <!--- *** UR4 PATCH -->

       4:         <ClientPatchInfo>

       5:             <!--- *** The PatchId is different for every Language.  Please see the KB Article at http://support.microsoft.com/?kbid=968176 for correct Patch ID to use -->

       6:             <PatchId>{004A7E60-5DB7-4F05-B7C1-1D2DD653A1A6}</PatchId>

       7:             <Title>Update Rollup 4 for Microsoft Dynamics CRM 4.0 (KB 968176)</Title>

       8:             <Description>Update Rollup 4 for Microsoft Dynamics CRM 4.0 (KB 961768)</Description>

       9:             <!--- *** This will make it Mandatory -->

      10:             <IsMandatory>true</IsMandatory>

      11:             <IsEnabled>true</IsEnabled>

      12:             <ClientType>OutlookLaptop, OutlookDesktop</ClientType>

      13:             <!--- *** The LinkId is different for every Language.  Please see the KB Article at http://support.microsoft.com/?kbid=968176 for correct Link ID to use -->

      14:             <!-- & in xml documents must be escaped using &amp; -->

      15:             <LinkId>150735&amp;clcid=0x409</LinkId>

      16:         </ClientPatchInfo>

      17:     </Create>

      18: </ClientPatches>

2. From the command prompt, go to the directory where the ClientPatchConfigurator.exe is located ([ServerInstallDir]\Tools and type microsoft.crm.tools.clientpatchconfigurator.exe [configfile].xml

3. Once the patch has been uploaded, launch the Outlook client

The dialog should now appear saying that “Update Rollup 4 for Microsoft Dynamics CRM 4.0 (KB 968176)” is available. If the <IsMandatory> is set to false, the client will only see the update if the user selects “Check for Updates” via the CRM Menu in the Outlook client.

Cheers,

Matt Brown

Link and Patch IDs for Update Rollup 4 are now part of the KB article. Please see http://support.microsoft.com/?kbid=968176 for more details.

Announcement, CRM4, Updates, Code

Comments

Andreas

15 May 2009 1:32 AM

Hello CRM Team,

after installing UR3 there was a problem with double spacing on our published workflow email templates. This problem was also metioned in the comments of the UR3 post.

The answer was, that it will be fixed in UR4. But after installing UR4, we still have the problem.

Greetings, Andreas
Matt Brown

15 May 2009 7:06 PM

The workflow line feed issue is still being worked on by our sustained engineering team and is targeted to UR5. We also plan to release it as a Critical on Demand (COD) hotfix prior to the UR5 release since it is an issue caused by a previous rollup. I do not have a specific date for the COD but expect it will be in the next 7-10 days. The COD will be available via support when ready. If you contact support, you can reference KB 971355. That kb is not yet published but will be the KB documenting the issue.

Thanks,

Matt
Andreas

19 May 2009 8:21 AM

Thanks for your fast answer Matt.

Greetings, Andreas
Andy

20 May 2009 2:27 PM

After installing UR4 on our terminal server (64-bit server 2008 running Office 2007) the outlook client would stall and hang up for all users attempting to open, reply, open calendar, or just about any action in Outlook. Uninstalling UR4 resolved the problem Are there actions to take on a terminal server after installing rollup to not have these hangups/lockups happen?
Michael

21 May 2009 6:28 AM

I'm perplexed. All indications are that the rollups don't require prereqs, so you can install the base Outlook Client then rollup4 and your done - yes?

Well, if that's the case, then why are the client rollups so different in size...

Client Rollup 1: 76mb

Client Rollup 2: 4.4mb

Client Rollup 3: 5.2mb

Client Rollup 4: 22.1mb

Surely if each rollup contained all subsequent fixes AND the new fixes you would expect the rollup size to keep increasing. Ok, you can say that there is some duplication as some identical files are updated in subsequent packages but not to such a massive extent.

Any ideas?
Phil Edry

21 May 2009 6:25 PM

Michael,

Rollup 1 included the rollups for all languages, so that's party why it was so large. Rollups 2-4 have independent releases for each language.
Nick

22 May 2009 9:06 AM

Matt,

We have the same problem. Do you have any update on a fix date for this and if no, how can I find out when it will be released?
Carsten

22 May 2009 12:51 PM

I´ve seen some trouble installing UR4 for outlook desktop clients. First you´re asked for "client.msi". Giving the correct path to this package the next error message is a missing path/files. Looking deeper into this, these files are only installed, if you´re using the laptop (offline) client, but not when you´ve installed the outlook client.
Morten

25 May 2009 6:46 AM

I have the same problem as Carsten. Any help would be appreciated.
Doug - PowerObjects

26 May 2009 12:13 PM

I've configured rollup 4 to be distributed via the AutoUpdate function, and I've done so with the other rolls ups as well. However, rollup 4 is giving me problems. I'm getting thef ollowing error:

11:45:59| Info| === Managed setup logging started: 5/19/2009 11:45:59 AM ===

11:45:59|Verbose| Method entry: Microsoft.Crm.UpdateWrapper.UpdateSetup.Initialize

11:45:59|Verbose| Method entry: Microsoft.Crm.Setup.Common.SetupBase.Initialize

11:45:59|Verbose| Method exit: Microsoft.Crm.Setup.Common.SetupBase.Initialize

11:45:59|Verbose| Method exit: Microsoft.Crm.UpdateWrapper.UpdateSetup.Initialize

11:45:59|Verbose| Method entry: Microsoft.Crm.UpdateWrapper.UpdateSetup.Run

11:45:59|Warning| The specified /config file config.xml won't be used

11:45:59|Verbose| Method entry: Microsoft.Crm.Setup.Common.SetupBase.Run

11:45:59|Verbose| Method exit: Microsoft.Crm.Setup.Common.SetupBase.Run

11:45:59|Verbose| Method entry: Microsoft.Crm.UpdateWrapper.UpdateSetup.VerifyRequiredKBsAreInstalled

11:45:59|Verbose| Method exit: Microsoft.Crm.UpdateWrapper.UpdateSetup.VerifyRequiredKBsAreInstalled

11:45:59| Info| InstallInfo.AdminTargetFolder:

11:45:59| Info| InstallInfo.AllowRun: True

11:45:59| Info| InstallInfo.CleanupRequired: False

11:45:59| Info| InstallInfo.ConfigFile: config.xml

11:45:59| Info| InstallInfo.CreateDatabase: True

11:45:59| Info| InstallInfo.CurrentFolder: c:\8a88feca5d8d37f24f16c9

11:45:59| Info| InstallInfo.InstallAlways: False

11:45:59| Info| InstallInfo.InstallingPackage: c:\8a88feca5d8d37f24f16c9\Client_i386.msp

11:45:59| Info| InstallInfo.InstallType: Install

11:45:59| Info| InstallInfo.LocalPackage:

11:45:59| Info| InstallInfo.LogFile: C:\Users\mpo\AppData\Roaming\Microsoft\MSCRM\AutoUpdate\{004a7e60-5db7-4f05-b7c1-1d2dd653a1a6}.log

11:45:59| Info| InstallInfo.PackageName: Client_i386.msp

11:45:59| Info| InstallInfo.RebootRequired: False

11:45:59| Info| InstallInfo.SharedInstall: False

11:45:59| Info| InstallInfo.SourceFolder: c:\8a88feca5d8d37f24f16c9

11:45:59| Info| InstallInfo.SuppressReboot: True

11:45:59| Info| InstallInfo.TargetFolder: C:\Windows\$CrmUninstallKB968176_Client$

11:45:59| Info| InstallInfo.UIMode: Quiet

11:45:59| Info| InstallInfo.UserCancel: False

11:45:59| Info| IpcInfo.NoLock: True

11:45:59| Info| ProductInfo.ExistingLanguage: 1033

11:45:59| Info| ProductInfo.ExistingProductCode: 539d63c6-4ef4-4b9e-9926-85053f119171

11:45:59| Info| ProductInfo.ExistingVersion: 4.0.7333.3

11:45:59| Info| ProductInfo.InstallState: Local

11:45:59| Info| UpdateInstallInfo.Auto: True

11:45:59| Info| UpdateInstallInfo.Component: Client

11:45:59| Info| UpdateInstallInfo.ComponentInfo: Microsoft.Crm.UpdateWrapper.ClientInfo

11:45:59| Info| UpdateInstallInfo.DbHotfix: False

11:45:59| Info| UpdateInstallInfo.KBNumber: KB968176

11:45:59| Info| UpdateInstallInfo.LanguageID: 1033

11:45:59| Info| UpdateInstallInfo.PatchID: {004A7E60-5DB7-4F05-B7C1-1D2DD653A1A6}

11:45:59| Info| UpdateInstallInfo.PublishReports: None

11:45:59| Info| UpdateInstallInfo.ReleaseType: Update Rollup 4

11:45:59| Info| UpdateInstallInfo.Revision: 1551

11:45:59|Verbose| Method entry: Microsoft.Crm.UpdateWrapper.UpdateSetup.Install| System.Collections.Hashtable

11:46:00|Verbose| Method entry: Microsoft.Crm.UpdateWrapper.HotfixMspInstaller.Install

11:46:00| Info| === Logging started: 5/19/2009 11:46:00 ===

11:46:00| Info| Action 11:46:00: INSTALL.

11:46:00| Info| Action start 11:46:00: INSTALL.

11:46:00| Info| Action 11:46:00: AppSearch. Searching for installed applications

11:46:00| Info| Action start 11:46:00: AppSearch.

11:46:00| Info| Action ended 11:46:00: AppSearch. Return value 1.

11:46:00| Info| Action 11:46:00: LaunchConditions. Evaluating launch conditions

11:46:00| Info| Action start 11:46:00: LaunchConditions.

11:46:00| Info| Action ended 11:46:00: LaunchConditions. Return value 1.

11:46:00| Info| Action 11:46:00: FindRelatedProducts. Searching for related applications

11:46:00| Info| Action start 11:46:00: FindRelatedProducts.

11:46:00| Info| Action ended 11:46:00: FindRelatedProducts. Return value 0.

11:46:00| Info| Action 11:46:00: ValidateProductID.

11:46:00| Info| Action start 11:46:00: ValidateProductID.

11:46:00| Info| Action ended 11:46:00: ValidateProductID. Return value 1.

11:46:00| Info| Action 11:46:00: SetInstallDirectory.

11:46:00| Info| Action start 11:46:00: SetInstallDirectory.

11:46:00| Info| Action ended 11:46:00: SetInstallDirectory. Return value 1.

11:46:00| Info| Action 11:46:00: SetTargetDirectory.

11:46:00| Info| Action start 11:46:00: SetTargetDirectory.

11:46:00| Info| Action ended 11:46:00: SetTargetDirectory. Return value 1.

11:46:00| Info| Action 11:46:00: CostInitialize. Computing space requirements

11:46:00| Info| Action start 11:46:00: CostInitialize.

11:46:00| Info| Action ended 11:46:00: CostInitialize. Return value 1.

11:46:01| Info| Action 11:46:01: SetIsDesktopClient.

11:46:01| Info| Action start 11:46:01: SetIsDesktopClient.

11:46:01| Info| Action ended 11:46:01: SetIsDesktopClient. Return value 1.

11:46:01| Info| Action 11:46:01: SetIsLightClient.

11:46:01| Info| Action start 11:46:01: SetIsLightClient.

11:46:01| Info| Action ended 11:46:01: SetIsLightClient. Return value 1.

11:46:01| Info| Action 11:46:01: SetInstalled.

11:46:01| Info| Action start 11:46:01: SetInstalled.

11:46:01| Info| Action ended 11:46:01: SetInstalled. Return value 1.

11:46:01| Info| Action 11:46:01: FileCost. Computing space requirements

11:46:01| Info| Action start 11:46:01: FileCost.

11:46:01| Info| Action ended 11:46:01: FileCost. Return value 1.

11:46:01| Info| Action 11:46:01: SetMapiPath.

11:46:01| Info| Action start 11:46:01: SetMapiPath.

11:46:01| Info| Action ended 11:46:01: SetMapiPath. Return value 1.

11:46:01| Info| Action 11:46:01: EditMapiPath.

11:46:01| Info| Action start 11:46:01: EditMapiPath.

11:46:03| Info| CAPACK: CAPack::InvokeManagedCustomAction(Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.EditMapiPath)

11:46:03| Info| CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSIE5C1.tmp-\

11:46:04| Info| CAPACK: Binding to CLR version v2.0.50727

11:46:04| Info| CustomActionProxy.InvokeCustomAction(Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.EditMapiPath)

11:46:04| Info| Calling custom action Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.EditMapiPath

11:46:05| Info| Action ended 11:46:05: EditMapiPath. Return value 1.

11:46:05| Info| Action 11:46:05: CostFinalize. Computing space requirements

11:46:05| Info| Action start 11:46:05: CostFinalize.

11:46:05| Info| Action ended 11:46:05: CostFinalize. Return value 1.

11:46:05| Info| Action 11:46:05: MigrateFeatureStates. Migrating feature states from related applications

11:46:05| Info| Action start 11:46:05: MigrateFeatureStates.

11:46:05| Info| Action ended 11:46:05: MigrateFeatureStates. Return value 0.

11:46:05| Info| Action 11:46:05: InstallValidate. Validating install

11:46:05| Info| Action start 11:46:05: InstallValidate.

11:46:11| Info| Action ended 11:46:11: InstallValidate. Return value 1.

11:46:11| Info| Action 11:46:11: InstallInitialize.

11:46:11| Info| Action start 11:46:11: InstallInitialize.

11:46:13| Info| Action ended 11:46:13: InstallInitialize. Return value 1.

11:46:13| Info| Action 11:46:13: InstallExecute.

11:46:13| Info| Action start 11:46:13: InstallExecute.

11:46:13| Info| Action ended 11:46:13: InstallExecute. Return value 1.

11:46:13| Info| Action 11:46:13: SetInstallLocation.

11:46:13| Info| Action start 11:46:13: SetInstallLocation.

11:46:13| Info| Action ended 11:46:13: SetInstallLocation. Return value 1.

11:46:13| Info| Action 11:46:13: ProcessComponents. Updating component registration

11:46:13| Info| Action start 11:46:13: ProcessComponents.

11:46:13| Info| Action 11:46:13: GenerateScript. Generating script operations for action:

11:46:13| Info| Action ended 11:46:13: ProcessComponents. Return value 1.

11:46:13| Info| Action 11:46:13: MsiUnpublishAssemblies. Unpublishing assembly information

11:46:13| Info| Action start 11:46:13: MsiUnpublishAssemblies.

11:46:13| Info| Action ended 11:46:13: MsiUnpublishAssemblies. Return value 1.

11:46:13| Info| Action 11:46:13: UnpublishFeatures. Unpublishing Product Features

11:46:13| Info| Action start 11:46:13: UnpublishFeatures.

11:46:13| Info| Action ended 11:46:13: UnpublishFeatures. Return value 1.

11:46:13| Info| Action 11:46:13: RemoveRegistryValues. Removing system registry values

11:46:13| Info| Action start 11:46:13: RemoveRegistryValues.

11:46:13| Info| Action ended 11:46:13: RemoveRegistryValues. Return value 1.

11:46:13| Info| Action 11:46:13: RemoveShortcuts. Removing shortcuts

11:46:13| Info| Action start 11:46:13: RemoveShortcuts.

11:46:13| Info| Action ended 11:46:13: RemoveShortcuts. Return value 1.

11:46:13| Info| Action 11:46:13: RemoveFiles. Removing files

11:46:13| Info| Action start 11:46:13: RemoveFiles.

11:46:13| Info| Action ended 11:46:13: RemoveFiles. Return value 0.

11:46:13| Info| Action 11:46:13: RemoveFolders. Removing folders

11:46:13| Info| Action start 11:46:13: RemoveFolders.

11:46:13| Info| Action ended 11:46:13: RemoveFolders. Return value 1.

11:46:13| Info| Action 11:46:13: CreateFolders. Creating folders

11:46:13| Info| Action start 11:46:13: CreateFolders.

11:46:13| Info| Action ended 11:46:13: CreateFolders. Return value 1.

11:46:13| Info| Action 11:46:13: InstallFiles. Copying new files

11:46:13| Info| Action start 11:46:13: InstallFiles.

11:46:16| Info| Action ended 11:46:16: InstallFiles. Return value 1.

11:46:16| Info| Action 11:46:16: ActivateAddin.

11:46:16| Info| Action start 11:46:16: ActivateAddin.

11:46:18| Info| CAPACK: CAPack::InvokeManagedCustomAction(Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.ActivateAddin)

11:46:18| Info| CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI1F0B.tmp-\

11:46:19| Info| CAPACK: Binding to CLR version v2.0.50727

11:46:19| Info| CustomActionProxy.InvokeCustomAction(Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.ActivateAddin)

11:46:19| Info| Calling custom action Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.ActivateAddin

11:46:23| Info| Successfully activated Microsoft Dynamics CRM for Outlook.

11:46:24| Info| Action ended 11:46:24: ActivateAddin. Return value 1.

11:46:24| Info| Action 11:46:24: SetEditMapiData.

11:46:24| Info| Action start 11:46:24: SetEditMapiData.

11:46:24| Info| Action ended 11:46:24: SetEditMapiData. Return value 1.

11:46:24| Info| Action 11:46:24: PatchFiles. Patching files

11:46:24| Info| Action start 11:46:24: PatchFiles.

11:46:24| Info| Action ended 11:46:24: PatchFiles. Return value 1.

11:46:24| Info| Action 11:46:24: EditMapi.

11:46:24| Info| Action start 11:46:24: EditMapi.

11:46:24| Info| Action ended 11:46:24: EditMapi. Return value 1.

11:46:24| Info| Action 11:46:24: SetHelpIndexData.

11:46:24| Info| Action start 11:46:24: SetHelpIndexData.

11:46:24| Info| Action ended 11:46:24: SetHelpIndexData. Return value 1.

11:46:24| Info| Action 11:46:24: CreateShortcuts. Creating shortcuts

11:46:24| Info| Action start 11:46:24: CreateShortcuts.

11:46:24| Info| Action ended 11:46:24: CreateShortcuts. Return value 1.

11:46:24| Info| Action 11:46:24: WriteRegistryValues. Writing system registry values

11:46:24| Info| Action start 11:46:24: WriteRegistryValues.

11:46:24| Info| Action ended 11:46:24: WriteRegistryValues. Return value 1.

11:46:24| Info| Action 11:46:24: RegisterUser. Registering user

11:46:24| Info| Action start 11:46:24: RegisterUser.

11:46:24| Info| Action ended 11:46:24: RegisterUser. Return value 0.

11:46:24| Info| Action 11:46:24: RegisterProduct. Registering product

11:46:24| Info| Action start 11:46:24: RegisterProduct.

11:46:24| Info| Action ended 11:46:24: RegisterProduct. Return value 1.

11:46:24| Info| Action 11:46:24: MsiPublishAssemblies. Publishing assembly information

11:46:24| Info| Action start 11:46:24: MsiPublishAssemblies.

11:46:25| Info| Action ended 11:46:25: MsiPublishAssemblies. Return value 1.

11:46:25| Info| Action 11:46:25: PublishFeatures. Publishing Product Features

11:46:25| Info| Action start 11:46:25: PublishFeatures.

11:46:25| Info| Action ended 11:46:25: PublishFeatures. Return value 1.

11:46:25| Info| Action 11:46:25: PublishProduct. Publishing product information

11:46:25| Info| Action start 11:46:25: PublishProduct.

11:46:25| Info| Action ended 11:46:25: PublishProduct. Return value 1.

11:46:25| Info| Action 11:46:25: InstallFinalize.

11:46:25| Info| Action start 11:46:25: InstallFinalize.

11:46:25| Info| Action 11:46:25: ProcessComponents. Updating component registration

11:46:26| Info| Action 11:46:26: CreateFolders. Creating folders

11:46:26| Info| Action 11:46:26: InstallFiles. Copying new files

11:46:26| Error| An installation package for the product Microsoft Dynamics CRM 4.0 for Microsoft Office Outlook cannot be found. Try the installation again using a valid copy of the installation package 'client.msi'., Error, OK, Option1

11:49:50| Info| InputResult: OK

11:49:50| Info| Action ended 11:49:50: InstallFinalize. Return value 3.

Action Microsoft.Crm.UpdateWrapper.MspInstallAction failed.

Fatal error during installation.

11:49:53| Error| System.Configuration.Install.InstallException ---> System.Exception: Action Microsoft.Crm.UpdateWrapper.MspInstallAction failed. ---> Microsoft.WindowsInstaller.InstallerException: Fatal error during installation.

at Microsoft.WindowsInstaller.Installer.ApplyPatch(String patchPackage, String installPackage, InstallType installType, String commandLine)

at Microsoft.WindowsInstaller.Installer.ApplyPatch(String patchPackage, String commandLine)

at Microsoft.Crm.UpdateWrapper.MspInstallAction.Do(IDictionary parameters)

at Microsoft.Crm.Setup.Common.Action.ExecuteAction(Action action, IDictionary parameters, Boolean undo)

--- End of inner exception stack trace ---

at Microsoft.Crm.Setup.Common.Action.ExecuteAction(Action action, IDictionary parameters, Boolean undo)

at Microsoft.Crm.Setup.Common.Action.DoAction(Action action, IDictionary parameters)

at Microsoft.Crm.UpdateWrapper.HotfixMspInstaller.Install()

at Microsoft.Crm.UpdateWrapper.HotfixMspInstaller.Install(IDictionary savedState)

at Microsoft.Crm.Setup.Common.ComposedInstaller.InternalInstall(IDictionary stateSaver)

at Microsoft.Crm.Setup.Common.ComposedInstaller.Install(IDictionary stateSaver)

at Microsoft.Crm.UpdateWrapper.UpdateSetup.Install(IDictionary data)

at Microsoft.Crm.UpdateWrapper.UpdateSetup.Run()

--- End of inner exception stack trace ---

at Microsoft.Crm.UpdateWrapper.UpdateSetup.Run()

at Microsoft.Crm.UpdateWrapper.UpdateSetup.InternalMain(String[] args)

In there a V2 in the works?

Having our clients manually install the rollup is not a feasible option with hundreds of users over multiple organizations!
Doug

26 May 2009 1:00 PM

I am having the same issue as Carsten.

I have implemented every other patch with AutoUpdate in the exact same manner, but this one is throwing the 'client.msi' error

Any plans for a V2?
Alex

27 May 2009 5:02 AM

Dutch UR4 version also asks for client.msi
bandicoot

27 May 2009 11:07 AM

Can CRMv4.0-KB968176-i386-Client-ENU.exe

be succesfully installed on a 64bit Vista client?

If not than what should be used to upgrade the CRM client as it fails to connect to the server after installing rollup 4.0
Dana

27 May 2009 2:44 PM

I am having a similar issue to Andy's where some of our CRM 4.0 for Office Outlook and some w/Offline access are reporting since the update constant hanging when doing anything in Outlook now.
Luke

28 May 2009 9:39 AM

Just pushed out the Auto-Update to our company. People receive a couple different error messages:

- Setup has detected files in use (with nothing but Outlook open)

- Installation package for Microsoft Dynamics CRM 4.0 for Microsoft Office Outlook cannot be found. Try the installation with a valid copy of the installation package 'Client.msi'

As of yet not one person has successfully gotten the rollup to install. I'd love to roll-back the changes, so that they are not prompted, but haven't seen anywhere on how to do that.

Help would be appreciated.