When users access SharePoint 2013 site using IE 11, they often are haunted by the following errors:
SharePoint 2013 calendar SCRIPT5009 and SEC7111 errors
- SCRIPT5009: ‘HighlightText’ is undefined
- SEC7111: HTTP security is compromised by (null)
In addition, you may also see that the “Edit Page” doesn’t render the page in Edit mode, etc.,
However if you try the same URL in chrome it works fine, which is an irony that the opposite would have been understandable!!!
The issue is due to SharePoint 2013’s incompatibility with IE 11, which can be fixed by performing the following:
GoTo IE 11->Tools->Compatibility View Settings -> “Add your site host name”
The above hack would ensure that the site when rendered uses the IE 10 mode (i.e., run in compatibility mode).
2,436 total views, 2 views today
The following is the Powershell command to help migrate a site from SharePoint 2010 Classic Authentication to SharePoint 2013 Claims mode along with Retaining the site Permissions defined for users.
Convert-SPWebApplication -Identity “Your Site URL” -To Claims -RetainPermissions
1,104 total views, no views today
Once a Sharepoint 2010 site is upgraded to 2013, the sites will still be rendered in the 2010 mode. We have two options to upgrade the sites:
Use the Visual Upgrade option in SharePoint 2013, which would in turn create an entry with the SharePoint timer job and will take a minimum of 10-15 minutes (or more depending on the site's size) to upgrade to the new 2013 look and feel.
Use the Powershell and perform the upgrade.
I always prefer the second option, as it allows you to script the Upgrade and perform the visual upgrade sequentially on many sites (especially if you have a parent site collection with 10 or more sub sites in it). The below is the powershell that needs to be executed to upgrade the site. (Open the SharePoint Management Shell in Administrator mode before executing the below powershell)
Upgrade-SPSite http://<Your_Web_Site_URL> -VersionUpgrade
How to verify if the sites are upgraded?
In order to verify if the sites are upgraded to 2013 look and feel, execute the below PowerShell which will display the site's compatibility level alongside (will either be 14 or 15) to indicate if the site's are upgraded or not: (Open the SharePoint Management Shell in Administrator mode before executing the below powershell)
get-spsite -Limit All
2,574 total views, no views today
During upgrade from SharePoint 2010 to 2013, when we execute the TEST-SPCONTENTDATABASE command, we run into the below exception that says :
"The <Web site> web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against a windows classic authentication mode. There is an inconsistency between the authentication mode of target web application and the source web application. Ensure that the authentication mode setting in upgraded web application is the same as what you had in previous SharePoint 2010 web application…."
4,141 total views, 5 views today
Too often when we want to try accessing a website hosted in IIS in Windows Server 2012 configured under Windows Authentication, from within the server, we are repeatedly presented with the "Windows Prompt" even after providing the correct credentials. Per Microsoft, this behavior is per design and to access the site we had to perform the below modification in the Registry:
Expand HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Control -> Lsa -> MSV1_0
Look for a key named "BackConnectionHostNames". If it doesnt exist then create a new one, by right-clicking onthe empty space and choose New -> Multi-String Value and provide the name as "BackConnectionHostNames"
Now add the name of the site (FQDN address), example http://test.contoso.com
Now if you try accessing the site, it will load without prompting for credentials. For more information on this topic visit, https://support.microsoft.com/en-us/kb/896861
2,532 total views, 1 views today
Too often Colloboration sites built on SharePoint, when accessed by users who try to open up documents from the document libraries would like to see the content on the native Microsoft Office than on Excel Services. Since on an OOB SharePoint 2013 installation where all services are enabled, when users click on an Excel document, it will try to open the document on the browser itself using Excel Services. The following configuratinos can be tried to change this behavior and force the documents to be opened in native Microsoft Office Clients:
1,704 total views, no views today
SharePoint 2013 has come out with the concept of “Device Channels” meant to allow designers/developers to define device specific master pages. For instance, the below is a pictorial layout that depicts a a typical 2 column layout in all websites:
2,999 total views, no views today
If for some reason you had to change the Service account password (in AD) used by SharePoint 2013 internally to execute the services, application pool etc., then you need to run the following to make sure that SharePoint is updated properly on the new password changes, otherwise you may get the below errors :
The password for the account domainName\AccountName, as currently stored in SharePoint, is not the same as the current password for the account within Active Directory
16,875 total views, 14 views today
This blog provides step-by-step instructions to develop a basic “hello world” SharePoint app. If you are new to the SharePoint app world, then please read my previous blog to get an intro to the “App Architecture” and its benefits before proceeding further. For those who has an understanding on the SharePoint App model, please read further :
24,309 total views, 49 views today
What is an App?
An app in SharePoint is a solution that connects to a SharePoint server/installation via client-side API’s (JSOM), CSOM or REST. It can either be embedded into a SharePoint page or can be deployed as a seperate application that leverages OAUTH 2.0 protocol to authenticate and access SharePoint functionality. They are managed through the “App Management Service” to manage, secure and license apps. Since the interaction between the App and SharePoint is controlled through OData-compliant REST interface, remote .Net client API’s and OAuth security protocols, an app can be developed in any language with any development tool. Apps can be developed either through Visual Studio 2012 or by using web-based development environment called Napa Office 365 Development Tools available free of charge. Apps can be purchased from SharePoint store (a public app marketplace) where users can find free and premium apps that can be installed onto individual sites (or managed through the App catalog).
6,570 total views, 5 views today