Podcast and Overview: Microsoft Dynamics CRM 2013 Update Rollup 2


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:

  • The release of Update Rollup 2 for Microsoft Dynamics CRM 2013
  • New supporting Microsoft technologies supported in CRM 2013 via Update Rollup 2
  • New fixes made available In Update Rollup 2

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,

  • View the Podcast in Compatibility View
    • in IE 11, select Tools (the upper right "Gear" icon) -> Compatibility View Settings -> add the blogtalkradio.com website, or
  • Use the "New Window" link on the Blogtalkradio page

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

  • They were released via CRM 2011 Update Rollup 15 and the Critical Update for Microsoft Dynamics CRM 2011 Update Rollup 11 CRM Server and CRM for Outlook Client
  • These post-Update Rollup 14 changes WERE included in the RTM version of CRM 2013, and include:
    • A feature that moves the CRM client-specific workload into its own process so that it no longer shares memory with the Microsoft Office Outlook process
      • This feature is also known as Process Isolation
    • An upgrade to Microsoft SQL Server for Windows CE 4.0 for better memory management, better caching, and connection enhancements
    • Updates to CRM for Outlook configuration files to make the CRM for Outlook SDF files compatible with SQL Server for Windows CE 4.0
    • Materialization of the Address Book Provider to reduce performance issues that are caused by large address books
    • Limits to the amount of active open forms
    • A MAPI Lock time-out
    • Hard coding of a previous registry setting that prevented pinned views from pulling down information to local SQL CE cache

Go to Top

General Upgrade Rollup Notes:

  • Testing CRM 2013 Update Rollups: Best Practices
    • Microsoft Dynamics CRM Premier Field Engineering recommends doing all the standard testing you generally do for all Update Rollups, which could be the functional and performance testing that you would do with a new major release or a subset of that test plan
    • The “general rule of thumb” for test plans for Update Rollup installs are:
      • Test any changes in a pre-production environment BEFORE introducing into your production environment. Manage your risk!
      • Consider using the Performance Toolkit for Microsoft Dynamics CRM to simulate your production user load in your testing environment, to shake out any performance-related issues early. The CRM 2011 version is currently being evaluated against CRM 2013
      • Test using the permissions your most restrictive end-user roles have. Testing with CRM Administrator permissions, for example, does not give you the complete picture
      • Concentrate on your SDK customizations, JavaScript, ISV add-ons – basically anything that’s not OOB functionality or customizations done from within the UI

Microsoft Dynamics CRM 2013 Custom Code Validation Tool

  • Consider familiarizing yourselves with this tool!
  • The Custom Code Validation tool for CRM 2013 is mostly the same as the Code Validation Tool for CRM 2011 UR12; the 2011 version has been deprecated and is no longer available. We added some additional checks for code that references the 2007 endpoint or other functionality that has been deprecated in CRM in 2013. And, most of the checks in the tool were built into the CRM 2013 Server installer as validation checks
  • Note that the URL for the CRM 2011 version of the tool now directs to the CRM 2013 version
  • Use the Microsoft Dynamics CRM 2013 Custom Code Validation Tool to identify potential issues with custom JavaScript in JavaScript libraries and HTML web resources. When using JavaScript code in Dynamics CRM, it is possible that some code will stop working or cause an error when you upgrade. The Microsoft Dynamics CRM 2011 Custom Code Validation Tool helps identify potential problems so that a developer can fix them

Go to Top


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!

This is a FREE downloadable tool - the "Dynamics CRM 2011 Organization Settings Editor".  Check it out; the download page has screenshots and information that will help you make good use of the tool.  Sean has also published a Premier Field Engineering blog: "Azure Mobile + JavaScript + WebResources = Easy Editing of OrgDBOrgSettings in Dynamics CRM 2011!" to share more details on the tool. It is currently updated with settings for CRM 2011 Update Rollup 16 and CRM 2013 Update Rollup 1, and he takes pride in keeping it updated as new Update Rollups are released. Thanks, Sean!

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.

