SharePoint By Yagya Shree

Posts Tagged ‘feature

SharePoint 2013: Publishing Feature Activation Issue

leave a comment »


Symptom:
Unable to activate the Publishing feature on the site http://(SiteCollection Url)/ . While enabling the feature, it fails with “Access denied” error and then the users (including the site collection administrator) are unable to login to the site , fails with same error as access denied.

Environment:
SharePoint server 2013 with product version : 15.0.4649.1000

Error Messages Seen:
“Access denied”

Cause:
It looks like the Super user account and Super reader account was NOT set properly.

Currently the displayed strings are as like below:

DomainName\ superuser
DomainName\ superread

But the displayed strings should be as like below if you are using claims authentication for the web application
Claims format :
i:0#.w| DomainName\ superuser
i:0#.w| DomainName\ superread

Resolution:
The following command was executed and found that the web applications are configured with portal super user account and portal super reader account, however the format was domain\username instead of Claims format.

Get-SPWebApplication | %{Write-Host “Web Application: ” $_.url “`nSuper user: ” $_.properties[“portalsuperuseraccount”] “`nSuper reader: ” $_.properties[“portalsuperreaderaccount”] “`n”}

We nullified the property values of portalsuperuseraccount and portalsuperreaderaccount using the below command

$wa = Get-SPWebApplication “http://(SiteCollection Url)/”
$wa.Properties.Remove(“portalsuperuseraccount”)
$wa.Properties.Remove(“portalsuperreaderaccount”)
$wa.Update()

Followed the article https://technet.microsoft.com/en-us/library/ff758656.aspx and set the accounts using CA and PowerShell with right Claims format

$wa = Get-SPWebApplication -Identity “http://(SiteCollection Url)/”
$wa.Properties[“portalsuperuseraccount”] = “i:0#.w| DomainName\ superuser ”
$wa.Properties[“portalsuperreaderaccount”] = “i:0#.w| DomainName\ superread ”
$wa.Update()

More information:
https://technet.microsoft.com/en-us/library/cc261797.aspx
https://technet.microsoft.com/en-us/library/ff934623.aspx
http://blogs.msdn.com/b/andrasg/archive/2010/09/30/setting-the-super-user-account-on-sharepoint-2010-and-getting-access-denied-errors-afterwards.aspx
http://blogs.msdn.com/b/tehnoonr/archive/2013/05/03/10209570.aspx
http://blogs.msdn.com/b/kunal_mukherjee/archive/2011/01/10/caching-in-share-point-2010-best-practice.aspx

Written by bajiraoshinde

February 12, 2016 at 7:15 pm

How to delete SharePoint Orphane Features?

leave a comment »


Please run below commands in the farm using service account from one of the WFE servers:

 

Get-SPFeature | ? { $_.Scope -eq $null }

 

Get-SPFeature | ? { !$_.Scope } | % { $_.Delete() }

 

Note: Above command is to delete any feature which is not scoped to any site/sitecollection/webapplication/farm.

Written by Yagyashree

August 24, 2014 at 12:25 pm

Posted in sharepoint

Tagged with , , ,

“File Not Found” error message accessing main page after enabling custom feature on site collection

leave a comment »


ISSUE:

——–

àAfter enabling the feature customer was unable to access the main page of the site and got error message “File Not Found”

àYou are facing the same issue when he browse the site actions–site settings, “Master Pages” & “Web Parts”
àYou are able to browse the top level site collection http://sps03.shorturl.com/ main page without any error message

àYou are also able to browse “Sites & Workspaces” beneath the http://sps03.shorturl.com/sites/yagyashree
àYou are using OOB Master Page. A summary of the solution is detailed below.

 

 Cause

——–

à Users have tried to enable a custom feature on this site collection

 

Resolution

————-

à Open the SharePoint site http://sps03.shorturl.com/sites/yagyashree in SharePoint Designer 2007
à Opened the subsite under this site
à Copy the default.master from the subsite

à Renamed the original default.master to default.old

à Paste the copy from subsite

à Right Click on new default.master and choose “Make this as new default.master

à Save the changes

à Open the site and it should be working fine
àCheck the site actions–site settings and check the “master pages” & “web parts”, they should be coming up fine

Written by Yagyashree

April 8, 2009 at 12:09 am

Posted in sharepoint

Tagged with , , , , , , , , , , , ,

%d bloggers like this: