SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After the 2007 to 2010 SharePoint upgrade i have taken notice that when i try to activate a feature under the site collection admin for a root site page and also with manage site features i keep on getting an error page as mentioned below.

           <custom Errors mode="Off"/>

I am confused as to why this problem would is occurring.

share|improve this question
do you know what this custom feature contains? – Falak Mahmood Jun 9 '12 at 12:14
It happens for all the features even the ones that are activated, when i try to deactivate they throw a custom error also – wayne9999 Jun 9 '12 at 21:21
see my response. – Falak Mahmood Jun 10 '12 at 17:21

It appears that you don't have enough permissions to activate custom features. I would recommend you opening SharePoint Management Shell (run it as an administrator) and run the following powershell to activate features:

Get-SPWebApplication nameofwebapplication| Get-SPSite -Limit ALL | % {Enable-SPFeature "nameoffeature" -Url $_.Url}

One more thing you can enable the custom error messages for layouts pages by changing the web.config in the following folder.

C:\Program Files\Common files\Microsoft Shared\Web Server Extensions\14\template\layouts

web.config change:

<customErrors mode="Off" />

Follow this blog for more details:

share|improve this answer
Permission should not be a issue because i have the farm admin account and also the webapp admin account also. – wayne9999 Jun 10 '12 at 18:06
did you the try the powershell as mentioned above? – Falak Mahmood Jun 10 '12 at 18:08
I tried the powershell cmd and it still didnt activate it was complaining about a duplicate content type name "resource" was found – wayne9999 Jun 12 '12 at 0:42
could you paste the complete error message? – Falak Mahmood Jun 13 '12 at 22:14

What is that feature supposed to do? You can try activating the feature again and check the log files at (14\Logs) to get the actual error message. Or you could turn on custom errors in web.config to get the actual message (but if this is already in prod, I would not do it this way). Check this page on how to turn on errors in web.config.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.