We're proud to announce that all packages for Microsoft Dynamics CRM 2013 Update Rollup 2 were released on Saturday, March 22nd 2014 to the Microsoft Download Center! The Update Rollup 2 packages should appear on Microsoft Update in April 8th 2014.
Update Rollup 2 Build number:
6.0.0002.0046 (Server re-release is 6.0.0002.0051)
Note: The CRM 2013 Update Rollup 2 Server package has been re-released for customers potentially having issues with authentication associated with Yammer integration or with CRM 2013 Server installation issues on Windows Server 2012 R2. The filename for the re-released package is CRM2013-Server-KB2919956-v2-ENU-amd64.exe, and is not needed if you are not using Yammer integration or setting up on Windows Server 2012 R2. The UR2 Server re-release build number is 6.0.0002.0051.
Update Rollup 2 Microsoft Download Center page
Here's the "Master" Microsoft Dynamics Knowledge Base article for Update Rollup 2: (KB 2919956). Going forward, the plan is for the Master Knowledge Base article for CRM 2013 Update Rollups to be published a bit in advance of release to aid planning.
On Friday, March 21st 2014 at 3:30 PM Pacific Time Greg Nichols and Ryan Anderson from the Microsoft CRM Premier Field Engineering Team provided information about:
on BlogTalkRadio during their Microsoft Dynamics CRM 2013 Update Rollup 2 Podcast
BlogTalkRadio and Internet Explorer 11 compatibility
If you're having trouble viewing the podcast when using Internet Explorer 11,
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"
Go to Top
Important CRM 2013 Update Rollup considerations!
A common question I get is “if I either upgrade from CRM 2011 or install the RTM version of CRM 2013 (build 6.0.0000.0809), what is the equivalent CRM 2011 Update Rollup level I have?" The answer is: essentially Update Rollup 14.
Some specific port requests for post-Update Rollup 14 fixes for CRM 2011 were included the original (RTM) release of CRM 2013, and port requests for other post-Update Rollup 14 CRM 2011 fixes can be requested via the normal Support process.
One set of port requests that you may be wondering about are the dramatic changes to the Microsoft Dynamics CRM Client for Microsoft Office Outlook
General Upgrade Rollup Notes:
Microsoft Dynamics CRM 2013 Custom Code Validation Tool
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 / CRM 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.
Update Rollup 2 packages are available for download via:
to update the Dynamics CRM Product installations listed in this Microsoft Knowledge base article:
Microsoft Dynamics CRM Installations, Updates and Documentation
Note: Microsoft Dynamics CRM 2013 Updates will be pushed via Microsoft Update as Important updates
Microsoft Dynamics CRM 2013 Update Rollup 2 Prerequisites:
Issues resolved via Microsoft Dynamics CRM 2013 Update Rollup 2:
Microsoft Dynamics CRM 2011 Update Rollup 2 is the second 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 2013 Update Rollups. As they are cumulative, Update Rollup 2 contains all fixes shipped via Update Rollups 1 and 2... you get the idea.
Fixes released via CRM 2013 Update Rollup 2:
Support for new technologies provided by this Update Rollup
The Microsoft Dynamics CRM Engineering team consistently tests Microsoft Dynamics CRM 2013 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 2013 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. Microsoft Dynamics CRM 2013 Update Rollup 2 provides support for:
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 2 will contain all fixes previously released via Update Rollup 1 as well as fixes newly released via Update Rollup 2. So if you install Update Rollup 2 on a machine upon which you previously installed no Update Rollups, you will need to manually enable any desired fixes for Update Rollups 1-2:
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 2013 for Microsoft Office Outlook, a common question is whether it is supported to run mismatched versions. For example, where Update Rollup 2 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 2 on the clients without installing Update Rollup 1 on the server.
The general rule of thumb is to try to keep the versions in sync as much as possible, and deltas of more than one version between client and server are not supported. So ideally, you would be running Update Rollup 2 (when it is released) on your CRM Servers with Update Rollup 1 or 2 on your Outlook clients. 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 Update Rollups for the Microsoft Dynamics CRM 2013 Email Router or Microsoft Dynamics CRM 2013 SSRS Data Connector), 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", which still applies to Microsoft Dynamics CRM 2013
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 2013 against pre-release and release versions of technology stack components that Microsoft Dynamics interoperates with. When appropriate, Microsoft will release enhancements via future Microsoft Dynamics CRM 2013 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 Dynamics CRM Senior Premier Field EngineerMicrosoft Corporation
I have installed the Update rollup 2 on MScrm 2013 and it is still showing me an error on saving the appointment. "Object Does'nt support property or method 'Form_onsave'.
Could you please verify if you are facing this issue on your end?
I can confirm, Sheenam. This is scheduled to be fixed in an upcoming CRM 2013 Update Rollup or release.
As per this forum posting:
there is a current workaround: to create an unmanaged solution, include only the appointment component without dependencies, and comment out or remove the Internal Handler from the customizations.xml and import this back into the organization. See below:
<Handler functionName="Mscrm.Form_onsave" libraryName="Appointment_main_system_library.js" handlerUniqueId="bd8e0272-4f6c-42e6-a51e-71e0fc627a5f" enabled="true" passExecutionContext="true" />
I have installed Update Rollup 2 on MS CRM 2013. Yammer is rendering perfectly on my Account entity and other entities, but when it comes to Contact entity, Yammer tab only displays a blank white page.
Any thoughts about this? Thank you!
I have also installed Update Rollup 2 on MS CRM2013. If I run "test and enable Mailbox" , it will return Success, but later on some of our users are still facing the issue "The mailbox (CRM User) has been disabled for synchronizing appointments, contacts, and tasks due to unknown error"
Any solutions for this? Many thanks!
@ Lei... this is a known issue currently under investigation. You might see whether the problem reproduces against CRM 2013 Service Pack 1, because in at least one instance this resolved the issue.
Hi I am trying to install Update Rollup 2 MS CRM2013. But It Saying - "The Update Rollup 2 for Microsoft Dynamics CRM Server (KB2919956-V2) completed successfully. However, the database update failed for some organizations."
View the log file for more information. To update each organization manually, use Deployment Manager.
Is there any way to do this ?
Before this I did Update Rollup 1 in CRM2013 Deployment Server and SRS package in SQL Server Successfully and Restarted Both Servers with Windows Updates Fine, But Rollup 2 Getting Problem
Please Help Me
Run Deployment Manager and choose Organizations in the left pane. Your organizational databases should be listed in the middle pane. There is an Update column. If an organization has had the database updates applied, the Update column should show "Not Available". If one hasn't been updated, right click on the value showing in the Update column, there should be an Update option.
Hi Greg Nichols Thank You Very Much Your Reply To Me With Good Answer, As You Mentioned In The Above Lines IT Seems to Be Every Organization Showing Is "Not Available" In Update View. But What Happens To This Update Rollup-2 If I am Running This Showing The Same Message
Microsoft Dynamics CRM Server (KB2919956-V2) completed successfully. However, the database update failed for some organizations."
This Message Means Is It Successfully Updated Or Not, And I Updated The Srs Rollup-2 Pack In SQL Server It Is Successful.
Once This Rollup-2 Problem Solves Then I will Do The Rollup-3 and After That Spring-14 Is Am I Doing Right ?
Please Help Me to Solve This Rollup-2 In CRM 2013 On premises
Since MS CRM 2015 outlook client support MFA (Multi-factor authentication). In case of a CRM IFD deployment If we want to use Yubikey with Outlook client as 2nd factor of authentification. How we can achieve that. I couldn't find any documentation integration oAuth 2.0 with Outlook client.
Appreciate if you can advise on the same.