Podcast and Overview: Microsoft Dynamics CRM 2011 Update Rollup 17


Contents:

We're proud to announce that all packages for Microsoft Dynamics CRM 2011 Update Rollup 17 were released on Thursday, May 8th, 2014 to the Microsoft Download Center!  The Update Rollup 17 packages should appear on Microsoft Update in late May, 2014.

Update Rollup 17 Build number:

5.0.9690.4150

Important Note: Microsoft Dynamics CRM 2011 Update Rollup 17 is compatible with Windows 8.1 or Windows 7 and Internet Explorer 11!

This includes the following supported configurations:

  • The browser application running in Internet Explorer 11 on Windows 8.1 or Windows 7
  • Dynamics CRM for Microsoft Office Outlook when running Office 2013 on Windows 8.1

Update Rollup 17 Microsoft Download Center page

Here's the "Master" Microsoft Dynamics Knowledge Base article for Update Rollup 17: KB 2915687

On Monday, May 12th 2014 at 10 AM Pacific Greg Nichols and Ryan Anderson from the Microsoft CRM Premier Field Engineering Team provided information about:

  • The release of Update Rollup 17 for Microsoft Dynamics CRM 2011
  • New fixes made available In Update Rollup 17
  • Collateral available about Update Rollup 17 and CRM Update Rollups in general

on BlogTalkRadio during their Microsoft Dynamics CRM 2011 Update Rollup 17 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"

Go to Top

Cumulative Update Rollup Changes

Update Rollup 17 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 17 news that you need to know because Update Rollups are cumulative, so these significant changes are also in Update Rollup 17!

 UR12 included the "Microsoft Dynamics CRM December 2012 Service Update"  See:

  • Additional cross-browser compatibility provided
    • The December 2012 Service Update component of Microsoft Dynamics CRM 2011 Update Rollup 12 introduces additional browser compatibility for Firefox, Chrome, and Safari
  • Indexes added to support the Update Rollup 10 Quick Find Optimizations
    • Update Rollup 12 includes new indexes for the following entities in the Quick Find Search Optimization feature. To fully reap the benefits of the platform changes included in Update Rollup 10, indexing is needed.  The indexes created are listed below:
      • Cases
      • Opportunities
      • Competitors
      • Contact (the Phone Number fields)
      • Business Unit
      • Connection
      • Connection Role
      • KB Article
      • Lead
      • Product
      • Sales Literature
    • These indexes are created during the Update Rollup 12 installation and you may notice that part of the installation will take longer to complete. The reason for this is that the indexes need to be populated and based on the size of your dataset the completion time will vary
  • Enhancements to Activity Feeds
    • The enhancements made to the activity feeds include a new feature called Like/Unlike
    • With this feature, you can express your immediate feedback about a post
    • For more information, see Like/Unlike
  • Updated User Experience for Sales and Customer Service and Product Update Functionality for Microsoft Dynamics CRM Online
    • The Microsoft Dynamics CRM December 2012 Service Update introduces a variety of new features and functionality, including an updated user experience. For Sales and Customer Service users, the updated user experience provides a new process flow visualization, which appears at the top of the forms, such as the Opportunity , Lead or Case form. The process flow guides users through the various phases of the sales and customer service processes
    • For trials and subscriptions initiated after December 2012, the updated Sales and Customer Service user experience is included by default. Existing Microsoft Dynamics CRM Online customers have an option of adding the updated user experience to the Opportunity , Lead and Case forms by installing the Product Updates. This lets Administrators install selected feature updates based upon the specific needs of their organizations. The Product Updates are installed by using the Microsoft Dynamics CRM web application; they cannot be installed programmatically
    • For more details, see What's New for Developers for Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online
  • Custom Workflow Activities for Microsoft Dynamics CRM Online
  • Developer Toolkit Support for Microsoft Visual Studio 2012
    • The Developer Toolkit for Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online now supports Microsoft Visual Studio 2012. The installer can be found in the SDK download in the sdk\tools\developertoolkit\ folder
  • Microsoft Dynamics CRM 2011 Software Development Kit (SDK) updated December 19th, 2013 for Update Rollup 15 (version 5.0.18)
  • Bulk Data Load performance enhancements
    • To support bulk data load scenarios, this release introduces the ExecuteMultipleRequest message. This message supports the execution of multiple message requests using a single web method call. ExecuteMultipleRequest accepts an input collection of message requests, executes each of the message requests in the order they appear in the input collection, and optionally returns a collection of responses containing each message’s response or the error that occurred. Processing requests in bulk results in lower network traffic and higher message processing throughput
    • For more information, see Use ExecuteMultiple to Improve Performance for Bulk Data Load
  • Activity Feeds changes
    • Microsoft Dynamics CRM Activity Feeds provide real-time notifications and quick sharing of information through short updates. These updates appear on your personal wall in the What's New area of the Workplace . Activity Feeds enable you to follow and learn about important activities that take place around people, accounts, contacts, leads, and anything else that you care about
    • Updates can be posted manually by you, or automatically based on predefined system rules through a workflow. Activity Feeds can also be posted to by external applications through the Microsoft Dynamics CRM web services API. Activity Feeds expose Microsoft Lync real-time presence functionality so that you can initiate communication activities such as IM, phone calls, and emails. For more information, see Activity Feeds Entities
  • More performance and stability-related fixes, including fixes to the CRM Client for Microsoft Outlook
  • Contains all hotfixes / updates released in earlier Update Rollups
  • Quick Find performance optimizations and EnableRetrieveMultipleOptimization SQL query performance optimizations (originally released in Update Rollup 10)

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 are also available in the MSDN version of this whitepaper.

