Watch out for the new “Minimal Download Strategy” feature that is default on Team Sites in SharePoint 2013 as it’s full of nasty little bugs. Microsoft is pushing it pretty hard as improving load times and better for performance due to the AJAX and partial load functionality but I think it wasn’t fully tested. My recommendation for now is to disable this feature until we get a CU or SP that addresses it. Read on for some of the common errors you’ll see. Continue reading →
All posts tagged Errors
I’ve been working with Managed Metadata Navigation and the Content Search Web Part a lot lately in SharePoint 2013. I just recently ran into a nasty little bug with a site that had been upgraded from SharePoint 2010.
The Content Search Web Part just wouldn’t work. Preview worked great but as soon as I published the page the web part was blank. So I opened the page up in Chrome from some better debugging tools and found the following:
I recently came across an issue with Internet Explorer 10 that causes problems with a number of web sites. It took a little over a week back and forth with Microsoft support before we were able to finally target it to the browser. I thought it was an issue with a particular clients Office 365 tenant so that left us chasing our tails for a bit.
The problem stems from the way that Internet Explorer 10 handles websites in compatibility mode. Internet Explorer 8 and 9 respected a meta property embedded in the head of the website. Microsoft products like CRM and SharePoint utilized this property to automatically force the page into compatibility mode without any involvement from the user.
<meta http-equiv="X-UA-Compatible" content="IE=8" />
Internet Explorer 10, however, seems to disable compatibility mode by default… a big step forward in terms of Microsoft’s commitment to web standards but a a step backwards when it comes to… well… compatibility. Continue reading →
Had an issue this week that was resulting in blank pages being rendered for users of our SharePoint Extranet. The issue surfaced itself in two different ways. Users were able to access the sign in page but once they completed the sign in using Live Authentication (we’re using LiveAuth via Claims FBA for our extranet) they immediately received the error.
Using Internet Explorer
Users received a generic “Page could not be displayed error message.”
Using Google Chrome
Users received the following error message.
Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error
Here’s a common issue: You export a site as a template, save down your WSP file, browse out to your client environment and prepare to upload your WSP but you receive an error that looks something like this:
After some hunting you come to find out that your source environment had Project Server installed and your destination environment does not. This same scenario can happen all over the place. Consider going from an Enterprise environment to a Standard environment or from on premise to Office 365.
So how do you fix this? Continue reading →