Update Rollup 2 for Microsoft Dynamics CRM 4.0 – More Info

On 2/8/2008, the CRM Sustained Engineering team released a new version of the Update Rollup 2 packages. The new version of Update Rollup 2 addresses some of the issues that have been noted in the comments for this blog entry.


  • Strings in the localized product showing up as garbage or in English.

  • Customized web.config causing issues after Update Rollup 2 is installed.

Customers do not need to uninstall the original Update Rollup 2 packages. The new packages will install over the top. If a customer has not been affected by the issues in the original Update Rollup 2 package they do not need to update to the new version. Customers can install Client, Server, Router Update Rollup 2 in any order.

The steps for the AutoUpdate have caused some confusion. There is a different PatchId and LinkId for every language of the product. You will find a table at the bottom of this post that has the PatchId and LinkId for each Language. Note: The new packages changed the PatchId so it will need to be updated, as the previous PatchId is no longer valid.


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 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 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 2.

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

*** 2/9/2008 Update ***

The steps below are for the English version of the product. The PatchId and LinkId values will be different for every localized version of CRM 4.0. There is a table at the bottom of this post that lists the correct PatchId and LinkId for each language.


1. Create the configuration XML file and save it.



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


<!--- *** The PatchId is different for every Language. Please see the table at the end for correct Link ID to use -->


          <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 -->



          <ClientType>OutlookLaptop, OutlookDesktop</ClientType>

<!--- *** The LinkId is different for every Language. Please see the table at the end for correct Link ID to use -->





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.

*** 2/9/2008 Update ***


LinkID: 140023&clcid=0x401

PatchID: {5976FEF7-2939-4597-B849-378B5010E7EA}

Chinese (Simplified)

LinkID: 140023&clcid=0x804

PatchID: {1F9AD22B-7E77-4704-94F2-ED4C9A9204FE}

Chinese (Hong Kong)

LinkID: 140023&clcid=0xc04

PatchID: {8E4BD4EB-6024-4F50-9F8B-ECB2D2962268}

Chinese (Traditional)

LinkID: 140023&clcid=0x404

PatchID: {544B5D8F-1561-4079-9D1B-871958FD5784}


LinkID: 140023&clcid=0x405

PatchID: {7703B3AB-5040-43A0-9E51-C679C1D901DB}


LinkID: 140023&clcid=0x406

PatchID: {9CE94585-65D2-4032-8E9C-2BEC113DBBC5}


LinkID: 140023&clcid=0x413

PatchID: {B0DABBC4-7E03-4BF4-85CB-7F6556D7A57D}


LinkID: 140023&clcid=0x409 (or just 140023)

PatchID: {321EFF1F-4402-4554-B037-B1492FFA67E9}


LinkID: 140023&clcid=0x40b

PatchID: {318C90C1-FE54-4383-BF1F-B9C20BBD2E58}


LinkID: 140023&clcid=0x40c

PatchID: {AA73B91A-CDAD-43CB-AD46-725AC839DAA4}


LinkID: 140023&clcid=0x407

PatchID: {C9344B1E-E32A-4C78-ADAB-332C3F934A95}


LinkID: 140023&clcid=0x408

PatchID: {460B3EBE-525F-44C2-8F59-D71DAA1E0136}


LinkID: 140023&clcid=0x40d

PatchID: {9C5A6F83-2C6E-4B32-91D8-6ADB7E279184}


LinkID: 140023&clcid=0x40e

PatchID: {CB0F2A7F-11F1-4AEE-AF5F-78A485DEB43A}


LinkID: 140023&clcid=0x410

PatchID: {1BF9AC1B-C4B8-4555-AABE-595C653C1A0D}


LinkID: 140023&clcid=0x411

PatchID: {FF755164-2686-4B81-860A-13B66A62A10A}


LinkID: 140023&clcid=0x412

PatchID: {6FD317AE-D2E1-4307-9E4F-F324B6615632}


LinkID: 140023&clcid=0x414

PatchID: {821536C9-5E42-4B95-879B-DEAD921C8510}


LinkID: 140023&clcid=0x415

PatchID: {D5D73DEA-FBC7-4B73-BDAF-3C54CD735DB0}

Portuguese (Brazil)

LinkID: 140023&clcid=0x416

PatchID: {98557D6F-49E8-4280-9435-9FE0CD6979F5}

Portuguese (Portugal)

LinkID: 140023&clcid=0x816

PatchID: {63F4323D-5341-4EC2-A7E6-6EB6A12E5EC5}


LinkID: 140023&clcid=0x419