Go to Top

OrgDbOrgSettings Editors:

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!

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 to include setting for CRM 2011 Update Rollup 16 and CRM 2013 Update Rollup 2, and he takes pride in keeping it updated. 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

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!

Go to Top

General Update Rollup Notes:

  • Testing Update Rollups: Best Practices
    • Premier Field Engineering recommends treating Update Rollup 12 (and above) testing like testing a new, major CRM release because of the introduction of new functionality introduced with the December 2012 Service Release. Do all the standard testing like you generally do for all UR’s, but then also all the functional and performance testing that you would do with a new major release
    • 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 2011 to simulate your production user load in your testing environment, to shake out any performance-related issues early
      • Test using the permissions your end-user roles (most restrictive) 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 2011 and 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 things that reference the 2007 endpoint or other things that will go away in 2013, so it's best to start removing them now. And, most of the checks in the tool were built into the installer for CRM 2013 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 2011 Custom Code Validation Tool to identify potential issues with custom JavaScript in JavaScript libraries and HTML web resources. The Microsoft Dynamics CRM Online Q2 2012 Service Update and Microsoft Dynamics CRM 2011 Update Rollup 9 include significant changes in the web application in order to be able to support a variety of browsers such as Safari, Chrome, and Firefox. 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
  • Update Rollup 12+ require Microsoft .NET Framework 4
  • Update Rollup 6 established a new servicing baseline. This will enable uninstalls of some future CRM 2011 Update Rollups, but this also means that Update Rollup 6 is prerequisite for installation of all future Microsoft CRM 2011 Update Rollups starting with Update Rollup 7
  • A database created with Microsoft Dynamics CRM 2011 Update Rollup 6 or a higher version cannot be imported to a deployment of Microsoft Dynamics CRM 2011 Update Rollup 5 or an earlier version. This scenario is not supported.  Best practice is to import databases or customizations between environments that are at the same Update Rollup level
  • As Update Rollup 17 is cumulative, containing all changes released in earlier Update Rollup releases, it also contains the Dynamics CRM Q4 Service Update features released via Update Rollup 6.  Some of these features include:
    • Outlook Client Updates:
      • Dialog Enhancements
      • Data Visualization Enhancements:
        • Chart Designer Enhancements
        • New Chart Types
      • Data Management Enhancements to:
        • Auditing
        • Duplicate Detection
      • Activity Feeds
        • Listening in on important activities in Social Media that take place around the people, accounts, contacts, leads or opportunities that you care about, including a Windows 7.5 phone application: "Business Hub"
        • Update Rollup 5 does not install Activity Feeds:

For more information about the Dynamics CRM Q4 2011 Service Update features, consult:

Go to Top

Update Rollup 17 packages are available for download via: 

  • The Update Rollup 17 Microsoft Download Center page (released May 8th, 2014)
  • The Microsoft Update Catalog - all packages have a planned release date in late May, 2014
  • The Microsoft Update detection / installation process
    • Note: Microsoft Dynamics CRM 2011 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 Update Rollup 17 "master" Microsoft Knowledge Base article
    • Please review my teammate Shawn Dieken's superb (and recently updated) blog posting "How to install Microsoft Dynamics CRM 2011 without an Internet Connection" which provides details on how to set up an install on a machine without access to the Internet
    • Please review my former teammate Jon Strand's equally superb 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

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)

