We're delighted to announce that Microsoft Dynamics CRM 4.0 Update Rollup 21 released Thursday February 9th, 2012! 

Note regarding Podcast: Microsoft Dynamics CRM 4.0 Update Rollup 21 was discussed during the CRM 2011 Update Rollup 6 Podcast delivered on October 26th, 2011.

NOTE: Due to the low volume of fix requests for CRM 4.0, the CRM SE team will stop shipping CRM 4.0 rollups on a regular schedule after UpdateRollup 21. CRM SE will service CRM 4.0 requests on an individual basis using our Critical on Demand process. 

CRM SE will continue to evaluate the need for Update Rollups for the remainder of CRM 4.0’s supported lifecycle.  A rollup will be shipped if there is a significant increase in volume of fix requests or in the event that a rollup will benefit a majority of the 4.0 installation base.

Related links you should know about: 

  • This article also contains links to related Microsoft Knowledge Base articles

Build number:
04.00.7333.3822 

Packages are available for download via the Update Rollup 21 Microsoft Download Center page for these CRM components:

 Microsoft Dynamics CRM 4.0 Update Rollup 21 Prerequisites:

Microsoft Dynamics CRM 4.0 Update Rollup 11 (and beyond) Prerequisites:

Issues resolved via Microsoft Dynamics CRM 4.0 Update Rollup 21: 

Microsoft Dynamics CRM 4.0 Update Rollup 21 is a cumulative Update Rollup that includes all the fixes for the issues that are documented in the "Master Knowledge Base Articles" for Update Rollups 1 through 21.

Hotfixes and updates that were released as individual fixes:

Update Rollup 21 for Microsoft Dynamics CRM 4.0 contains one update that was released as an individual fix:.

  • 2667046  Applications that use the Microsoft CRM Deployment web service may experience time-out errors in deployments that have large domains and multiple sub domains

Other fixes released via CRM 4.0 Update Rollup 21:

  • When you map users during the organization import process and then delete the users from Active Directory, the organization import process fails
  • When you add many marketing list members by using the Advanced Find function, and then you use the Add all the members option, you experience slow performance in Microsoft Dynamics CRM. Additionally, Microsoft SQL Server stops responding
  • Assume that you have two related entities. When only one of the entities has the Create privilege, Microsoft Dynamics CRM users cannot see the Add Existing button on the sub grids of the entity that does not have the Create privilege
  • When you enable or disable a user, SYSTEM is displayed in the Last Modified By field of the record. However, the user who performed the action should be displayed in the field
  • Assume that you upload data in a Microsoft Dynamics CRM 4.0 client for Outlook that is in offline mode. Then, you go online and perform a client synchronization. In this situation, you experience slow performance during client synchronization. However, the issue does not occur when you run the Fiddler tool
  • Assume that you reassign a workflow rule definition to another user, and the user publishes the workflow. The workflow instance records are associated with an entity type against which the workflow is run. In this situation, you cannot open the workflow instance in the System Jobs menu. Additionally, the workflow instance is not displayed in the relationship entity for workflow instances in the System Jobs menu in the workflow definition form

Hotfixes and updates that you have to enable or configure manually

Update Rollup 21 for Microsoft Dynamics CRM 4.0 contains no updates that you must enable or configure manually:

Special Considerations

  • 64-bit versions of Office 2010 will not be supported in Microsoft Dynamics CRM 4.0
  • With Update Rollup 8 installed, Microsoft CRM E-mail Router Service supports Microsoft Exchange Server 2010
  • With Update Rollup 12 installed, the Rule Deployment Wizard supports Microsoft Exchange Server 2010

Mismatched Update Rollup versions within a Microsoft Dynamics CRM deployment

In a scenario where you may be running many client workstations with Microsoft Dynamics CRM 4.0 for Microsoft Office Outlook, a common question is whether it is supported to run mismatched versions. For example, where Update Rollup 20 has been installed on the CRM Server but the Outlook clients are still on Update Rollup 15, or where Update Rollup 10 is on the CRM server but due to updates available to the Outlook client you have decided to install Update Rollup 20 on the clients without installing Update Rollup 20 on the server.

The general rule of thumb is to try to keep the versions in sync as much as possible. However, it is permissible (though not recommended as a long-term solution) to run mismatched Update Rollup versions on Outlook client and server, as Microsoft does do some testing of such combinations.

However, regarding the other Update Rollups (for example Rollups for the Microsoft Dynamics CRM 2011 Email Router or Microsoft Dynamics CRM 2011 Reporting Extensions), it is not supported nor recommended to run mismatched versions. A best practice is to update these components at the same time you update your CRM Server. Do the best you can to keep these Update Rollup versions in sync.

Internet Explorer 9 Compatibility

The Microsoft Dynamics CRM Sustained Engineering team extensively tested Microsoft Dynamics CRM 4.0 against pre-release versions of Internet Explorer 9 and continue to address compatibility issues, as they're reported, against the released (Released to Web) version of Internet Explorer 9.0.  If necessary, they plan to release enhancements via future Microsoft Dynamics CRM 4.0 Update Rollup releases to assure compatibility with Internet Explorer 9.