Go to Top

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

  • Client packages installed manually by downloading the packages and running install will require local administrator privileges. If the client packages are installed via Microsoft Update or SCCM (System Center Configuration Manager), they will not require local administrator privileges
  • Consider using Windows Server Update Services (WSUS) or similar software distribution technologies to distribute Dynamics CRM Update Rollups internally.  WSUS is a locally managed system that works with the public Microsoft Update website to give system administrators more control. By using Windows Server Update Services, administrators can manage the distribution of Microsoft hotfixes and updates released through Automatic Updates to computers in a corporate environment
  • For help with installation please see the Installation Information section of the Service Pack 1 Update Rollup 2 "master" Microsoft Knowledge Base article
  • Please review my former teammate Jon Strand's blog posting "CRM 2011: Silently Installing Update Rollups" which provides details on installing CRM Outlook client update rollups "silently" in order to limit end-user interruption, which also applies to CRM 2013 and CRM 2015 Update Rollups and Service Packs

Go to Top

Microsoft Dynamics CRM 2013 Update Rollup 2 Prerequisites:

  • Essentially the prerequisites listed in the Microsoft Dynamics CRM 2013 Implementation Guide download for the various CRM components serviced

Go to Top

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:

  • CRM 2013 Outlook filtering does not work after you perform a quick find search
  • When you use Internet Explorer 8, the related record dropdown is missing when a record is opened
  • When you use the Upgrade Wizard, an error message is shown with a red flag in the System Checks window: "The product key is not compatible with the installed version of Microsoft Dynamics CRM"
  • Upgrade does not create relationship for custom activity entities to mailbox_sendermailboxid
  • When you run the email router to process incoming email, some email may be skipped. This occurs if the email in Exchange Server has a different message class than the IPM.Note default
  • When you try to use a view that has a condition for Owner Equals Current User's Teams and the user does not belong to any team that has a security role, you receive an error:
    • Invalid Argument
  • When you click the hyperlink in a lookup field after you focus in the field, you receive a script error
  • When you create a recurring appointment that has exactly 16 occurrences, only 15 occurrences are created. When you create 17 occurrences or more (or 15 occurrences or less), the correct number of appointments are created
  • Microsoft Dynamics CRM 2013 has inconsistent behavior, depending on the place from which the case is resolved:
    • When you click Resolve Case from the entity Form, the Resolution (subject) that is passed in by the end-user is replaced by the generic phrase "Resolve Case."
    • When you click Resolve Case from the Grid, Microsoft Dynamics CRM saves the value that was provided by the end-user
      • In Microsoft Dynamics CRM 2011, the value was provided by the end-user and not overridden by CRM
  • When you view completed activities, such as email, you cannot select any text on the record
    • This includes the body control
  • Users of the offline edition of the Microsoft Dynamics CRM Client for Outlook cannot configure their Offline Scheduled Sync settings under Personal Settings
  • Depending on the placement of an option set field in a section of the Microsoft Dynamics CRM 2013 form, the number of visible options is limited, and the user has to scroll to see the remaining options
  • After you upgrade Microsoft Dynamics CRM 2011 to Microsoft Dynamics CRM 2013 or import Microsoft Dynamics CRM 2011 appointment customization, you receive a pop-up error message while you are saving appointments:
    • There was an error with this field’s customized event
    • Field:crmform
    • Event:onsave
    • Error: Object doesn't support property or method 'Form_onsave'
  • Field alignment setting is not respected on Microsoft Dynamics CRM 2013 forms
  • You cannot customize YomiName fields because the detail form does not display
  • Copying and pasting multiple lines of text from a Microsoft Word document to the body of a Microsoft Dynamics CRM email activity record causes additional line breaks to be inserted between each line
  • When you use the Chrome browser to view duplicate detection rules in Microsoft Dynamics CRM 2013, the criteria are not shown every time that you open the record
    • You may have to close and then reopen the record an undetermined number of times before the criteria are shown
  • The Client for Microsoft Office Outlook client is unresponsive during startup
  • When you save or send an email from the Microsoft Dynamics CRM 2013 web client in an email activity that had a template inserted, the body is saved or sent with nothing in it
    • If you edit the email body after you insert the email template, or if you use the insert template button on the email editor toolbar, the body is saved or sent correctly
  • When you use Internet Explorer 8, the related record dropdown is missing when a record is opened
  • After you upgrade or install Microsoft Dynamics CRM 2013 when you create a telephone call activity from an existing contact or lead, the telephone number field is not populated correctly
    • This behavior is different from what occurred in Microsoft Dynamics CRM 2011
  • Outlook saved views are not sorted alphabetically as they are in the web client
    • Outlook saved views should be sorted exactly as they are in the web client
  • Deadlocks occur when an Associate request is called to add users to teams
  • Custom entity grid icon is not visible in Outlook
  • A large number of notes cause the focus to be lost when you create new notes
  • Custom reports that aggregate with a groupby on OptionSet fields display:
    • #Error
  • When a user searches for a string of numbers that exceed the upper bound of the whole number column in Microsoft SQL Server, the following error is returned to users, and the search is ended:
    • "Invalid Argument"
  • Field security on check boxes causes JScript error when you save
  • When you have a web resource that should be shown across the width of a section, and you change the visibility of the web resource, the width is reduced by half
  • Incorrect "Do Not Allow" notification is generated on Phone Call/Email
  • Subgrids update continuously with a "Loading..." message
  • Consider the scenario in which using Microsoft Dynamics CRM 2013 affects synchronous plug-ins or synchronous workflows to perform an update of the StateCode and StatusCode of Activity entity:
    • The StateCode and StatusCode action is taken Post-Create synchronously then an exception occurs on the Save
    • When the same plugin code registered asynchronously, it will process and complete without error
  • Query Builder error occurs when you use addCustomView that contains a related attribute
  • When you set IME mode on an attribute on an entity to ACTIVE, the IME mode is not honored
    • This occurs with Single Line of Text, Multiple Lines of Text, and other attributes that are bound to input elements or text area elements
  • After you paste a numbered list into the email body control and convert the pasted content to a bulleted list, the bullets are misplaced above the selected text
    • The bullets will appear on their own separate line, even though there is no line break
    • Additionally, the text cannot be moved up to the bullet so that both the text and the bullet appear on the same line
  • Personal View is removed when Show Selected Views is used on Dashboard Grid after redraw
  • Time Format selection is not reflect correctly in setting
  • Unexpected format changes occur when you create mail messages from an email template
  • Users who have no Create permissions but has Read, Write, Append, and Append To permissions cannot select an Entity record that has an N:N relationship
    • This occurs for both custom-to-custom and system-to-custom entities:
      • Unable to get property 'get_element' of undefined or null reference
      • SCRIPT5007: Unable to get property 'get_element' of undefined or null reference
      • File: inlineeditcontrols.js, Line: 1, Column: 89186
  • When you import an updated solution that contains lots of entities, the import is not completed in Microsoft Dynamics CRM 2013
  • If a user presses the Enter key in the body and then presses the Delete key when the user is replying to email activity records in the application, a line break is inserted into the body of the form
  • The mailbox (CRM User) has been disabled for synchronizing appointments, contacts, and tasks due to unknown error
    • The owner of the associated email server profile (Profile Name) has been notified
  • When you review Microsoft Dynamics CRM client for Outlook tracing, the tracing incorrectly suggests that an item was being updated when in fact it was being created in Outlook from a synchronized CRM Microsoft Dynamics CRM item such as a contact, appointment, or service activity

Go to Top

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:

Go to Top

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:

  • Update Rollup 1: no updates requiring manual configuration
  • Update Rollup 2: no updates requiring manual configuration

Go to Top

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

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 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 Engineer
Microsoft Corporation


































Comments (9)

  1. Sheenam Jindal says:


    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?

  2. Greg Nichols says:

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

    Greg Nichols

    Microsoft Corporation

  3. Xander says:

    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!

  4. Lei says:

    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!

  5. Greg Nichols says:

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

    Greg Nichols

    Microsoft Corporation

  6. siva says:

    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

  7. Greg Nichols says:

    @ Siva…

    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.

    Greg Nichols

    Microsoft Corporation

  8. Siva says:

    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



  9. Oauth 2.0 outlook client 2015 says:


    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.



Skip to main content