Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We experience an error in Outlook Client for MS CRM 2011 (on-premise) in Online mode when navigating in views on the homepage for any entity (custom and vanilla). Does anyone experience the same problem and knows the root cause and / or has a possible solution?
Steps to Reproduce:
- Select an entity from the navigation on CRM homepage (e.g. Account).
- Create a view with at least to columns of any type and a result set with more than 500 records. Select two sorting columns for the view.
- Open the view in the homepage (regardless if it is pinned or not).
- Counter in the view displays the correct total number of records returned in the view.
- Use paging to navigate to the next pages of the view
Problem:- Either paging is not possible anymore after some pages and user cannot see all records in the view or paging is possible for more records than the total number of records.
Further information:- Behavior can be reproduced with Windows 7 and Windows 10.
- View can be opened in Advanced Find and everything is working correctly
- Warnings are available in client trace. I pasted it below.
Assumptions after first analysis:- View paging may have been negatively impacted by a recent Outlook / Office patch issued by Microsoft.
- DisableMapiCaching is set to True in the OrgDBSettings and a change does not influence the behavior. Maybe interfering with KB4011637 where it says "Third-party MAPI providers may be blocked despite being in the Outlook profile."
Warning from Outlook Client Trace:
CrmPageContext.Microsoft.Crm.Outlook.IManagedBrowserShell.GetParameter ilOffset = 0x5E8 at CrmPageContext.Microsoft.Crm.Outlook.IManagedBrowserShell.GetParameter(String name) ilOffset = 0x5E8 at <>c__DisplayClass33.<Microsoft.Crm.Outlook.IManagedBrowserShell.GetParameter>b__31() ilOffset = 0x11 at ExceptionFilter.TryFilterAllNoCatch(Func`1 body, Action`1 filter) ilOffset = 0xF at ManagedBrowserShell.Microsoft.Crm.Outlook.IManagedBrowserShell.GetParameter(String name) ilOffset = 0x2C at RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor) ilOffset = 0xFFFFFFFF at RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object parameters, Object arguments) ilOffset = 0x16 at RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture) ilOffset = 0x7A at RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object args, Boolean byrefModifiers, Int32 culture, String namedParameters) ilOffset = 0xFFFFFFFF at RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object providedArgs, ParameterModifier modifiers, CultureInfo culture, String namedParams) ilOffset = 0x1EC at CrmPageContext.ExecuteScriptFunctionInternal(IHTMLDocument2 document, String functionName, Object arguments) ilOffset = 0x3E at <>c__DisplayClassa.<ExecuteScriptFunction>b__8() ilOffset = 0x0 at ExceptionFilter.TryFilterAllCatch(Func`1 body, Action`1 filter, TResult resultIfFailed) ilOffset = 0xF at <>c__DisplayClassa.<ExecuteScriptFunction>b__7() ilOffset = 0x60 at RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor) ilOffset = 0xFFFFFFFF at RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object parameters, Object arguments) ilOffset = 0x39 at Delegate.DynamicInvokeImpl(Object args) ilOffset = 0x24 at Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme) ilOffset = 0xCF at Control.InvokeMarshaledCallbackHelper(Object obj) ilOffset = 0x35 at Control.InvokeMarshaledCallback(ThreadMethodEntry tme) ilOffset = 0x4F at Control.InvokeMarshaledCallbacks() ilOffset = 0x62 at Control.MarshaledInvoke(Control caller, Delegate method, Object args, Boolean synchronous) ilOffset = 0xF8 at Control.Invoke(Delegate method, Object args) ilOffset = 0xD at Control.Invoke(Delegate method) ilOffset = 0x3 at OutlookInstanceCache.MainThreadInvoke(Delegate method) ilOffset = 0x0 at CrmPageContext.ExecuteScriptFunction(String functionName, Object arguments) ilOffset = 0x27 at CrmOutlookWebContextExtensionMethods.ExecuteScriptFunctionAndCatchWebContextExceptions(ICrmOutlookWebContext context, String functionName, Object arguments) ilOffset = 0x18 at RibbonActionHandler.GetEnabled(String command, String id) ilOffset = 0x2F at BaseFrameWindowWrapper.RibbonGetEnabled(String command, String id) ilOffset = 0x0 at ExplorerWrapper.RibbonGetEnabled(String command, String id) ilOffset = 0x0 at GlobalRibbonSupport.ExplorerServerButtonGetEnabled(IRibbonControl ribbonControl) ilOffset = 0x39 at OutlookInstance.Microsoft.Crm.Application.SMWrappers.IOutlookInstance.ExplorerServerButtonGetEnabled(IRibbonControl ribbonControl) ilOffset = 0x1GetParameter was called with unhandled parameter 'enableFilters'.
Can you provide details of the version of the Outlook Client and Outlook?
Keep in mind that CRM 2011 is out of mainstream support, so even if this is a bug, it is not 100% it will actually get fixed..
Thank you very much for your reply. The versions are as followed:
Windows: Version 10.0.14393 Build 14393
MS CRM: 5.0.9690.4376 (CRM 2011 UR18)
Outlook: Microsoft Outlook 2013 (15.0.4997.1000) 32-Bit
Outlook Client: 5.0.9690.1992
If it is a bug we will most likely not be the only ones experiencing the problem and I am wondering if anybody else sees this issue.
We actually found the solution to our issue. It was fixed by applying KB3179593 to the client. It was released over a year ago but we weren't aware about this last patch to CRM 2011 UR18.
It is suggested to apply the patch to CRM 2011 server instance, too.
Business Applications communities