Share via

Problem Applying a web Template

Anonymous
2018-12-24T20:49:18+00:00

I got a copy of SharePoint online to give me access to meta data for storing documents.  I then saw a site where I could implement Getting Things Done(GTD) using SharePoint.  I am using it with outlook.  I have no knowledge from a development side other than watching some videos on Lynda to start my learning, but I hope I can find a solution.  This solution involves using a template.  When the template is applied I get the error listed in the subject.  The author of the template posted a solution.  In the solution is references a PowerShell script.  However the website no longer exists to get the script and the site appears to be no longer updated by the author.  The author says the problem is from the a site that was a 2010 instance that was upgraded to 2013 where the template was created.  Any ideas would be helpful.  Here is the link that has the information related to the issue.  

http://wendy-neal.com/2015/07/this-web-template-requires-that-certain-features-be-installed-activated-and-licensed-error-when-creating-office-365-site-from-custom-template/

Thanks for any help

Microsoft 365 and Office | SharePoint | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

10 answers

Sort by: Most helpful
  1. Anonymous
    2018-12-28T15:27:22+00:00

    According to many threads posted here, this is a common problem which Msft has been unable to explain. I also posted about several "phantom" features that wouldn't activate on the assumption that Msft would identify them and resolve the issue, but they never did. Based on the poor development practices applied to sharepoint and its many unresolved bugs, the only conclusion we can reach is that site templates don't work properly so I wouldn't invest too much time in them.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-12-28T12:52:51+00:00

    It Activated a few more.  

    and only left  3.

    I will run the scripts again on those 3 and report back my results.

    Thanks for the help.

    SearchDrivenContent Feature

    Site collection

    592ccb4a-9304-49ab-aab1-66638198bb58

    Not activated

    SearchTaxonomyRefinementWebPartsHtml Feature

    Site collection

    8c34f59f-8dfb-4a39-9a08-7497237e3dc4

    Not activated

    SearchTaxonomyRefinementWebParts Feature

    Site collection

    67ae7d04-6731-42dd-abe1-ba2a5eaa3b48

    Not activated

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-12-27T06:35:28+00:00

    Hi Randy,

    You may try enabling SharePoint Server Publishing Infrastructure in site collection features to see the result. Please check the steps below:

    1. Click the Gear icon on the upper right corner of the site page, then click Site information > View all site settings.
    2. Click Site collection features under Site Collection Administration.
    3. Click the Activate button beside SharePoint Server Publishing Infrastructure.

    Regards,

    Tisky

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-12-26T15:08:48+00:00

    I was able to apply the solution.  I had to modify the command slightly.  I used the online version of the commands and it worked.  However it did not work for them all.  

    Did Work For

         Share With Everyone Feature

         Project Based Policy Feature

         Translation Feature

    Did not Work For

         SearchDrivenContent Feature

         SearchTaxonomyRefinementWebPartsHtml Feature

         ViewFormPagesLockDown Feature

         EnterpriseWikiSecondPhase Feature

         SearchTaxonomyRefinementWebParts Feature

    I figured what it did work for and did not might be helpful.  

    Thanks for the help.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-12-25T00:10:07+00:00

    Hi Randy,

    As the article provided by you in your post said, the problem is related to some features that are not enabled in SharePoint 2013, I found this post in our TechNet forum: Problem creating a SharePoint 2013 test site from a solution, you can active the feature using the following script: 

    $siteUrl = "http://Your site URL" #URL of site collection

    $site = Get-SPSite $siteUrl

    $site.Features.Add([System.Guid]"10F73B29-5779-46b3-85A8-4817A6E9A6C2")

    And run the same script again by putting the other feature ID and activate them as well using the script and create the site again.

    Regards,

    Tisky

    Was this answer helpful?

    0 comments No comments