Go to Top

 Microsoft Dynamics CRM 2011 Update Rollup 17 Prerequisites:

  • Essentially the prerequisites listed in the Microsoft Dynamics CRM 2011 Implementation Guide download or online versions for the various CRM components serviced
  • You must have Microsoft Dynamics CRM 2011 Update Rollup 6 installed (build 5.0.9690.1992) to apply this Update Rollup

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 11+ and Microsoft Windows 8.x as TBD until testing is complete; generally near General Availability (GA) of that product.

Go to Top

Issues resolved via Microsoft Dynamics CRM 2011 Update Rollup 17: 

Microsoft Dynamics CRM 2011 Update Rollup 17 is the sixteenth (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 17 contains all fixes shipped via Update Rollups 1-17, including fixes that were never publicly released via Update Rollup 9.

  • A partial import is reported as a failure instead of a partial failure: The record could not be updated because the original record no longer exists in Microsoft Dynamics CRM
  • With the latest version of the CRM 2011 SDK you cannot use the Workflow activity that is part of the Windows Workflow Activities provided in the Microsoft.Xrm.Sdk.Workflow.dll in the Workflow Designer
  • ViewID for custom view is not respected when same relationship is added multiple times on form by directly editing the entity FormXML and adding different ViewID for same relationships
  • Quick Find fails with "Invalid Argument" when whole number fields are added as find columns
  • You are not able to navigate as Next Page arrow option disabled in Service Calendar Frame
  • You are not able to edit properties of a SharePoint document on Dynamics CRM when clicking on Actions -> Edit Properties
    • This message is displayed: "You must check out this item before making changes. Do you want to check out this Item now?"
    • Click on OK and then you can see a page to edit the properties of the document but when click on Save button, we receive the message:
      • "The file "File name" is not checked out. you must check out this document before making changes"
  • Recurring Series Expansion job does not complete if Recurring Appointment owner is a team
    When you create service activities and you sync those activities to your Outlook Exchange Mailbox, and you have devices like an iPhone or Windows Phone you will see UNKNOWN:UNKNOWN on the activity parties or invitees on those devices when viewing those service activities

    • This can lead to invitees getting removed from the service activity or becoming duplicated in CRM
  • Any modification to the "Goals with Same Metrics and Time Period" View loses filter on Active records
  • Bulk Edit on Cases shows an incorrect dialog box
  • Poor performance with smart matching when the Email Hash and Activity tables have a large number of records
  • Clicking the mail merge button in the Ribbon bar of the Advanced Find screen opened from the Contacts entity does not display the Mail Merge dialog
  • When adding users to a dynamic list using manage members and having a related entity link in the advanced find query to find members, the query generated doesn't execute because of duplicate table alias
  • When a User does not have permission on a folder created by Dynamics CRM record,
    • The user is redirected to the Parent SharePoint folder
    • They are able to see all folders that belongs to other Dynamics CRM entities on the SharePoint List Component when access should be denied
  • The context sensitive ribbon is not displaying in the Outlook 2011 Client when configured to a CRM 2013 deployment
  • Removing / Adding any field to the form after enabling the option "Automatically expand to use available space" causes the sub grid to shrink or resize to much smaller in size
  • Recurring appointment fails to track with exceptions outside EffectiveRange
  • When you go offline in the CRM 2011 client for Outlook running on UR11 Critical Update or UR 15+ you receive the following error:
    • An error occurred during Offline Synchronization. Try going offline again, or restart Microsoft Outlook
    • Exception happened. The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter /:args">/:args">http://<organization>/:args
    • The InnerException message was 'There was an error deserializing the object of type Microsoft.Crm.Application.Outlook.OfflineSync.SyncInfoRequest. The maximum string content length quota (8192) has been exceeded while reading XML data. This quota may be increased by changing the MaxStringContentLength property on the XmlDictionaryReaderQuotas object used when creating the XML reader.’
  • After Update Rollup 12 or greater is applied to the Outlook client, the startup time for Outlook.exe can be significantly impacted if the configured organization contains many customizations
  • Microsoft.Interop.Mapi.MAPINameId.GetHashCode module leads to an Outlook crash
  • Reports cannot be executed once the default filter form the report is removed and the update is saved. The execution fails with the following error on screen:
    • "Reporting Error: The repot cannot be displayed"
  • Outlook start-up time is impacted post Update Rollup 12
  • Outlook Quick Find does not work correctly for custom entities after Update Rollup 12
  • When users have several forms open in the Outlook Client and then open a model dialog such as a Lookup, several of the forms will be forced to the background, losing focus
  • In CRM 2011, the PostFollow(Follow) entity workflow cannot be triggered
  • When creating an activitymimeattachment using the REST endpoint and JavaScript when the Microsoft Dynamics CRM 2011 Client for Outlook is offline, the user will see an error:
    • "activitymimeattachment With Id = <GUID> Does Not Exist"
  • After applying Update Rollup 16, Solution import fails with overwriting components
  • SharePoint 2010 Integration won't work if Windows6.1-KB2894844-x64 is installed
  • An environment where the SendEmailSynchronously OrgDbOrgSetting set to 1 the message below is presented when forwarding e-mails from Outlook:
    • "A record with these values already exists. A duplicate record cannot be created. Select one or more unique values and try again. Do you want send the e-mail?
    • If you click Yes, the e-mail will be sent out, but no corresponding activity will be created in Microsoft Dynamics CRM."
  • Update to CRM UR16 fails with error: SqlException:
    • Invalid column name 'IsMapiPrivate'
  • When a manually tracked contact in Microsoft Dynamics CRM 2011 Client for Outlook is merged with another contact as a subordinate record, that contact can be incorrectly synchronized to Outlook if the Outlook Client is reconfigured
  • After installing Update Rollup 16, CRM reports embedded in IFRAME objects (on forms / dashboards /etc...) no longer display correctly when using Internet Explorer 9 or Internet Explorer 10
  • N:N relationship records are not replicated offline
  • After installing UR12+, addCustomView method from SDK fails on multi-entity lookups
    • This was previously fixed in UR 10 and UR 11 for CRM 2011
  • SDK OrganizationServiceContext fails to update a related record while in a create transaction
  • Reports cannot be executed once the default filter has been changed
  • A form has multiple tabs which are initially hidden and then made visible programmatically
    • Once the tabs are made visible, the navigation bar containing the links to other related entities moves down and part of it gets off the screen, making the users unable to see or select some links
  • Horizontal scrollbar appears on mouse over the form sections navigation pane
  • Queue emails not being tracked in CRM via the e-mail router
  • When processing async operation jobs, the CrmAsyncService crashes unexpectedly
    • Event Viewer shows that there was a problem deserializing some data to process a job:
    • Exception: System.ArgumentException: An item with the same key has already been added
      • at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
      • at System.Runtime.Serialization.DataContractSerializer.ReadObject(XmlReader reader)
  • Chart is not displayed when a subgrid is placed on the business unit entity
  • When opening and closing service activities in the Microsoft Dynamics CRM 2011 Client for Outlook, the parent ribbon for the Service Calendar will render a single blank tab
  • Untracking an email you do not own results in the email being deleted from CRM
  • After exporting the results of a Quick Find search to Excel Pivot Table, the resulting file cannot be opened. The following error appears:
    • "[Microsoft][ODBC SQL Server Driver][SQL Server]The SELECT permission was denied on the object 'AccountBase', database '...._MSCRM', schema 'dbo'."
  • Advanced Find date range with "last-x-fiscal-years" is incorrect when exported to a Dynamic Worksheet
  • Adding an out of the box optionset field for the Connection Entity in a view, causes the view to not load in the CRM Outlook client
  • When a user selects a Service Appointment in the Outlook calendar and they choose to click the Untrack button in the Microsoft Dynamics CRM 2011 Client For Outlook, users will encounter error dialogs such as:
    • Invalid ArgumentItem Name=<SubjectOfServiceActivity>
    • An error has occurred. Try this action again. If the problem continues, check the Microsoft Dynamics CRM Community for solutions or contact your organization's Microsoft Dynamics CRM Administrator. Finally, you can contact Microsoft Support.Item Name=<SubjectOfServiceActivity>
  • Cannot change owner on create of Appointment after Update Rollup 16
  • Quick campaigns are not working in Outlook client when Critical Update is installed
  • When you have an HTML web resource on a form, the web resource is removed when clicking the backspace button in Internet Explorer
  • You cannot select "Goals with Same Metrics and Time Period" view for parent goal lookup
  • Spaces used in a Grid URL cause the URL to add additional http:// to the beginning of the URL and renders as http://http://
  • When a form is opened, if a user clicks "Insert Template" before the rest of the form finishes loading, one of the following script errors might occur:
    • <ScriptErrorDetails>
    • <Message>'Mscrm.FormControlInputBehavior.GetBehavior(...)' is null or not an object</Message>
    • <Line>1</Line>
    • <URL>/_static/_controls/emailbody/emailbody.js?ver=-764166174</URL>
      or:
    • <ScriptErrorDetails>
    • <Message>Unable to get property 'Items' of undefined or null reference</Message>
    • <Line>1</Line>
    • <URL>/_static/_controls/emailbody/emailbody.js?ver=-55529662</URL>
      or:
    • <ScriptErrorDetails>
    • <Message>Object expected</Message>
    • <Line>58</Line>
    • <URL>/userdefined/edit.aspx?contactInfo=&etc=4202&pId=%7b0D1757B9-FC47-E311-BF17-
      or:
    • The value of the property 'ApplyTemplate' is null or undefined, not a Function object
  • Audit setting is disabled when changing cascading behavior
  • The AddCustomView method from SDK does not work on a multi-entity lookup as expected
  • When a manually tracked contact in Microsoft Dynamics CRM 2011 Client for Outlook is merged with another contact as a subordinate record, that contact can be incorrectly synchronized to Outlook if the Outlook Client is reconfigured
  • When doing a multi-select lookup of an unresolved email address in CC the email address are not properly transferred to the dialog. Subsequently changes to the addresses in the dialog are not copied back to the form and some are removed
  • When you invite multiple CRM users to a meeting in the Outlook client and that meeting is recurring and you do not initially track the meeting, each CRM user could track that meeting resulting in duplicate recurring appointments in CRM for the same meeting causing confusion
    • This can also result in problems with the scheduling engine showing that a resource is not available, when in fact they are not available since the meeting which is blocking is the same meeting attempted to be created
  • Dynamics CRM users are unable to add more than one Document Location when the document location is based on an entity centric structure, like: Account/<accountname>/opportunity/<opportunityname>
    Users attempting to delete the oldest audit log in Microsoft Dynamics CRM 2011 after Update Rollup 12 receive the following error:

    • "You can only delete the oldest audit log"
  • The CRM Outlook client first looks locally for an icon. If the icon does not exist local it makes an asynchronous request to the server and when the response comes back caches it locally for future reference
    • The cache location is *local appdata*/Microsoft\MSCRM\Client\IconCache
      • In this scenario the request made to obtain the custom entity custom 16x16 grid icon doesn't have an orgname in the URL
      • This results in HTTP 401 and 500 errors
  • Recurring Series Expansion job does not complete if Recurring Appointment owner is a team
  • Activity Types change when importing Solutions. As a result a view on the Activity entity that references the custom activity entity stops working
    • Warning message on the filter: This condition had one or more list values that no longer exist in the system
  • After applying Update Rollup 16 in Microsoft Dynamics CRM 2011, users are unable to remove Deployment Administrators if the account exists in a separate domain.
  • After installing Update Rollup 12, there are changes to the Microsoft Dynamics CRM 2011 forms that may impact the visually impaired such as lighter colors and the absence of highlighting on items such as the SiteMap and Tab titles
  • When users have several forms open in the Outlook Client and then open a modal dialog such as a Lookup, several of the forms will be forced to the background, losing focus
  • When going online in Outlook, the view duplicates window for the record appears, but the value for lookup and optionset attributes will not be shown in offline record grid
  • Users of the Microsoft Dynamics CRM 2011 Client for Outlook may experience issues where shared personal views may not show up on entity grids if the views had been shared or unshared previously
  • Fonts with spaces are ignored in CRM reports
  • After installing Update Rollup 10, 11, or 12, file attachments for emails get a contentId appended to them
  • If file name is mywordfile.doc, then the file attachment in CRM will show {cid:somecontentid@somedomain}mywordfile.doc
  • The newly-released SharePoint List Web Part will cause the Document Management functionality to hang on the loading circles when configured on a SharePoint 2010 server
  • If the number of notes on a record exceeds the records per page set in a user personal options, you will not be able to see the additional notes in the control
    • For example, if the records per page is set to 25, and you have 26 notes on the record, you will not be able to see the first note
    • Prior to Update Rollup 12 the Notes Control had "Add a new note..." and "Show more notes" hyperlinks on the notes control.”Show more notes" would allow you to display the next page of notes in the notes control
  • Microsoft.Interop.Mapi.MAPINameId.GetHashCode module leads to Outlook crash
  • Clicking the mail merge button in the Ribbon bar of the Advanced Find screen opened from the Contacts entity does not function
  • When you attempt to deploy a mailbox rule using the forward mailbox rule deployment wizard, with a split deployment for Exchange 2010 where your mailbox servers are not client access servers, you receive an error:
    • Failed to access the default store for the user
  • After Update Rollup 4 of Microsoft Dynamics CRM 2011, exports of fetch based reports to Excel gave users to ability to include an unformatted column of data to allow for calculations in Excel
  • Even though the print preview fits one page, a blank page 2 is printed

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 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:
    • Update Rollup 1: no updates requiring manual configuration
    • Update Rollup 2 for Microsoft Dynamics CRM 2011 contains the following update that you must enable or configure manually - details on enabling or configuring can be found in this Microsoft Knowledge Base article:
      • 2535245 RetrieveMultiple optimization for basic depth needed for local and deep depth read privileges in Microsoft Dynamics CRM 2011
      • NOTE: see comments near the beginning of this blog regarding significant rework to EnableRetrieveMultipleOptimization released in Update Rollup 10
    • Update Rollup 3: no updates requiring manual configuration
    • Update Rollup 4: no updates requiring manual configuration
    • Update Rollup 5: no updates requiring manual configuration
    • Update Rollup 6 for Microsoft Dynamics CRM 2011 contains the following update that you must enable or configure manually - details on enabling or configuring can be found in this Microsoft Knowledge Base article:
      • 2664150  Steps to clean up the PrincipalObjectAccess table in Microsoft Dynamics CRM 2011 after Update Rollup 6 is applied
    • Update Rollup 7: no updates requiring manual configuration
    • Update Rollup 8: no updates requiring manual configuration
    • Update Rollup 10 (includes hotfix components of Update Rollup 9): no updates requiring manual configuration to enable, but
      • Note my above comments regarding ERMO (EnableRetrieveMultipleOptimization) option configuration via registry keys or (preferred) OrgDbOrgSettings updates
      • This information supercedes the information in KB 2535245, which discusses EnableRetrieveMultipleOptimization enhancements shipped in CRM 2011 Update Rollup 2
    • Update Rollup 11 for Microsoft Dynamics CRM 2011 contains the following update that you must enable or configure manually - details on enabling or configuring can be found in this Microsoft Knowledge Base article:
      • 2820838 Microsoft Dynamics CRM E-mail Router Rule Deployment Wizard does not work in an Exchange 2003 and Exchange 2010 mixed environment
    • Update Rollup 12 for Microsoft Dynamics CRM 2011 contains the following update that you must enable or configure manually - details on enabling or configuring can be found in this Microsoft Knowledge Base article:
      • 2820835 Sync the private property from Outlook appointments to Microsoft Dynamics CRM 2011 with Update Rollup 12
    • Update Rollup 13: no updates requiring manual configuration
    • Update Rollup 14: no updates requiring manual configuration
    • Update Rollup 15: no updates requiring manual configuration
    • Update Rollup 16: no updates requiring manual configuration
    • Update Rollup 17 for Microsoft Dynamics CRM 2011 contains the following update that you must enable or configure manually:
      • When you attempt to deploy a mailbox rule using the forward mailbox rule deployment wizard, with a split deployment for Exchange 2010 where your mailbox servers are not client access servers, you receive an error: Failed to access the default store for the user. To enable this fix,
        • On the Email Router machine, add a new String value Key named "CASServerName" in the path HKEY_Local_Machine\Software\Microsoft\MSCRMEmail, then:
        • Enter the NetBIOS name of one of the Exchange CAS servers

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 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
Senior Premier Field Engineer
Microsoft Corporation

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

CRM2011UR17_PFEPodcast.mp3

Comments (0)

Skip to main content