Archive

Archive for the ‘Internet Explorer’ Category

Microsoft Dynamics CRM–Support with Windows 10, Edge and Office 2016

August 15, 2015 Leave a comment

A lot of us now have moved onto Windows 10 and enjoying the new operating system, well personally I can say I am. This blog post will reference another blog post on the Microsoft Dynamics CRM Support Blog regarding CRM support with Windows 10, the new Edge Browser and Office 2016.

In summary:

All Dynamics CRM releases including CRM 2011, CRM 2013, and CRM 2015 currently support Windows 10 for use with the web client. The supported browser is Internet Explorer 11.

Support of Microsoft Dynamics CRM 2015 on Edge browser will be available for CRM 2015 with Update 0.2 (7.0.2) and Update 1.1 (7.1.1) in September.

Support with Microsoft Dynamics CRM 2013 will be introduced in Update Rollup 4 for Service Pack 1 (6.1.4)

For more information, head along to the URL below:

https://community.dynamics.com/crm/b/dynamicscrmsupportblog/archive/2015/07/10/dynamics-crm-support-with-windows-10-edge-browser-and-office-2016

Greg Olsen
YellowDuckGuy

Microsoft Dynamics CRM – FIX: ‘CRM makes extensive use of your Web browser’s client-side abilities’ IE notification

This blog post quickly shows you how to fix the notification below when browsing Dynamics CRM via the web client of Internet Explorer.

Issue

You receive the following notification within Internet Explorer when browsing to Microsoft Dynamics CRM:

Microsoft Dynamics CRM makes extensive use of your Web browser’s client-side abilities. You either have one of these features turned off or your security settings are set so high that they prevent these features from being used. To enable these features, change your browser settings to allow the Microsoft Dynamics CRM site to run JavaScript. Learn more.

IE will show the message similar to below (screenshot taken from IE11)

CRM IE Browser Issue

Fix

Are you browsing to CRM from the server? if so, then the main fix for this issue is to turn off the IE Enhanced Security Configuration (ESC) within Server Manager tool. If not, then this fix may not work for your scenario. But keep reading!  Note: it is recommended to leave IE ESC on to protect IE from website vulnerabilities.  Locate the option of Configure IE ESC. Location of IE ESC is shown below.

IE Security Enhancement

Next is to turn off the IE ESC setting. You will notice in the screenshot above it is set to On for Users.

Set Users to Off

IE Security Enhancement2

Now when you browse to CRM the notification message should disappear and you are shown Microsoft Dynamics CRM within the [IE] browser.

If you have any related info on this topic, feel free to add a comment. I have only documented one FIX option, I’m sure there are other scenarios where you will get this notification issue.

Greg Olsen
YellowDuckGuy

Microsoft Dynamics CRM 2011 – Include HTC Support in CRM forms

February 2, 2013 Leave a comment

So the first thing you are probably asking is what is HTC support mean? HTML Components, known as HTCs, are a nonstandard mechanism to implement components in script as Dynamic HTML (DHTML) "behaviours" in the Microsoft Internet Explorer (IE) web browser. These files typically use an .htc extension. You may have seen a few of these files on the CRM web server? An HTC is typically an HTML file (with JavaScript / VBScript) and a set of elements that define the component.

Next question you may be asking yourself is, do I enable this or not? Well this is where it all begins. Update Rollup 12 and the December 2012 Service Update support additional browsers by generating HTML that supports W3C standards. This requires removing dependencies on HTML components (HTCs that we mentioned earlier) that are specific to IE. Makes sense right? This needed to be done to allow for the new and cool cross-browser support.

In Microsoft Dynamics CRM 4.0, or during an upgrade from CRM 4.0 to CRM 2011, the ‘crmForm’ JavaScript API that was used to access form elements will continue to provide backward compatibility only for IE. If you have code that uses the crmForm API, or any unsupported internal methods that interact with form objects that used HTC components, you must select to Include HTC support in CRM Forms on the Customization tab of System Settings

To enable ‘HTC support in CRM Forms’ follow the steps below:

  1. Navigate to Settings > Administration > System Settings
  2. After opening System Settings, click the Customization tab
  3. Find the section called HTML component support
  4. Select the option Include HTC support in Microsoft Dynamics CRM forms
  5. Click OK

System Settings

Enable Selection

Using this setting will not allow newer versions of IE to provide the best performance possible. IE 10 does not support HTC components. Microsoft has indicated that the option to continue support for HTC will be removed in the next major release of Microsoft Dynamics CRM. At that time the ‘crmForm‘ JavaScript API will no longer be supported. Therefore, you should seriously be planning to upgrade your form scripts to use Xrm.Page API. See my previous blog post where I discuss the CRM 2011 Custom Code Validation Tool. https://yellowduckguy.wordpress.com/2012/11/26/microsoft-dynamics-crm-2011-custom-code-validation-tool/

