We're proud to announce that Microsoft Dynamics CRM 2011 Update Rollup 10 released Thursday, August 16th, 2012!
Here's the "Master" Microsoft Dynamics Knowledge Base article (KB 2710577)
On Friday, August 17th, Greg Nichols and Ryan Anderson from the Microsoft Premier Field Engineering team provided information about:
during their Microsoft Dynamics CRM 2011 Update Rollup 10 Podcast
Big Update Rollup 10 news!
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.
Where is Update Rollup 9?
Update Rollup 9 for Microsoft Dynamics CRM 2011 will not be released publically because of a delay in the Q2 Service Update, which was to be included in Update Rollup 9. For more details, see the blog "Q2 2012 Service Update – New delivery schedule"
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.
Feature Additions in Update Rollup 10, also available in Update Rollup 7 and 8!
Update Rollup 7 for Microsoft Dynamics CRM 2011 introduced a new feature known as Read Optimized Forms. Read Optimized Forms allow a user to quickly open a read-only copy of a record form. Read Optimized Forms improve performance for users who have high network latency and users who spend most of their time consuming information instead of editing. Form loads are faster because of the removal of the ribbon, navigation pane, web resources, and form scripting. However, you can still open the standard editable form if changes have to be made. The ability to default to using the Read Optimized Forms can be set at the Organization level, but is also controlled per user to meet individual needs. For more information about Read Optimized Forms, see "Customize Entity Forms in Microsoft Dynamics CRM"
Update Rollup 10 Build number:5.0.9690.2730
Update Rollup 10 can be uninstalled, unlike Update Rollups 4-6 which could not be uninstalled. However, you should always back up your databases and application servers before you install an Update Rollup.
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.
Note: As Update Rollup 10 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 5. Some of these features include:
For more information about the Dynamics CRM Q4 2011 Service Update features, consult:
For more information about the Dynamics CRM Q4 2012 Service Update features, consult:
Packages are available for download via:
for these CRM components:
NOTE: As of Jan. 20th, 2012 these installation files have been updated to include CRM 2011 Update Rollup 6 (Build 05.00.9690.1992)
Microsoft Dynamics CRM 2011 Update Rollup 10 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 and Microsoft Windows 8 as TBD until testing is complete; generally near General Availability (GA) of that product.
Issues resolved via Microsoft Dynamics CRM 2011 Update Rollups:
Microsoft Dynamics CRM 2011 Update Rollup 10 is the tenth (or ninth, 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 10 contains all fixes shipped via Update Rollups 1-10, including fixes that were never publicly released via Update Rollup 9.
Hotfixes and updates that were released as individual fixes before Update Rollup 10 release:
The following issues were fixed and delivered to requesting customers prior to Update Rollup 10 release as Critical On Demand (COD) fixes:
Other fixes released via CRM 2011 Update Rollup 10:
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 10 contains all fixes previously released via Update Rollups 1-9 as well as fixes newly released via Update Rollup 10. So if you install Update Rollup 10 on a machine upon which you previously installed no Update Rollups, you will need to manually enable any desired fixes for Update Rollups 1-10:
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. 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"
Internet Explorer 9 and 10 Compatibility
The Microsoft Dynamics CRM Sustained Engineering team has extensively tested Microsoft Dynamics CRM 2011 against pre-release versions of Internet Explorer 9 and 10 and continues to address compatibility issues, as appropriate, against the RTW (Released to Web) versions of Internet Explorer. When necessary, Microsoft plans to release enhancements via future Microsoft Dynamics CRM 2011 Update Rollups to assure compatibility with future releases of Internet Explorer.
Greg NicholsPremier Field EngineeringMicrosoft Corporation
Great to get support for IE10 & Win 8 - when will these be supported in CRM Online?
@ Roger - TBD on the CRM Online story, I don't have much visibility into that. I work with a few Online customers but my focus is on the On-Premise version.
As I mentioned in my podcast this morning, keep an eye on the "Microsoft Dynamics CRM Compatibility List":
support.microsoft.com/.../2669061 - per product, it has hyperlinks to underlying Knowledge Base articles that describe the nature of support / compatibility for these new products as of CRM 2011 Update Rollup 10:
Support with Microsoft Dynamics CRM 2011 and Windows 8: support.microsoft.com/.../2744954
Support with Microsoft Dynamics CRM 2011 and Internet Explorer 10: support.microsoft.com/.../2743941
Support with Microsoft Dynamics CRM 2011 and Microsoft Office 2013 Preview: support.microsoft.com/.../2744957
After installing the rollup 10, I can not enter the CRM. Every time I try to enter my organization fails. This is error appears in event viewer:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 8/20/2012 10:37:58 AM
Event time (UTC): 8/20/2012 8:37:58 AM
Event ID: 76d79d6117bc4eac942d697b1193d2ad
Event sequence: 3
Event occurrence: 1
Event detail code: 0
Application domain: /LM/W3SVC/3/ROOT-1-129899254201817927
Trust level: Full
Application Virtual Path: /
Application Path: C:\Program Files\Microsoft Dynamics CRM\CRMWeb\
Machine name: CRMDEV-VPC
Process ID: 2652
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception type: MissingMethodException
Exception message: Method not found: 'Void Microsoft.Xrm.Sdk.Query.FilterExpression.set_IsQuickFindFilter(Boolean)'.
at Microsoft.Crm.BusinessEntities.QueryFromLegacyQueryVisitor.Visit(FilterExpression filter)
at Microsoft.Crm.BusinessEntities.QueryFromLegacyQueryVisitor.Visit(QueryExpression query)
at Microsoft.Crm.BusinessEntities.ConversionHelpers.ConvertIfQueryExpression(Object source, Type destinationType)
at Microsoft.Crm.BusinessEntities.ConversionHelpers.Convert(ICrmConversionContext conversionContext, Object source, Type destinationType)
at Microsoft.Crm.Application.Platform.ServiceCommands.RetrieveMultipleCommand.CreateQueryRequest(QueryBase query, Boolean retrieveLatest)
at Microsoft.Crm.Application.Caching.CustomResourceLoader.GetCustomResources(IOrganizationContext context, Int32 cacheKey)
at Microsoft.Crm.Application.Caching.CustomResourceLoader.LoadCacheData(Int32 key, IOrganizationContext context)
at Microsoft.Crm.Caching.CrmMultiOrgCache`2.LookupEntry(TKey key, IOrganizationContext context)
at Microsoft.Crm.Application.ResourceManager.CustomResourceManager.TryGetCultureString(String name, CultureInfo culture, Boolean getSystemString, IOrganizationContext context)
at Microsoft.Crm.Application.ResourceManager.CustomResourceManager.TryGetCultureString(String name, CultureInfo culture, IOrganizationContext context)
at Microsoft.Crm.Application.ResourceManager.BasicResourceManager.GetCultureString(String name, CultureInfo culture, IOrganizationContext context)
at ASP.avanadecrmdev_main_aspx.__BuildControlTree(avanadecrmdev_main_aspx __ctrl)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Request URL: http://XXXXX/XXX/main.aspx
Request path: /XXXXXX/main.aspx
User host address: fe10::32fc:f0ef:fd1a:4300NT AUTHORITY\NETWORK SERVICE
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread ID: 8
Is impersonating: True
Stack trace: at Microsoft.Crm.BusinessEntities.QueryFromLegacyQueryVisitor.Visit(FilterExpression filter)
at ASP.comun_main_aspx.__BuildControlTree(comun_main_aspx __ctrl)
Custom event details:
@Jose - the error message you're receiving is a "MissingMethodException" indicating that your DLL's are not properly in sync (the calling DLL is looking for a function that doesn't exist in the target dll - meaning the versions are likely mismatched). Either the update rollup failed to install properly, the dll update was skipped, or there is an old version of the DLL in the GAC. First off, I would make sure you remove all Microsoft.Crm dll’s from the GAC as this is not required and can cause issues like you’re seeing. Second, I would try installing UR10 one more time to make sure everything is installed properly, you can check the version numbers of the organizations in deployment manager and check the version numbers of the DLL's in file explorer. Finally, if all else fails I would either: contact Support for assistance or run a repair on CRM 2011 and re-patch to make sure you have all the files in place.
Having exact same issue as Jose. I have tried to install RU10 without any luck. I also don't have Microsoft.Crm dll in GAC
The server is windows 2008 R2. SQL 2008 R2
We experienced issues where Outlook would no longer open after the patch was applied. We saw the following errors in a CRM diagnostic trace on the system. We had to uninstall the RU10 to get folks back online.
[2012-08-27 16:09:03.829] Process:OUTLOOK |Thread:9060 |Category: Unmanaged.Platform |User: PlatformUser |Level: Info | Reading registry key 0B1A001A-9351-43d0-A6C0-44A8D711E020 failed Function: FReadDWORDRegKeyValue File: c:\bt\40250\src\application\outlook\addin\..\Common\utility.h Line: 223
>Unhandled Exception in MAPIInterop: Microsoft.Crm.MapiStore.MapiServiceEntryPoints+KnownStackTraceException: Error in the application.
at Microsoft.Crm.MapiStore.MapiServiceEntryPoints.MapiApplication_MapiUnhandledException(IntPtr ep)
at ExceptionFilter(_EXCEPTION_POINTERS* ep)
at Microsoft.Crm.MapiStore.ContentsTable.QueryPosition(Int32& Row, Int32& Numerator, Int32& Denominator)
at Microsoft.Interop.Mapi.MAPITableImpl<IMAPITable,Microsoft::Interop::Mapi::IMAPITable>.QueryPositionManaged(MAPITableImpl<IMAPITable\,Microsoft::Interop::Mapi::IMAPITable>* , UInt32* pulRow, UInt32* pulNumerator, UInt32* pulDenominator)
Will report to Watson as Native Exception.
Below are the errors from the Event Viewer on the server where the login was not working.
Log Name: Application
Source: Windows Error Reporting
Date: 8/27/2012 5:30:33 AM
Event ID: 1001
Task Category: None
Fault bucket , type 0
Event Name: CRMUnmanaged
Response: Not available
Cab Id: 0
These files may be available here:
Rechecking for solution: 0
Report Id: fc7e230f-f042-11e1-b9e4-0050569e00a9
Report Status: 0
Log Name: Application
Date: 8/27/2012 5:20:48 AM
Event Name: APPCRASH
Report Id: a0e7157d-f041-11e1-b9e4-0050569e00a9
Source: Application Error
Date: 8/27/2012 5:20:47 AM
Event ID: 1000
Task Category: (100)
Faulting application name: OUTLOOK.EXE, version: 12.0.6661.5003, time stamp: 0x4fa2a9e1
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e211319
Exception code: 0xe0434352
Fault offset: 0x0000b9bc
Faulting process id: 0x234c
Faulting application start time: 0x01cd844e55bba195
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office12\OUTLOOK.EXE
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Source: MailMeter Outlook AddIn
Date: 8/27/2012 5:03:19 AM
Event ID: 0
[MailMeter Outlook AddIn]OutlookInterface.OutlookInterface_FolderSwitch: An exception occurred: Exception=[System.NullReferenceException: Object reference not set to an instance of an object.
at AddinCode.FolderManager.GetSearchFor(MAPIFolder folder)
In my scenario the following error message with UR 10 got resolved following below resolution:-
MSCRM Error Report:
Error: Method not found: 'Void Microsoft.Xrm.Sdk.Query.FilterExpression.set_IsQuickFindFilter(Boolean)'.
Error Message: Method not found: 'Void Microsoft.Xrm.Sdk.Query.FilterExpression.set_IsQuickFindFilter(Boolean)'.
We registered the dlls by taking the following steps:
1. Install SDK for .NET 4.0 at www.microsoft.com/.../details.aspx.
2. Open a command prompt and cd to C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\NETFX 4.0 Tools
3. Register the Microsoft.Xrm.Sdk.dll and Microsoft.Crm.Extensibility.dll files by running the following commands:
gacutil.exe -I "C:\Program Files\Microsoft Dynamics CRM\CRMWeb\bin\Microsoft.Xrm.Sdk.dll"
gacutil.exe -I "C:\Program Files\Microsoft Dynamics CRM\CRMWeb\bin\Microsoft.Crm.Extensibility.dll"
4. Perform an IISRESET.
Thanks for the knowledge and keeping the field folks up-to-date!
@Arpita, @Jose, & @Jaimie - please do not register the DLL's in the GAC, most likely you've somehow deleted or replaced a version of a CRM platform DLL with an older version or a version the installer was not expecting thus it will skip patching the file. When you add it to the GAC you'll give the platform one more place to find the right version - but in the next UR you may run into the same issue again and be in a worse position than you are now. To properly address this you have a couple options:
1. Open a support ticket - support has a utility they can run that will report the various DLL versions and can help you identify which DLL is incorrect. If you're engaged with PFE/Premier we can assist as well.
2. Find the DLL's yourself by looking in each folder and adding the version number to the display of the detailed explorer view
3. The final option is to run a repair of CRM to reset the DLL versions.
If you have your CRM DLL's in the GAC - remove them so that there are no version mismatches or conflicts.
It appears that Rollup 10 has killed the 2007 CRM Discovery Service endpoints used by many third party products in organizations using IFD on a secured site. Any idea if a workaround exists for us to keep using these products without uninstalling Rollup 10?
For those of you who have installed RU10 and Outlook instantly crashes, there is a known issue with RU10 and SQL CE 4.0. It mostly affects people in terminal server (e.g. Citrix) environments where the servers are running SQL CE 4.0. I burned a support ticket to find out it was a known (but not publicly released) issue. The bigger problem is that Microsoft is not planning on publicly announcing a fix for this so I'm not sure yet how to get the new patch. They apparently have some "large" customers who cannot install RU10 becuase of the SQL CE 4.0 problem so they are working on a fix. In the mean time, leave RU8 in place. Its a good thing they have large customers complaining or the fix would probably come in the next major RU.