The Microsoft Dynamics CRM Blog
News and views from the Microsoft Dynamics CRM Team

Update Rollup 2 for Microsoft Dynamics CRM 4.0

Update Rollup 2 for Microsoft Dynamics CRM 4.0

  • Comments 25

Note: This post has been rewritten with many of the changes you recommended in the comments below. You can find the new announcement here. 

The Microsoft Dynamics CRM Sustained Engineering team released Microsoft Dynamics CRM 4.0 Update Rollup 2 on Thursday, January 15, 2009.

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

Install Details about Update Rollup 2

  • Update Rollup 1 is not a prerequisite for installing Update Rollup 2
  • The Update Rollup 2 client can be deployed before the server is upgraded to Update Rollup 2
  • Update Rollup 2 can be uninstalled
  • Unlike Update Rollup 1, Update Rollup 2 is packaged so that each language is packaged individually. As a result, the download size of the packages for Update Rollup 2 is significantly smaller. For example, the CRM Server package size is reduced from about 171 MB in Update Rollup 1 to about 9 MB in Update Rollup 2. The Outlook Client package size is reduced from about 78 MB in Update Rollup 1 to about 4 MB in Update Rollup 2

How to avoid a required reboot when installing Update Rollup 2 for 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.
  • Check for Updates and start the install.  While that is running, choose Exit from Outlook’s File menu to close down Outlook.  This will avoid any “File in use” errors.  If you do get the error, you were probably a little slow in shutting down Outlook.  You can click-on “Retry” once Outlook and the CRM hoster process have completed their shutdowns.
  • Restart Outlook after the patch is installed.

Making Update Rollup 2 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 1.

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

1. Create the configuration XML file and save it.

<ClientPatches>

   <Create>

      <!--- *** UR2 PATCH -->

        <ClientPatchInfo>

          <PatchId>{9EA7FDEB-9D7E-4278-8CD1-94ACEFA40D3F }</PatchId>

          <Title>Update Rollup 2 for Microsoft Dynamics CRM 4.0 (KB 959419)</Title>

          <Description>Update Rollup 2 for Microsoft Dynamics CRM 4.0 (KB 959419)</Description>

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

          <IsMandatory>true</IsMandatory>

          <IsEnabled>true</IsEnabled>

          <ClientType>OutlookLaptop, OutlookDesktop</ClientType>

          <LinkId>140023</LinkId>

      </ClientPatchInfo>

   </Create>

</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 2 for Microsoft Dynamics CRM 4.0 (KB 959419)” 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.

Smiti Shah

  • Vår produktteam har publiserat mer information om vad som finns i Rollup 2 för Dynamics CRM. Speciellt

  • On our german crm pro server the text of the export customizations confirmation dialog looks very strange after update rollup 2 (some encoding error?). Any ideas?

  • On one of my app/platform servers I am getting this error:

    System.Exception: Action Microsoft.Crm.UpdateWrapper.MspInstallAction failed. ---> Microsoft.WindowsInstaller.InstallerException: This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.

    Any ideas?

  • On our german crm pro server the text of the export customizations confirmation dialog looks very strange after the rollup 2 (some encoding error?).

    The second issue is that workflow rules with send email actions can't be published.

    Any ideas?

  • One more thing. With Update Rollup 1, when you clicked Check for Updates, you would get a message stating no new updates were available if you had already installed rollup 1.

    However, with rollup 2 deployed as you have above, you do not get this message if rollup 2 is already installed. Instead, you are allowed to re-download and re-install rollup 2 ad nauseum. Thoughts?

  • I'm wondering if there may be an issue with my install.

    I had an install of CRM 4 with Rollup Pack 1 and I went to install Rollup Pack 2.

    a) I got a warning that there were files in use... apparently the setup does not stop the Async service

    b) during the install I got an error updating a file (404 ).  Apparently the installer was trying to hit http://<hostname> or http://<localhost> and my install is in a named site (http://crm.fqdn).  I got around the problem by temporarily stoping my other site, adding the default (*) binding to the CRM site, completing the install, then removing that binding (so my other site could be started).

    Are these known issues, or do I have bigger problems?

  • After installing Update Rollup 2 we cannot publish any of our workflows, old ones that used to work before nor the new ones. Unistalling the Update Rollup from the server - hope it helps!

  • For the issues with publishing workflows:

    If you have modified the Microsoft CRM website web.config file, then you need to manually open the Microsoft CRM Web site web.config file in an editor like Notepad and add the following section to it in order to continue being able to publish workflows:

    In the section <authorizedTypes>

    …multiple lines here

                                                   <authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Globalization" TypeName="CultureInfo" Authorized="True"/>

    </authorizedTypes>

    Thanks

  • I have an IFD of MS CRM. I've configured the AutoUpdate using the XML found in this article, and you get prompted to install the update and all that goes well. However everytime I or other users start outlook they are asked to install the same update again. If I look in Add/Remove programs I can see that the update has been installed.

    Also I'm using <LinkId>140023</LinkId>.

    Any ideas?

  • I have followed the instructions and the clients get prompted to install the update as expected.  I have it so that each client gets the update direct from the Internet.  The install completes as expected, and is shown as installed.  However after the reboot the prompt comes up again saying it needs to be installed, even though it can be seen in add/remove programs as being installed.

    Has anyone got any suggestions?

  • I am also having the issue with the error coming saying "System.Exception: Action Microsoft.Crm.UpdateWrapper.MspInstallAction failed. ---> Microsoft.WindowsInstaller.InstallerException: This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package."

    Anyone getting the client update to work?

  • I have the same problem, the update shows every time I start Outlook. It is listed in add/remove programs......

    Also, the blog says "Below are the necessary steps to configure the AutoUpdate for Update Rollup 1." <- should be 2, right? ;)

    /T

  • In what order should I install server, router and srs?

    /T

  • Is there a 64bit client version of this rollup ????

  • We managed to fix our problem with update being installed and then the outlook client not recognizing as being installed.

    The issue was that the above patchid {9EA7FDEB-9D7E-4278-8CD1-94ACEFA40D3F} is incorrect and should be

    {84EBD2D4-7530-47DA-B7C5-72E4F4FA5AE5}

    We also had to use the <Delete> command in our patch config file to remove the incorrect patchid.

    Hope that helps.

Page 1 of 2 (25 items) 12
Leave a Comment
  • Please add 1 and 4 and type the answer here:
  • Post