You maybe also asking the question, what is the default setting for my CRM installation? Here are the default settings:

  • CRM Online: Off
  • If you have an existing code script that requires HTC support, you have a CRM 2011 solution which is an upgrade from CRM 4.0 (without using Xrm.Page) or if you install a new solution that depends on HTC support you must change this to be enabled (On).

  • CRM On Premise: On
  • You will get better performance if you have this setting disabled (Off). But this would only happen if you have no code scripts that depend on HTC support.

So in summary, make sure you select the best option that suits your CRM solution. If you haven’t upgraded your ‘crmForm’ scripts, then now is probably the best time to start doing that.

Hope that helps?

Greg Olsen
YellowDuckGuy

Nokia Lumia 800 – Configuring the Vodafone NZ APN

If you are having issues accessing the Marketplace or browsing sites with Internet Explorer on your Nokia Lumia 800 within NZ then you may have an issue with the settings on your handset and require an update to the APN settings or have an APN setting added. Note: This blog applies to New Zealand only.

VodafoneNZ settings

Some error codes you may receive:

  • C00cee3b
  • C101a006

To setup the APN settings for your Nokia Lumia 800, then download the document from the link below and follow the instructions.

Configuring the NZ Vodafone APN on the Lumia.pdf (151.6KB)

Greg Olsen
Yellow Duck Guy

Microsoft Dynamics CRM 2011 – Unable to set value of property ‘innerHTML’

When attempting to Save and Close a form you might be presented with the error message shown below.

Microsoft Encountered an Error

To view the error details, the user can click View the data that will be sent to Microsoft link. The error information relating to this post will look similar to the following screenshot.

InnerHTML error

The error message is:

<Message>Unable to set value of the property ‘innerHTML’: object is null or undefined</Message>

Also notice that is commonly appears on line 6.

Issue

When you enter data in a CRM 2011 lookup field that has the field formatting option of most recently used items functionality enabled, you receive a script error when clicking Save and Close on the CRM form.

Note: This is also related (with the same resolution steps) to an original posting on this blog here.

Resolution

1. Go to Settings > Customization, and then click Customize the System.
2. Open your CRM 2011 entity in question, and then click Forms.
3. Double-click the form so the form customization window opens.

What you will need to do now for each custom lookup fields is the following:
4. Double-click to open.
5. Under Field Behaviour section in the Display tab, deselect or un tick the option Disable most recently used items for this field.

DisableOption

Now save and publish your customisation. You should now notice the issue disappear.

Greg Olsen
Yellow Duck Guy

Microsoft Dynamics CRM 2011–”Microsoft Dynamics CRM has encountered an error” – Lookup Error

May 28, 2012 1 comment

Posting the resolution to an issue found during UAT of a CRM 2011 system. The issue arose when the tester clicked save and close on a CRM 2011 record. The error message presented to the tester is shown below.

Microsoft Encountered an Error

To view the error details, the user can click View the data that will be sent to Microsoft link. The error information relating to this post will look similar to the following screenshot.

CRM Script Error

The error message is:

<Message>‘this.$E_2.contentWindow.document.body’ is null or not an object</Message>

Also notice that is commonly appears on line 6.

Issue

When you enter data in a CRM 2011 lookup field that has the field formatting option of most recently used items functionality enabled, you receive a script error when clicking Save and Close on the CRM form.

Resolution

1. Go to Settings > Customization, and then click Customize the System.
2. Open your CRM 2011 entity in question, and then click Forms.
3. Double-click the form so the form customization window opens.

What you will need to do now for each custom lookup fields is the following:
4. Double-click to open.
5. Under Field Behaviour section in the Display tab, deselect or un tick the option Disable most recently used items for this field.

DisableOption

 

Now save and publish your customisation. You should now notice the issue disappear.

Greg Olsen
Yellow Duck Guy

Internet Explorer – IE7 Compatibility Tag

IE 8 has been released for awhile now. If you create web pages, then you probably should be aware of the IE 7 compatibility meta data tag which can force your pages you have working in IE 7, to be compatible with IE 8.  IE 8 attempts to adhere to the CSS web standards and your old (yeah they are old now) IE 7 pages may not render correctly in IE 8.
 
Below is the meta data tag which you can use to force IE 8 to render the page in IE 7 format.
<meta http-equiv=”X-UA-Compatible” content=”IE=EmulateIE7″ />
 
Microsoft have more info here: http://go.microsoft.com/fwlink/?LinkId=120024
 
Greg Olsen
Yellow Duck Guy
Categories: Internet Explorer