PatchID: {D6A8BD6F-E3AF-42DB-95C1-4538520C227D}


LinkID: 140023&clcid=0xc0a

PatchID: {52B9A75C-22E0-4556-B978-9CF5CAB5353F}


LinkID: 140023&clcid=0x41d

PatchID: {75EF6272-B9A7-4C78-87B4-1730B019C431}


LinkID: 140023&clcid=0x41f

PatchID: {6F3E936F-F745-44CE-8412-EA5CDE05748D}

Keep your comments, experiences, and observations coming. We're listening.

Matt Brown

Comments (15)

  1. Phil Edry says:

    I have now registered config files both V1 and V2 of Rollup 2 on my CRM server. How do I remove the old Rollup 2 (V1) config file registration? Now when users go to check for updates, they get two duplicate "Update Rollup 2 for Microsoft Dynamics CRM 4.0 (KB 959419)" entries, one for V1 that I registered earlier, and one for V2.

    This does not solve the original issue, because the original registration for Rollup 2 V1 will always show up as an available update.

    I realize that Rollup 2 V2 will install over Rollup 2 V1, but it would be cleaner if we didn’t see Rollup 2 V1 as an option to install.

    Phil Edry – DynamicsCRMBlog.com

  2. Update Rollup 2 for Microsoft Dynamics CRM 4.0 is available. This update rollup is available for all

  3. Update Rollup 2 for Microsoft Dynamics CRM 4.0 is available. This update rollup is available for all

  4. Andre says:

    We installed Rollup 2 version 2 for MS CRM 4.0. After this, when in crm, you can’t assign a task or any type of activity to yourself. This happens even if you are system administrator. You can also reassign the task to anybody else, just not yourself.

  5. Corey says:

    Phil – To remove an update from the config datbaase that you uploaded you need to run the clientpatchconfigurator tool that you used to make the update available and pass in a delete xml file. Similar to this.






    See the Maining Guide in the Implementation Guide for more information.


  6. Mike says:


    Can the server update be installed before the clients? will the clients experience any issues if they are not rolled up straight away?


  7. Hace unos días hablaba en este blog de la salida del Update Rollup 2 para CRM 4 . Pues bien, en el blog

  8. Lori says:

    Update Rollup 2 seems to have broken some things for me.  1) In Workflows, I am trying to choose a child workflow.  I use the lookup tool to select the workflow and when I hit "save" my selection is gone.  This a major problem.  2)  Within the Task Activity form, a user could assign a Task to a queue by selecting the "owner" lookup field, then change the picklist from "user" to "queue".  That picklist is now disabled.  Anyone else having these issues, or could anyone get me pointed in the right direction with Microsoft to get this resolved?

  9. Simon Gadsby says:

    FYI if you use the config.xml file to distribute the update, then note that the LinkID attribute is appended to "AutoUpdateDownloadUrl" if it is defined, or "http://go.microsoft.com/fwlink/?LinkId=&quot;.

    As a consequence, if your clients are downloading from the Internet:

    a) set the LinkID attribute to the numeric as per article to ensure correct download from Microsoft.

    b) make sure that you do not have an authenticating proxy server set on the clients!

    If you have configured "AutoUpdateDownloadUrl" for clients to download the update internally:

    a) set LinkID attribute to the filename of the update on the target webserver.

  10. Josh Ashwood says:

    Does this still require admin rights?

    In a post regarding AutoUpdate last year (http://blogs.msdn.com/crm/archive/2008/05/08/crm-client-autoupdate.aspx) , Eric Newell mentioned the team was looking at addressing this issue. Any feedback appreciated, obviously in many organizations the end users do not have the ability to control software installation.

  11. Phil Edry says:

    Thanks Corey! I hadn’t realized this tool had been documented in the IG.

    For everyone’s reference, the ClientPatchConfigurator is documented on page 2-5 of the Microsoft Dynamics CRM 4.0 Operating and Maintaining Guide (Rev. 4.3.0).

  12. Bryan Cooke says:

    To answer Josh’s question…

    Client updates still require admin rights on the box.  We are working on some enhancements that will hopefully eliminate that requirement. I don’t have a timeframe for you at this time.

  13. Josh Ashwood says:

    Guys… kb955055 – Problems with Mail Merge, included in this rollup.

    Does this resolve the same issue with Word 2003 SP3? ‘… is a mail merge document… Word cannot find its data source’

    The only product it talks about is Word 2007 SP1, however I can reproduce this using Office 2003 SP3.

    Any help appreciated!


  14. This post will cover some of the common issues seen in support and the common resolutions to those issues.

Skip to main content