none
Manage Farm Features Fails

    Pergunta

  • In CA when I click on Manage Farm Features I get the following error:

    Required attribute 'Scope' is missing from tag 'Feature' in feature definition for feature with ID '00000000-0000-0000-0000-000000000000'.

    When I try to access site features or site collection feature from any site settings page I also get the return to page standard error.

    Not sure how to start troubleshooting this one.


    davidh

    quinta-feira, 21 de junho de 2012 17:26

Respostas

  • Thanks to all you guys for helping with this issue. After doing some digging around I found that one of the other adminstrators had installed a third party feature and tried to modify it, but it took some investigation on the Sharepoint side before I finally got an idea of what was going on, I asked the other admins and then found out how this happened. Below is synopsis of what I did to find the problem and what I had to do to resolve it. I hope it helps someone else down the line.

    Issue:

    When accessing Farm Features from CA or site features from any site settings page the following error was displayed

    Required attribute 'Scope' is missing from tag 'Feature' in feature definition for feature with ID '00000000-0000-0000-0000-000000000000'

    Resolution:

    Knowing that features had worked recently I searched for recent feature.xml file modifications. I found two feature folders with recent dates on the server that I believed to be related to the problem, ‘emailfeature’ and ‘harmonemail’. Further, the instructions in the harmon.ie KB article (http://harmon.ie/KB/mapping-e-mail-headers-sharepoint-metadata) to install the harmon.ie email feature  refer to a folder with the name 'emailfeature':

    STSADM.EXE -o installfeature -name emailfeature

    I found that the information that was in this folder is somehow malformed and would not uninstall by using the stsadm commands specified in the KB article:

    cd C:\Program Files\Common Files\Microsoft Shared\web server extensions\14\BIN

    STSADM -o deactivatefeature -name emailfeature -url <SharePoint URL>

    STSADM -o uninstallfeature -name emailfeature

    IISRESET

    The deactivate command threw this error:

    Required attribute 'Scope' is missing from tag 'Feature' in feature definition for feature with ID 'BBDCB76D6-BB40-4608-9A91-3AFAC22A76F'

    Additionally the GUID listed in the feature.xml file in the 'emailfeature' folder, and as shown in the error above, is not what is specified as authentic by harmon.ie support. However, the information in the 'harmonemail' folder is correct,and appears to be what Harmon.ie supports. I also found some additional command parameters to force the uninstall. Using these commands and using the 'harmonemail' folder in the stsadm commands vs the 'emailfeature' folder I was able to uninstall the harmonemail feature without error.

    stsadm -o deactivatefeature -filename FeatureNameFolder\feature.xml -force -url http://site

    stsadm -o uninstallfeature -filename FeatureNameFolder\feature.xml -force

    Iisreset

    In order to uninstall the 'emailfeature' feature, I deleted the malformed .xml files found in the 'emailfeature' folder and then copied the .xml files from the 'harmonemail' folder. I ran the stsadm commands using the 'emailfeature' folder and the command returned 'Operation completed successfully'. After iisreset I was once again able to access the features pages.


    davidh



    • Marcado como Resposta DAH69 quinta-feira, 12 de julho de 2012 17:53
    • Editado DAH69 quinta-feira, 12 de julho de 2012 17:55
    quinta-feira, 12 de julho de 2012 17:53

Todas as Respostas

  • Hi,

    DId you install any feature recently, if yes what command you used? or did you try to change feature.xml file. For me its look, some feature not installed properly. Did you check the ULS logs?

    thanks

    -ws


    Thanks -WS SharePoint administrator, MCITP(SharePoint 2010)

    quinta-feira, 21 de junho de 2012 21:20
  • please check

    http://social.msdn.microsoft.com/Forums/eu/sharepointdevelopment/thread/8e6c5a56-15e7-49e1-bd02-2e816a0f9d4e

    Pious | Enthusiastic about SharePoint | Posting is provided "AS IS" with no warranties, and confers no rights

    sexta-feira, 22 de junho de 2012 07:49
  • Nope, I have not recently added any features. But unfortunately I have a couple of other folks who also modfy things from time to time. Where can I find the feature.xml file? A search of the server finds a lot of feature.xml files. I did find one that has a modified date of just a couple of days ago. This is the contnet of that file. I am not well versed in xml coding. Do any of you guys see something wrong with this:

    <?xml version="1.0" encoding="utf-8" ?>
    <Feature Id="BDCB76D6-BB40-4608-9A91-3A4FAC22A76F">
    AlwaysForceInstall="True"
    Title="E-mail Content Type"
    Description="E-mail Content Type and Columns"
    Version="12.0.0.0"
    Scope="Site"
    xmlns="http://schemas.microsoft.com/sharepoint/">
    <ElementManifests>
    <ElementManifest Location="emailcolumns.xml"/>
    <ElementManifest Location="emailcontenttype.xml"/>
    </ElementManifests>
    </Feature>


    davidh


    • Editado DAH69 sexta-feira, 22 de junho de 2012 14:55
    sexta-feira, 22 de junho de 2012 09:42
  • The Scope=Site line stands out.  And what version of SharPoint are you using, the XML above indicates 2007?

    Steven Andrews | SharePoint Professional | http://www.twitter.com/backpackerd00d | https://baron72.wordpress.com/

    sexta-feira, 22 de junho de 2012 10:38
    Usuário que responde
  • We are on Sharepoint 2010.

    So what should it be if Scope="Site" is incorrect?

    Since I can't get into any of the site features or farm features pages is there a way to simply remove this entirely?

    Thanks for the help Steven.


    davidh


    • Editado DAH69 sexta-feira, 22 de junho de 2012 14:54
    sexta-feira, 22 de junho de 2012 10:44
  • One of the feature.xml is corrupted and it could be on any of the servers (WFEs or APP) of the farm. You can run powershell on all servers to find a feature.xml where ID attribute is missing.

    Get-ChildItem ".......\14\TEMPLATE\FEATURE" -filter "feature*.xml" -recurse|%{

    $featureFile = $_.FullName;

    $contents = Get-Content $featureFile

    if( $contents -match "Scope" -and $contents -match "ID"){

    Write-Host "Feature Schema valid"

    }

    else{

    Write-Host "Feature Schema Corrupted: " $featureFile

    }

    }

    sábado, 23 de junho de 2012 18:11
  • Many thanks!

    Wow, that returned a lot of information. Is there anyway to have that piped to a .txt file?


    davidh

    segunda-feira, 25 de junho de 2012 10:09
  • This script is a good starting point but it returns so many lines that exceeds the buffer and I can't see everything that has scrolled past. Is there a way to capture this to a .txt file or something. All help appreciated.


    davidh

    terça-feira, 26 de junho de 2012 17:40
  • Try capturing the corrupt feature files and pipe it out to a file.

    $CorruptFeatures=@();
    Get-ChildItem ".......\14\TEMPLATE\FEATURE" -filter "feature*.xml" -recurse|%{
    $featureFile = $_.FullName;

    $contents = Get-Content $featureFile

    if( $contents -match "Scope" -and $contents -match "ID"){

    Write-Host "Feature Schema valid"

    }

    else{

    Write-Host "Feature Schema Corrupted: " $featureFile
    $CorruptFeatures += $featureFile;

    }

    }
    $CorruptFeatures > "C:\CorruptFeatureSchema.csv";

    terça-feira, 26 de junho de 2012 19:03
  • Thanks, that let me grab the ones that this script identifies as corrupted. However none of them contain a call for "Scope", maybe they aren't really corrupted and just simply don't contain that element? The code for one of them is below, they are all very similar to this. Interestingly the dates on each of these dates back over 2 years to shortly after we created the farm. Not sure where to go frome here?

    <?xml version="1.0" encoding="utf-8" ?>
    - <!--
     Copyright (c) Microsoft Corporation. All rights reserved. 
      -->
    - <Elements xmlns="http://schemas.microsoft.com/sharepoint/">
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="STS#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="STS#2" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="MPS#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="MPS#1" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="MPS#2" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="MPS#3" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="MPS#4" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="WIKI#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="BLOG#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SGS#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="BDR#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="OFFILE#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="OFFILE#1" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="PWA#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="PWS#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SPS#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SPSPERS#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SPSMSITE#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SPSTOC#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SPSTOPIC#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SPSNEWS#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SPSNHOME#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SPSSITES#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SPSBWEB#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SPSCOMMU#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SPSREPORTCENTER#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SPSPORTAL#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="SRCHCEN#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="PROFILES#0" />
      <FeatureSiteTemplateAssociation Id="3CB475E7-4E87-45Eb-A1F3-DB96AD7CF313" TemplateName="CMSPUBLISHING#0" />
      </Elements>

    davidh

    quarta-feira, 27 de junho de 2012 14:02
  • These are valid Feature Staplers for all the site definitions. Let me check the script again since I didn't test it. Even I had experienced a similar issue where in Scope and ID attributes went missing from one of the feature.xml files and I had to use Powershell script to quickly identify the corrupted file.
    • Marcado como Resposta Rock Wang– MSFT sexta-feira, 29 de junho de 2012 07:16
    • Não Marcado como Resposta DAH69 sexta-feira, 29 de junho de 2012 09:37
    quarta-feira, 27 de junho de 2012 14:08
  • Thank you!

    davidh

    quarta-feira, 27 de junho de 2012 14:10
  • Hi Guru, did you get a chance to test the script again? Thanks again for the help.

    davidh

    sexta-feira, 29 de junho de 2012 09:44
  • Thanks to all you guys for helping with this issue. After doing some digging around I found that one of the other adminstrators had installed a third party feature and tried to modify it, but it took some investigation on the Sharepoint side before I finally got an idea of what was going on, I asked the other admins and then found out how this happened. Below is synopsis of what I did to find the problem and what I had to do to resolve it. I hope it helps someone else down the line.

    Issue:

    When accessing Farm Features from CA or site features from any site settings page the following error was displayed

    Required attribute 'Scope' is missing from tag 'Feature' in feature definition for feature with ID '00000000-0000-0000-0000-000000000000'

    Resolution:

    Knowing that features had worked recently I searched for recent feature.xml file modifications. I found two feature folders with recent dates on the server that I believed to be related to the problem, ‘emailfeature’ and ‘harmonemail’. Further, the instructions in the harmon.ie KB article (http://harmon.ie/KB/mapping-e-mail-headers-sharepoint-metadata) to install the harmon.ie email feature  refer to a folder with the name 'emailfeature':

    STSADM.EXE -o installfeature -name emailfeature

    I found that the information that was in this folder is somehow malformed and would not uninstall by using the stsadm commands specified in the KB article:

    cd C:\Program Files\Common Files\Microsoft Shared\web server extensions\14\BIN

    STSADM -o deactivatefeature -name emailfeature -url <SharePoint URL>

    STSADM -o uninstallfeature -name emailfeature

    IISRESET

    The deactivate command threw this error:

    Required attribute 'Scope' is missing from tag 'Feature' in feature definition for feature with ID 'BBDCB76D6-BB40-4608-9A91-3AFAC22A76F'

    Additionally the GUID listed in the feature.xml file in the 'emailfeature' folder, and as shown in the error above, is not what is specified as authentic by harmon.ie support. However, the information in the 'harmonemail' folder is correct,and appears to be what Harmon.ie supports. I also found some additional command parameters to force the uninstall. Using these commands and using the 'harmonemail' folder in the stsadm commands vs the 'emailfeature' folder I was able to uninstall the harmonemail feature without error.

    stsadm -o deactivatefeature -filename FeatureNameFolder\feature.xml -force -url http://site

    stsadm -o uninstallfeature -filename FeatureNameFolder\feature.xml -force

    Iisreset

    In order to uninstall the 'emailfeature' feature, I deleted the malformed .xml files found in the 'emailfeature' folder and then copied the .xml files from the 'harmonemail' folder. I ran the stsadm commands using the 'emailfeature' folder and the command returned 'Operation completed successfully'. After iisreset I was once again able to access the features pages.


    davidh



    • Marcado como Resposta DAH69 quinta-feira, 12 de julho de 2012 17:53
    • Editado DAH69 quinta-feira, 12 de julho de 2012 17:55
    quinta-feira, 12 de julho de 2012 17:53