Daniel Reed
.NET, SharePoint and Graphic Design
Posted by mirata on Jul 19, 2011 in SharePoint | 7 Comments

I recently created a masterpage using advanced CSS features such as rounded borders and shadows. As many of you will know, the only Internet Explorer releases to navitely support these features without the use of tools like CSS3PIE are IE9 and the pre-release builds of IE10.

Now depending on how you are using your SharePoint environment, the site will be displayed in either IE8 Mode, or IE8 Compatibility Mode even if you have IE9. This is often due to a number of factors:

  • Compatibility View settings – by default, Intranet Sites are set to display in Compatibility Mode, so Intranet SharePoint sites will be affected
  • MasterPage settings – the default masterpage v4.master has a meta tag telliong thge browser to use IE8.

Essentially we can override these two settings by creating a custom master page using the following meta tag instead:

<meta http-equiv="X-UA-Compatible" content="IE=Edge" />

This forces IE to use the latest browser rendering engine it has. And this seems to be fine. Until you try to use a PeopleEditor field to select people or groups…

Namespace prefix 'xsd' is not defined.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: Namespace prefix 'xsd' is not defined.

Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[InvalidOperationException: Namespace prefix 'xsd' is not defined.]
System.Xml.Serialization.XmlSerializationReader.ToXmlQualifiedName(String value, Boolean decodeName) +1338197
Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderDictionaryEntryArray.Read1_Object(Boolean isNullable, Boolean checkType) +92
Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderDictionaryEntryArray.Read2_DictionaryEntry(Boolean checkType) +651
Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderDictionaryEntryArray.Read3_ArrayOfDictionaryEntry() +645
[InvalidOperationException: There is an error in XML document (1, 43).]
System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) +1479
System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader) +166
Microsoft.SharePoint.WebControls.EntityEditor.ParseSpanData(String spans) +810
Microsoft.SharePoint.WebControls.EntityEditor.LoadPostData(String postDataKey, NameValueCollection values) +85
System.Web.UI.Page.ProcessPostData(NameValueCollection postData, Boolean fBeforeLoad) +945
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2071

What the? This is actually a server-side error, so the browser is maybe not passing back some details when in IE9 mode. Not entirely sure.

Now after reading around, I noticed a forum comment that SP1 fixed this error. After installing SP1, I can say that it does not.

This is unfortunate news. I hope Microsoft resolves this issue soon. In the current state, one of Microsoft’s flagship products has issues with its latest software. I’m keen to hear if anyone has any resolutions or approaches to this problem.

  • Hey, Im having the same problem as well..
    God damn it.. SP is so weak =)

  • Same issue, any updates on the problem?

  • Same issue. Funny how SharePoint runs better on the latest version of Firefox these days.

  • Same issue. I totally agree that this is an embarrassing bug, and after reading the code of the Microsoft.SharePoint.WebControls.EntityEditor.ParseSpanData(String spans) method I’m not surprised. What a sad mess :-(

  • I am also experiancing this any fix

  • Sept 2012 here… Microsoft.. where are you on this fix? Get your heads out of your a$$es and start supporting your customers who actually have resources to afford front end developer talent and put a premium on the latest standards and technologies.

    This is very depressing that their own browser is not compatible with their own server product. It must be embarrassing for the SharePoint team as well to ship with such a critical bug (it would be embarrassing for me at least)


  • Try in the pickerdialog.master after the head tag.
    Worked for me to remove the error. still had toruble adding the person to the alert list though, but at least the picker worked

Leave a comment to James T

Spam Protection by WP-SpamFree