We're proud to announce that all packages for Microsoft Dynamics CRM 2011 Update Rollup 16 were released on Wednesday, January 22nd, 2014 to the Microsoft Download Center! The Update Rollup 16 packages should appear on Microsoft Update in February, 2014.
Update Rollup 16 Build number:
Update Rollup 16 Microsoft Download Center page
Here's the "Master" Microsoft Dynamics Knowledge Base article for Update Rollup 16: (KB 2872369).
On Friday, January 24th 2014 at 9 AM Pacific Greg Nichols and Ryan Anderson from the Microsoft CRM Premier Field Engineering Team will provide information about:
on BlogTalkRadio during their Microsoft Dynamics CRM 2011 Update Rollup 16 Podcast.
Note regarding Podcasts: You can make our CRM Premier Field Engineering podcasts available on Zune by using the RSS feed below. In the Zune software, go to Collection -> Podcasts and click on the Add a Podcast button on the lower left, then enter the url for the RSS feed: http://www.blogtalkradio.com/pfedynamics.rss. After that, you can adjust the series settings like any other podcast, so you can sync with your smartphone or Zune.
Go to Top
The "CRM Update Rollup Collateral Page"
For pointers to download locations, release dates, build information, and CRM Premier Field Engineering blogs and podcasts for all Microsoft Dynamics CRM Update Rollups, visit the "CRM Update Rollup Collateral Page"
Update Rollup 16 News!
Update Rollup 16 is one of the larger CRM 2011 Update Rollups released, including over 140 fixes. As mentioned earlier, we plan on including the Update Rollup 16 fixes in Update Rollup 2 for CRM 2013
Update Rollup 16 is a collection of fixes for issues reported by customers or found by Microsoft's Engineering Team, plus changes to provide support for related technology components.
Update Rollup 16 news that you need to know because Update Rollups are cumulative, so these significant changes are also in Update Rollup 16!
For Microsoft Dynamics CRM business solutions that include an entity with a large dataset, record retrieval and grid rendering performance can be negatively impacted for users that do not have global access to all records associated with that entity. Code changes to mitigate this behavior first appeared in Microsoft Dynamics CRM 4.0, and have been fine-tuned since then.
With Microsoft Dynamics CRM 2011 Update Rollup 10 and later, big advancements have been made to optimize the performance of queries against large datasets by adjusting specific “statistical” settings to address the issue. Should this fail to achieve desired levels of performance, adjust the value associated with EnableRetrieveMultipleOptimization (ERMO) setting. You may have heard these changes described at this year's Convergence.
A first step in efforts to optimize the performance of queries against large data sets is to make adjustments to the “statistical” settings that affect the behavior of RetrieveMultiple queries. Although you can configure these settings by modifying the Windows Registry (under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM) on the each of the Web servers that is used in a deployment, we recommend that these settings be configured by using the OrgDbOrgSettings, which will ensure that the configuration applies to a specific organization. For additional information about configuring these settings by using the OrgDbOrgSettings, and to download the tool that makes the OrgDbOrgSettings changes you desire, see the Microsoft Knowledge Base article titled "OrgDBOrgSettings Tool for Microsoft Dynamics CRM 2011" (KB 2691237)
If making adjustments to these settings does not yield satisfactory levels of performance, then consider adjusting the value of the EnableRetrieveMultipleOptimization (ERMO) setting. The ERMO setting is commonly used to limit the duration of certain long running queries; specifically, to overcome issues related to local or deep business unit access within Microsoft Dynamics CRM 2011 security roles.
Many more details describing appropriate scenarios for the available settings are already available via the Microsoft Download Center in a revised version of the whitepaper "Optimizing and Maintaining the Performance of a Microsoft Dynamics CRM 2011 Server Infrastructure", in the sections “Optimizing the Performance of Queries against Large Datasets” and “Optimizing the Performance of Quick Find Queries”. The details will appear in the MSDN version of this whitepaper as quickly as possible.
NEW RELEASE REGARDING OrgDbOrgSettings!
You're probably familiar with the OrgDbOrgSettings command line tool (mentioned above) released by the CRM Product Group in the "Tools" package that is updated and released with each set of Update Rollup packages. With it, you configure some .xml and call your .xml with the command line utility described in KB 2691237. However, you may be daunted by configuring this .xml, to the point that you may not use the tool, or use it minimally - not exploring the many options outlined in KB 2691237 that may be of use to you. Well, the Microsoft Dynamics PFE team now has another option for you! By popular demand, our esteemed CRM PFE colleague Sean McNellis has developed a tool - a CRM 2011 / 2013 managed solution - that provides you with an easy-to-use GUI with which you can configure all of the options outlined in the Knowledge Base on a per-tenant basis. Feel free to download it, install it, and check it out... I sure use it!
Note: there is a code issue with the CRM Client for Microsoft Outlook that was resolved in Update Rollup 16 Client packages. Do not set either the AddressBookMaterializedViewsEnabled or DisableMapiCaching settings in the Organization entity metadata via the OrgDbOrgSettings tool in the Update Rollup Tools package or the Organizational Settings Editor on Codeplex if you are not running CRM 2011 Update Rollup 16 or higher on the Client. Also, do not set this key prior to the next major release of CRM 2013.
NOTE REGARDING "Deferring Database Updates when installing CRM 2011 Update Rollups"
My esteemed PFE teammate Sean McNellis published a blog you should be aware of regarding the possibility of deferring the CRM database updates when installing CRM 2011 Update Rollups. Essentially, Dynamics CRM 2011 Update Rollup executable packages automatically process and update the organization database updates during the installation. If your deployment has several large tenants or just one very large tenant you may prefer to first install the “binary” updates and worry about applying the database updates after the binary installation of the rollup (on an organization by organization basis). This would put the control and timing of when to update organizations from a SQL perspective in the hands of the administrator, and may make troubleshooting easier.
This feature allows you to separate the installation of the binary updates (DLL’s, executables, etc) from the installation of the database components (updated stored procedures, UDFs (user-defined functions), schema updates, out-of-box index changes, etc). Both updates still need to be completed as part of the update but you can now separately manage and execute those operations. This also allows you to retry database updates if they timeout or do not complete, without jeopardizing the installation binary updates.
I strongly urge you to read the entire blog to see if it applies to your needs. Thanks again, Sean!
General Update Rollup Notes:
Microsoft Dynamics CRM 2011 and 2013 Custom Code Validation Tool
Outlook Client Updates:
Data Management Enhancements to:
For more information about the Dynamics CRM Q4 2011 Service Update features, consult:
Go to Top
Update Rollup 16 packages are available for download via:
for these CRM components:
NOTE: On Jan. 20th, 2012 these installation files were updated to include CRM 2011 Update Rollup 6 (Build 05.00.9690.1992)
Microsoft Dynamics CRM 2011 Update Rollup 16 Prerequisites:
Note regarding Microsoft Dynamics CRM Stack Technology Compatibility:
Do you want to know if certain Service Packs or versions of a Microsoft product are supported with Dynamics CRM? Now we have all of this in one “living" Knowledge Base article: the Microsoft Dynamics CRM Compatibility List. For example, you can use this KB article to determine the latest Microsoft SQL Server major version and Service Pack that is supported. Microsoft lists new products like Internet Explorer 10, Microsoft Windows 8, and Microsoft Office 2013 Preview as TBD until testing is complete; generally near General Availability (GA) of that product.
Issues resolved via Microsoft Dynamics CRM 2011 Update Rollup 16:
Microsoft Dynamics CRM 2011 Update Rollup 16 is the fifteenth (considering that Update Rollup 9 was not released publicly) of a series of cumulative Update Rollups that include fixes for the issues that are or will be documented in the "Master Knowledge Base Articles" for CRM 2011 Update Rollups. As they are cumulative, Update Rollup 16 contains all fixes shipped via Update Rollups 1-16, including fixes that were never publicly released via Update Rollup 9.
Hotfixes and updates that you have to enable or configure manually
Occasionally, updates released via Update Rollups require manual configuration to enable them. Microsoft Dynamics CRM Update Rollups are always cumulative; for example, Update Rollup 16 contains all fixes previously released via Update Rollups 1-15 as well as fixes newly released via Update Rollup 16. So if you install Update Rollup 16 on a machine upon which you previously installed no Update Rollups, you will need to manually enable any desired fixes for Update Rollups 1-16:
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 2011 for Microsoft Office Outlook, a common question is whether it is supported to run mismatched versions. For example, where Update Rollup 5 has been installed on the CRM Server but the Outlook clients are still on Update Rollup 1, or where Update Rollup 1 is on the CRM server but due to updates available to the Outlook client you have decided to install Update Rollup 6 on the clients without installing Update Rollup 4 on the server.
The general rule of thumb is to try to keep the versions in sync as much as possible, and we recommend that you avoid deltas of more than one version between client and server. So ideally, you would be running Update Rollup 14 server with Update Rollup 13 or 14 on your Outlook client. 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.
For more information, see the blog posting "User experience while accessing CRM 2011 application servers while Update Rollups are being applied"
Go to Top
Microsoft Dynamics CRM compatibility with technology stack components: Internet Explorer, Windows Client and Server, Office, .NET Framework, and more
The Microsoft Dynamics CRM Engineering team consistently tests Microsoft Dynamics CRM 2011 against pre-release and release versions of technology stack components that Microsoft Dynamics interoperates with. When appropriate, Microsoft releases enhancements via future Microsoft Dynamics CRM 2011 Update Rollups or new major version releases to assure compatibility with future releases of these products. This compatibility matrix is updated via this Microsoft Knowledge Base article: Microsoft Dynamics CRM Compatibility List.
Greg Nichols Premier Field Engineering Microsoft Corporation
After installing roll up 16 an iframe on our dashboard containing a report shows the report shrunk. I've posted on forums, but nobody has an answer. I've rolled back to RU15 and it's works again.
@Chris - for this I would recommend opening a support case so they can investigate it and see if it's an intended change or if it's something that needs to be fixed in the future.
am new here,
just wanted to know where I can keep myself updated on next rollup release dates(ex: rollup-17 tentative release dates)
I found few links but that tells everything about previous versions and not about upcoming rollup versions dates.
IS there any place I can find a detailed description of what AddressBookMaterializedViewsEnabled does? Also, for performance, what's the recommended setting here?
@ Amit... currently we're not publishing tentative release dates for upcoming Update Rollups for either CRM 2011 or CRM 2013. The Knowledge Base articles are published a bit early, i.e. the KB article for CRM 2013 Update Rollup 2 has been available externally for a while, but it does not contain a release date. It does contain information on the fixes included, however. See support.microsoft.com/.../2919956.
@ Daniel: The AddressBookMaterializedViewsEnabled setting enables a "materialized view" (a database object that contains the results of a query) for the CRM Address Book. Using this setting can reduce memory pressure and possible Out of Memory exceptions on the CRM Client for Microsoft Office Outlook when you have a large number of CRM records in the address book - for example, > 100,000.
Note: there is a code issue with the CRM Client for Microsoft Outlook that was resolved in Update Rollup 16 Client packages. Do not set either the AddressBookMaterializedViewsEnabled or DisableMapiCaching settings in the Organization entity metadata via the OrgDbOrgSettings tool in the Update Rollup Tools package or the Organizational Settings Editor on Codeplex if you are not running UR16 on the Client. Also, do not set this key prior to the next major release of CRM 2013.
Thank you very much! I stumbled upon the reason why not to set this as I was testing Client 14 and 15. It would crash. We are now testing R 16 and it's behaving well so will skip those 2.
Again, thank you for your answer!
We have a same issue as Chris. Report in dashboard iFrame is broken. Shows big blank space in the header.
@ Chris & H. Desai... you're describing a known issue whose fix is tentatively scheduled for release in CRM 2011 Update Rollup 17.
Thanks Greg for the confirmation. Any idea on expected release date of UR 17?