Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Update Rollup 4 Client Installation problem RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    So I am in the middle of deploying Update Rollup 4 to my client machine.  I currently has Update Rollup 3.  Well, during the install, it asks for the CRM 4.0 disc so it can find client.msi.  This in and of itself is weird, but I get it and pop it in.  Well, it fails to find the client.msi on the disc, so I point it there manually.  The installer breifly continues before crashing with this error in the log:

    13:25:12|   Info| === Logging stopped: 5/13/2009  13:25:12 ===
    13:25:12|   Info| InstallerException: 1603
    13:25:12|  Error| 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 ---, Error, RetryCancel, Option1
    13:25:13|   Info| InputResult: Cancel
    13:25:13|  Error| Configuration exception.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.UpdateWrapper.UpdateSetup.Install(IDictionary data)
       at Microsoft.Crm.UpdateWrapper.UpdateSetup.Run()
    13:25:13|Verbose| Update Rollup 4 (KB968176) Was Not Completed Successfully.
    13:25:13|   Info| Microsoft Dynamics CRM 4.0 for Microsoft Office Outlook update was not completed successfully because of the following problems:
       

    Action Microsoft.Crm.UpdateWrapper.MspInstallAction failed.
    Fatal error during installation.


    Does anyone know the fix for that?  I need to know before I roll it out to all my clients.
    Wednesday, May 13, 2009 5:32 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    I found this to be an issue as well. What I determinied is that if you have deployed CRM via SMS\SCCM and it is looking for the original source, it most likely has been cleaned up if you do regular maintenaance cleaning of the client cache. There is a registry key that references that spot. If you point it to a network location, it will read what it needs from there and continue the UR4 installation. Since we had forgone the UR3 update due to internal process slowness, we really needed to push this one out. I simply updated the key to point the the network location and then did a "regedit.exe /q export.reg" as a "Run another program first" requirement for the UR4 installation. This worked just fine and we are rolling out with no problem. The key path is as follows:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\6C36D9354FE4E9B499625850F3111917\SourceList\Net]
    "1"=hex(2):#####

    The hex value would be determined by what you have entered. I maually updated the key on my system and then did an export rather than take the time to calculate the hex code to use in a vbscript. I hope this helps!

    Eric A. Groff
    Desktop Engineer
    Memphis, TN
    • Proposed as answer by Eric A. Groff Monday, June 29, 2009 4:02 PM
    • Marked as answer by Wayne Walton Tuesday, July 7, 2009 9:14 PM
    Monday, June 29, 2009 4:01 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    bump, anyone?
    Thursday, May 14, 2009 5:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Wayne, if you're absolutely sure you're using the right update for the installed lanugage I'd suggest opening a support ticket with Microsoft about this.

    You might try extracting the update with <insert exe here>.exe /x and trying to apply the asp manually (Right click -> Apply).


    Friday, May 15, 2009 6:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Did you get it figured out?  I'm getting the same error.
    Friday, May 22, 2009 2:33 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Last weekend we made Update Rollup #4 available for download for our hosted clients. Shortly after rolling out this update reports began to trickle in from users experiencing an error message which was causing the installation of the Update Rollup to fail. This message was asking users for the location of a very elusive ‘client.msi’ file. After combing through countless forums and blogs it became very clear that this was a wide-spread issue and one not limited to PowerObjects and our customers. We filed an escalated support ticket with Microsoft in hopes of getting the Update Rollup distributing and installing properly.

     

    After working with Microsoft for the better part of a week we received news from their CRM Support Team that:

    1.    There are NO plans to release a revised version of Update Rollup #4 that corrects the installation issue.

    2.    There is NO workaround at the present time and NO workaround will be developed.

    3.    The issue will be resolved with Update Rollup #5 which is scheduled to be released in early July.

     

    Here is a bit of insight from Mike Brown of the Microsoft CRM Team Blog:

     

    This is the same issue for both the normal and the Auto Update scenario[client.msi].  In UR4, the CRM Sustained Engineering Team made a performance fix that required adding a few additional files.  Because the new files were added to the package the Windows Installer thinks it needs to install them regardless on if they need to be or not.  The most common scenario for this happening is when trying to update the desktop client.  The issue is resolved in our upcoming UR5 release.

     

    We will keep an eye on this developing situation should any new information surface but at this time it does not look like there will be any client side updates until after the 4th of July. Rest assured we will provide news when Update Rollup #5 becomes available!

     

    We appreciate everyone’s patience with this issue!

    Monday, June 1, 2009 8:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I had a real difficult time installing this update.  I ended up uninstalling the CRM 4 client, but then couldn't reinstall.  I tried just about everything (uninstall office, re-install .NET Framework, etc., etc.).  My setup is Vista 64 with Office 2007.

    Then I found this posting:  http://www.vistax64.com/microsoft-office/52821-ms-office-2003-error-1913-mapisvc-inf.html

    I followed the steps to grant my login account with with full permissions on this file (default was set to SYSTEM): C:\Windows\SysWOW64\mapisvc.inf.

    After doing that, I was able to install the client and then Update 4.  So far so good.

    Chris.
    Wednesday, June 3, 2009 9:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    We are advising our clients to NOT install UR 4 as this setup issue describe above can be a real pain. 

    One method we have sucessfuly used to get UR 4 isntalled is to compmletely remove outlook crm client -  make sure all traces of it are truly gone.  Then install outlook crm client and go directly to UR 4. 
    Alex - www.PowerObjects.com
    • Proposed as answer by René Vroemen Monday, June 15, 2009 1:22 PM
    Monday, June 8, 2009 1:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I got the same error. After downloading (to be sure) the latest Outlook Client, uninstalling the Outlook Client and reinstalling it, I was able to successfully install Rollup 4 for the Outlook Client.

    CRM Consultant
    Monday, June 15, 2009 1:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I found this to be an issue as well. What I determinied is that if you have deployed CRM via SMS\SCCM and it is looking for the original source, it most likely has been cleaned up if you do regular maintenaance cleaning of the client cache. There is a registry key that references that spot. If you point it to a network location, it will read what it needs from there and continue the UR4 installation. Since we had forgone the UR3 update due to internal process slowness, we really needed to push this one out. I simply updated the key to point the the network location and then did a "regedit.exe /q export.reg" as a "Run another program first" requirement for the UR4 installation. This worked just fine and we are rolling out with no problem. The key path is as follows:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\6C36D9354FE4E9B499625850F3111917\SourceList\Net]
    "1"=hex(2):#####

    The hex value would be determined by what you have entered. I maually updated the key on my system and then did an export rather than take the time to calculate the hex code to use in a vbscript. I hope this helps!

    Eric A. Groff
    Desktop Engineer
    Memphis, TN
    • Proposed as answer by Eric A. Groff Monday, June 29, 2009 4:02 PM
    • Marked as answer by Wayne Walton Tuesday, July 7, 2009 9:14 PM
    Monday, June 29, 2009 4:01 PM