Unable to activate "SharePoint Server Publishing Infrastructure"

HI,I am unable to active publishing feature " SharePoint Server Publishing Infrastructure" in site collection features.while activating i am getting the below error.Please assist on this.

Hi Sekhar,
You posted on SharePoint 2010 forum, but seeing the screenshot I reckon you are having the issue in SharePoint 2013.
- Did you already activate this feature successfully on this particular Site Collection or never?
>> If never, try to delete this site collection (if this is an option for you like in a Dev environment for instance), and recreate it, then try reactivate the feature.
- Try to enable the feature by PowerShell
TechNet article to enable features by PowerShell
- Try enable the feature on another Site Collection
Cheers
FrenchSpeaker - MCTS

Similar Messages

Error when trying to activate SharePoint Server Publishing Infrastructure

I have recently inherited a SharePoint environment. On one site collection (which has 786 sites and subsites), I am trying to activate the
SharePoint Server Publishing Infrastructure feature and am getting the below error:-
The field with Id {51d39414-03dc-4bd0-b777-d3e20cb350f7} defined in feature {aebc918d-b20f-4a11-a1db-9ed84d79c87e} was found in the current site collection or in a subsite.
I believe there are two site templates which when they are deactivated, the publishing feature will activate but then the site templates will not activate.
I have seen from other posts etc. that this is related to
Feature with Id {aebc918d-b20f-4a11-a1db-9ed84d79c87e} is "PublishingResources", a hidden feature
Field with Id {51d39414-03dc-4bd0-b777-d3e20cb350f7} is "PublishingStartDate". It's the first field defined in the feature PublishingResources
I found this thread which suggests using the -force to activate the feature - https://social.msdn.microsoft.com/Forums/en-US/af5d0943-a568-4426-89f3-b0691f8d3f87/error-activating-publishing-feature?forum=sharepointgeneralprevious which
I havent tried as yet as I need to copy it to a test environment so I don't break it and the DB is edging toward 200GB (another seperate issue).
I guess my questions are:-
I am migrating all of this content to SP 2013 in the near future - I am assuming it is best to fix this beforehand?
Would it be easiest to edit the site templates somehow - what would to do to the template to fix it?
Some direction would be great.

Hi Kelsnz,
I recommend to use the command below to check which sites have this field:
$site = Get-SPSite http://yoursitecollectionURL
write-host $site
$webs = Get-SPWeb -Site $site -Limit All
foreach ($web in $webs)
foreach ($field in $web.availablefields)
if ($field.id -eq [GUID]"51d39414-03dc-4bd0-b777-d3e20cb350f7")
write-host $web " = " $field " " $field.id
If there are any sites listed, you may need to re-create the site before you migrate the environment to SharePoint 2013.
More references about this issue:
http://www.techques.com/question/19-27196/Activating-OOTB-Features-Fails
http://pedrosneglectedtechblog.blogspot.com/2010/03/adventures-in-sharepoint-2010-upgrades.html
Best regards.
Thanks
Victoria Xia
TechNet Community Support

SharePoint Server Publishing Infrastructure with drag-and-drop

Hello,
When I activated "SharePoint Server Publishing Infrastructure" future, I can no longer use drag-and-drop functionality between two libraries (eg. drag from Document Library to MyDoc library). When I disable it, drag and drop is possible.
But I need both of this functionalities, because i use Managed navigation. What should I do?
Thanks in advance,
Tomaz

Hi Tomaz,
According to your description, I could reproduce this issue as:
1. Create a web application with team site
2. Create a new library called docA, upload a new document
3. Then I could move the document to Document library with drag-and-drop feature
4. Activate SharePoint Server Publishing Infrastructure
5. I could not move the document from Document library to docA library with drag-and-drop feature
6. Upload a new document to docA, then also could not move it to Document library with drag-and-drop feature
Since you also want to use Managed Navigation, you can use Content and Structure feature to move a document from one library to another library. You can do as Site Settings->content and structure under Site Administration->clicking on the library,
then you can move or copy the document to the destination library.
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

SharePoint Server Publishing infrastructure - Sorry, you don't have access to this page

If I enable site feature on Any site in any site collection on Sharepoint farm,
every one get lock out (include Farm admin, ect) with error Sorry, you don't have access to this page.
I have to go to Web application -> User Policies Add: NT Authority\Authenticated Users, so that I can
log in to site, disable feature and everything start to work.
On : Site Collection Administration -> Site Collection Features
-> SharePoint Server Publishing Infrastructure : is activated
Infrastructure : I use Host name site collection, all effected sites are located in the same web application.
I think problem is with “SharePoint Server Publishing Infrastructure”. Because if I enable
that feature on site collection, then o have problem choosing together
SharePoint Server Standard Site Collection features and SharePoint Server Enterprise Site Collection features
If SharePoint Server Publishing Infrastructure is enabled, if a activate Standard Site Collection features , then choosing Server Enterprise Site Collection features, produce error : Sorry, something went wrong.
But I can enabled both features “Standard Site & Server Enterprise” before enabling SharePoint Server Publishing Infrastructure.
ULS logs, when I enable SharePoint Server Publishing Infrastructure :
From bottom up : Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|DOMAIN\user1, ClaimsCount=55
DelegateControl: Exception thrown while adding control 'Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource':
System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(Exception ex)
at Microsoft.SharePoint.Library.SPRequest.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid&
pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)
at Microsoft.SharePoint.SPWeb.GetList(String strUrl)
at Microsoft.SharePoint.Publishing.CacheManager..ctor(SPSite site)
at Microsoft.SharePoint.Publishing.CacheManager.GetManager(SPSite site, Boolean useContextSite, Boolean
allowContextSiteOptimization, Boolean refreshIfNoContext)
at Microsoft.SharePoint.Publishing.CachedAreaLookup.EnsureLookup(Boolean errorsAsExceptions)
at Microsoft.SharePoint.Publishing.CachedAreaLookup.GetCachedAreaOrException()
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigationCache.GetCachedWebInfo(CachedAreaLookup
cachedAreaLookup)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigationCache.GetWebNavigationSettings(CachedAreaLookup
cachedArea, CachedAreaLookup& parentCachedArea, Exception& loadError)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettingsList(CachedAreaLookup
cachedArea, Boolean includeInheritedSettings)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettings[T](CachedAreaLookup
cachedArea, String siteMapProviderName, Boolean includeInheritedSettings, CachedAreaLookup& cachedAreaWithSettings)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettings[T](SPWeb
web, String siteMapProviderName, Boolean includeInheritedSettings)
at Microsoft.SharePoint.Publishing.Navigation.SwitchableSiteMapProvider.GetCurrentWrappedProvider()
at Microsoft.SharePoint.Publishing.Navigation.SwitchableSiteMapProvider.get_RootNode()
at Microsoft.SharePoint.Publishing.Navigation.SwitchableDataSourceBehavior.AssignProperties(SiteMapProvider
targetProvider)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at Microsoft.SharePoint.WebControls.DelegateControl.AddControlResilient(Control ctl)
System.IO.FileNotFoundException: The system cannot find the file specified. (Exception from HRESULT: 0x80070002), StackTrace:
at Microsoft.SharePoint.SPWeb.GetObjectForUrl(String strUrl, Guid& listId)
at Microsoft.SharePoint.Utilities.SPUtility.<>c__DisplayClass9.<FindObjectAccessed>b__8()
at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3()
at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.SharePoint.Utilities.SPUtility.FindObjectAccessed(SPWeb web, SPSite site, SPObjectType&
objType, String& strObject, String& strListItemId)
at Microsoft.SharePoint.Utilities.SPUtility.RedirectToAccessDeniedPage(HttpContext context)
at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(HttpContext context)
at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(Exception ex)
at Microsoft.SharePoint.Library.SPRequest.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid&
pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)
at Microsoft.SharePoint.SPWeb.GetList(String strUrl)
at Microsoft.SharePoint.Publishing.CacheManager..ctor(SPSite site)
at Microsoft.SharePoint.Publishing.CacheManager.GetManager(SPSite site, Boolean useContextSite, Boolean
allowContextSiteOptimization, Boolean refreshIfNoContext)
at Microsoft.SharePoint.Publishing.CachedAreaLookup.EnsureLookup(Boolean errorsAsExceptions)
at Microsoft.SharePoint.Publishing.CachedAreaLookup.GetCachedAreaOrException()
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigationCache.GetCachedWebInfo(CachedAreaLookup
cachedAreaLookup)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigationCache.GetWebNavigationSettings(CachedAreaLookup
cachedArea, CachedAreaLookup& parentCachedArea, Exception& loadError)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettingsList(CachedAreaLookup
cachedArea, Boolean includeInheritedSettings)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettings[T](CachedAreaLookup
cachedArea, String siteMapProviderName, Boolean includeInheritedSettings, CachedAreaLookup& cachedAreaWithSettings)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettings[T](SPWeb
web, String siteMapProviderName, Boolean includeInheritedSettings)
at Microsoft.SharePoint.Publishing.Navigation.SwitchableSiteMapProvider.GetCurrentWrappedProvider()
at Microsoft.SharePoint.Publishing.Navigation.SwitchableSiteMapProvider.get_RootNode()
at Microsoft.SharePoint.Publishing.Navigation.SwitchableDataSourceBehavior.AssignProperties(SiteMapProvider
targetProvider)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at Microsoft.SharePoint.WebControls.DelegateControl.AddControlResilient(Control ctl)
at Microsoft.SharePoint.WebControls.DelegateControl.CreateChildControlsInternal()
at Microsoft.SharePoint.WebControls.DelegateControl.CreateChildControls()
at System.Web.UI.Control.EnsureChildControls()
at Microsoft.SharePoint.WebControls.DelegateControl.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer,
IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr
nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus&
notificationStatus)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus&
notificationStatus)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer,
IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr
nativeRequestContext, IntPtr moduleData, Int32 flags)
SPRequest.GetMetadataForUrl: UserPrincipalName=, AppPrincipalName= ,bstrUrl=/_layouts/15/ManageFeatures.aspx ,METADATAFLAGS=59
Unknown SPRequest error occurred. More information: 0x80070002
Access Denied. Exception: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)), StackTrace:
at Microsoft.SharePoint.Library.SPRequestInternalClass.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS,
Guid& pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)
at Microsoft.SharePoint.Library.SPRequest.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid& pgListId, Int32&
plItemId, Int32& plType, Object& pvarFileOrFolder).
System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)), StackTrace:
at Microsoft.SharePoint.SPWeb.GetList(String strUrl)
at Microsoft.SharePoint.Publishing.CacheManager..ctor(SPSite site)
at Microsoft.SharePoint.Publishing.CacheManager.GetManager(SPSite site, Boolean useContextSite, Boolean
allowContextSiteOptimization, Boolean refreshIfNoContext)
at Microsoft.SharePoint.Publishing.CachedAreaLookup.EnsureLookup(Boolean errorsAsExceptions)
at Microsoft.SharePoint.Publishing.CachedAreaLookup.GetCachedAreaOrException()
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigationCache.GetCachedWebInfo(CachedAreaLookup
cachedAreaLookup)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigationCache.GetWebNavigationSettings(CachedAreaLookup
cachedArea, CachedAreaLookup& parentCachedArea, Exception& loadError)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettingsList(CachedAreaLookup
cachedArea, Boolean includeInheritedSettings)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettings[T](CachedAreaLookup
cachedArea, String siteMapProviderName, Boolean includeInheritedSettings, CachedAreaLookup& cachedAreaWithSettings)
at Microsoft.SharePoint.Publishing.Navigation.TaxonomyNavigation.GetEffectiveProviderSettings[T](SPWeb
web, String siteMapProviderName, Boolean includeInheritedSettings)
at Microsoft.SharePoint.Publishing.Navigation.SwitchableSiteMapProvider.GetCurrentWrappedProvider()
at Microsoft.SharePoint.Publishing.Navigation.SwitchableSiteMapProvider.get_RootNode()
at Microsoft.SharePoint.Publishing.Navigation.SwitchableDataSourceBehavior.AssignProperties(SiteMapProvider
targetProvider)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapDataSource.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at Microsoft.SharePoint.WebControls.DelegateControl.AddControlResilient(Control ctl)
at Microsoft.SharePoint.WebControls.DelegateControl.CreateChildControlsInternal()
at Microsoft.SharePoint.WebControls.DelegateControl.CreateChildControls()
at System.Web.UI.Control.EnsureChildControls()
at Microsoft.SharePoint.WebControls.DelegateControl.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer,
IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr
nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus&
notificationStatus)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus&
notificationStatus)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer,
IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr
nativeRequestContext, IntPtr moduleData, Int32 flags)
SPRequest.GetMetadataForUrl: UserPrincipalName=i:0).w|s-1-5-21-1794000256-2036170096-312552118-17692, AppPrincipalName= ,bstrUrl=/Cache Profiles ,METADATAFLAGS=59
Feature Activation: Feature 'PublishingSite' (ID: 'f6924d36-2fa8-4f0b-b16d-06b7250180fa') was activated at URL
https://intranet.domain.com.
Calling 'FeatureActivated' method of SPFeatureReceiver for Feature 'PublishingSite' (ID: 'f6924d36-2fa8-4f0b-b16d-06b7250180fa').
Feature Activation: Activating Feature 'PublishingSite' (ID: 'f6924d36-2fa8-4f0b-b16d-06b7250180fa') at URL
https://intranet.domain.com.

Hi Mali,
According to your description, my understanding is that users cannot access the SharePoint site if SharePoint Server Publishing Infrastructure is enabled.
If I misunderstood please feel free to correct me.
I recommend use PowerShell to activate the feature in SharePoint 2013 to see if the issue still occurs.
http://technet.microsoft.com/en-us/library/ff607803(v=office.15).aspx
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Activate SharePoint Server Publishing

Hi guys,
This might be a simple question but I'd like to activate the SharePoint Server Publishing feature on my site collection where this site collection using a custom branding feature (i.e. using sandbox solution).
There is no documentation how this sandbox solution developed. But the branding solution is uploaded to solution gallery and the feature is activated at the site collection level.
I wonder if its safe for me to activate SharePoint Server Publishing feature and it will not overwrite current look and feel?
Any advise greatly appreciated.
Balai

As per below explination it shouldnt be a problem.
REad throught the below content and you will get a clear idea .
The SharePoint Server Publishing Infrastructure feature provides publishing functionality at the site collection level, and the SharePoint
Server Publishing feature provides publishing functionality at the site level. The subset of features contained in each of these primary features is collectively known as “publishing features.” Publishing features are all the features that are part of a preconfigured
publishing site or that are added when publishing is enabled at the site collection and site level. When publishing is enabled, all publishing features are automatically enabled. You cannot select individual publishing features, such as variations, to be enabled
separately without enabling other publishing features. All publishing features are either active or inactive. However, even though you can decide to enable the publishing features, you do not have to use them all.
When you enable the SharePoint Server Publishing Infrastructure feature, the Inherit
Theme and Apply
Theme sections are added to the Site Theme page. These options allow a site administrator to specify whether a site should
inherit the theme from the parent site or should use its own theme. These themes also allow the site administrator to specify whether to
apply the selected theme only to the current site or to the current site and all sites below it in the site hierarchy. For more information about themes, see Themes
overview (SharePoint Server 2010).
New master pages and page layouts, such as article pages and a Wiki page that is used by publishing sites, are added.
A new folder is created in the Master Page Gallery library, and is named based on the language that was used for the SharePoint Server 2010 installation. For example, if the English version
was installed, the folder name is en-us. This folder contains a folder named Preview Images, which contains the thumbnail preview images of the Publishing page layouts.
http://msdn.microsoft.com/en-us/library/office/gg430141(v=office.14).aspx

The SharePoint Server Publishing Infrastructure feature must be activated at the site collection level before the Publishing feature can be activated.

Hi All,
I am trying to activate the Publishing feature for a SharePoint website using a custom Site Definition File. The problem I am getting
is when I try to use the custom site template I get an error message:
New-SPSite : The SharePoint Server Publishing Infrastructure feature must be activated at the site collection level before the Publishing feature can be activated.
The custom
Site Definition File snippet is show below:
<?xml
version="1.0"
encoding="utf-8"?>
<Project
Title="SiteDefinition1"
Revision="2"
ListDir=""
xmlns:ows="Microsoft
SharePoint"
xmlns="http://schemas.microsoft.com/sharepoint/">
<NavBars>
</NavBars>
<Configurations>
    <Configuration
ID="0"
Name="SiteDefinitionDelegateControls2">
      <Lists/>
      <SiteFeatures>
        
        <Feature
ID="{3bae86a2-776d-499d-9db8-fa4cdc7884f8}"
Name="FeatureDefinition/15/3bae86a2-776d-499d-9db8-fa4cdc7884f8"
/>
        
        <Feature
ID="{a392da98-270b-4e85-9769-04c0fde267aa}"
Name="FeatureDefinition/15/a392da98-270b-4e85-9769-04c0fde267aa"
/>
      ...Other Site Features
      </SiteFeatures>
     <WebFeatures>
        
     <Feature
ID="{94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb}"
Name="FeatureDefinition/15/94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb"/>
     ... Other Web Features
      </WebFeatures>
      <Modules>
        <Module
Name="DefaultBlank"
/>
      </Modules>
    </Configuration>
</Configurations>
<Modules>
    <Module
Name="DefaultBlank"
Url=""
Path="">
      <File
Url="default.aspx">
      </File>
    </Module>
</Modules>
</Project>
I hope you can help
Colin

As the error says. The Publishing Infrastructure feature must be activated at the Site Collection level where you are creating a new site PRIOR to turning on the Publishing feature. So if you are trying to use this site definition to create a
new Site Collection then its not going to work. If you are trying to create a sub site then make sure that Publishing Infrastructure is enabled in the site collection before trying to create a sub site with this site definition.
Internally Microsoft does this for the Publishing Portals using custom code. Here's an article that discusses how to do it in SharePoint 2010.
http://msdn.microsoft.com/en-us/library/office/gg615465(v=office.14).aspx
Compare what's in the article to one of the Publishing templates available out of the box in 2013 and you should be able to find the assembly that is used to load the Publishing features.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Use Powershell to deactivate Feature SharePoint Server Publishing Infrastructure

Hi - we have activated Feature SharePoint Server Publishing Infrastructure on a site collection and now we have lost access that site - So is there a way I can use PowerShell to deactivate the feature?
Thanks
J

Hi J,
I'm not getting "we have lost access that site", Site administrator and System Account always have access to the site unless there is some error coming on the site which is not letting user to login in the browser.
If you are getting access denied error then powershell script also throw the same error. So, for running powershell script you must have access to site.
Best Regards,
Brij K
http://bloggerbrij.blogspot.co.uk/

Sharepoint Server Publishing Won't Activate After Deactivating

I am trying to reactive SharePoint Server Publish under Manage Site Features after deactivating. However I keep getting an error:
SharePoint Server Publishing Infrastructure is Activate in Site Collection Features. Any assistance you can provide would be helpful. THANKS!

check the ULS log for more detail about the error, you can get the trace for the correlation ID mentioned in the error.
Also try to enable it via command line. check this
http://www.blog4sharepoint.com/activate-publishing-feature-powershell
http://www.sharepointblog.in/2013/07/activate-sharepoint-server-publishing.html
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Which user data or customization is associated with Sharepoint Server Publishing feature

Hi
I want to deactivate/activate sharepoint server publishing feature but there's a warning message which says:
Any user data or customizations associated with this feature might be lost
How could I know specifically which user data will be lost after deactivating this feature?
Please note that this is "Sharepoint Server Publishing" and not "Sharepoint Server Publishing Infrastructure". The feature I want to deactivate is a site level feature and not a site collection level feature.
Any clues may be helpfull

If you deactivate the Publishing Infrastructure at the site collection then any items in your Pages lists may not survive.
http://sharepoint.stackexchange.com/questions/87031/what-user-data-or-customizations-will-i-lose-if-i-deactivate-and-reactivate-a-si
Generally speaking you need to check dependencies of other Features to this Feature, but also to ensure that existing functionality do not depend on any artifacts this feature could deploy (Web parts, physical files, controls, etc.).
To check if other features depend on this one you could do this by looking up the GUID of the feature in a physical folder and everywhere it appears check the FeatureDependencies element.
To identify what this feature does you would look into the Feature.xml and Elements.xml to see what artifacts it deploys, e.g. stuff deployed via Modules must be removed manually, any custom controls, web-parts, which might depend on the actual assembly
deployed by the feature will also crash.
Also, to my knowledge the SSRS site collection feature is part of the actual Enterprise features which are usually pushed-down from Central Admin when using the "Activate/Deactivate Enterprise Features on existing sites" - any farm admin would be able to
re-activate it again.
If this helped you resolve your issue, please mark it Answered

Ran into a problem by activating the SharePoint Server Publishing feature

By activating the "SharePoint Server Publishing feature" at site level the complete look and feel of the site has been changed to a default page layout , all the customization's were removed.
Changes were not rolled back even after deactivating the feature.
any help on how to get back my look and feel is appreciated.
Thanks in advance.
Regards
Bhaskar

Hi,
How did you customize the site initially? Was that in SharePoint designer? And if so what part of it did you exactly customize? The page itself or the masterpage?
Regards,
Casper

Unable to activate windows server 2012 (0x80072F8F)

I seem to be unable to activate my Windows Server 2012 Essentials. All I recieve is the following message:
Windows couldn´t be activated
Go to Control Panel to learn about other ways to activate
Error code: 0x80072F8F
Error description: A security error occurred
This is a presisting problem and I can´t find any other way to activate in the control panel, what to do?

I'd double check that the date / time are correct.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Unable to activate CS3

I am trying to move my copy of CS3 to a new PC, but got a message saying something like "unable to activate, the server is not available now". I had not yet de-activated the old licence and do not know whether that is the problem or whether it is another issue.
Can someone please help?
Thanks
Bob

CS3 works fine on my Windows 8 machine, and the Windows site says they're compatible. My problem activating was other software on my machine. Specifically for us, something called Net Nanny, an internet filter. Maybe McAfee or Norton would cause the same trouble? Temporarily disabling the software fixed my problem. Good luck!

Not able to see 'sharepoint publishing infrastructure' feature to activate

i m trying to activate publishing infrastrucure feature in my top site . but it is never present there. i m trying team site and i tried on one publishing site even then i can not find this feature . pls someone suggest me whats wrong

The Publishing Infrastructure feature is a site collection scoped feature. Go to the root level of your site. Click on Site settings -> Site Collection administration -> Site Collection feature. Here you should be able to find the feature. Please note
that Publishing feature is not available in SharePoint foundation. An alternative to it is available here:
https://spf2013publishing.codeplex.com/
Blog | SharePoint Learnings CodePlex Tools |
Export Version History To Excel |
Autocomplete Lookup Field

SharePoint Foundation Sandboxed Code Service - Unable to activate worker process proxy object within the worker process

Issue:
On a vanilla installation, the sandboxed code service (e.g. SPUCHostService.exe) is started; however, SPUCWorkerProcessProxy.exe and subsequently SPUCWorkerProcess.exe fails to start.
Resolution/Workarounds attempted:
Attempted 2 different Load balancing settings – local and remote (i.e. affinity)
Ensured local computer policy on server for ‘RPC Endpoint Mapper Client Authentication’ and ‘Restrictions for Unauthenticated RPC clients’ is disabled.
Ensured following key in registry is set properly - HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\RPC
Attempted to bypass SharePoint’s check for certificate revocations at crl.microsoft.com
Ensured the service account is added to the respective groups (e.g. Performance Log Users, Performance Monitor Users, IIS_IUSRS, WSS_ADMIN_WPG, WSS_WPG)
Increased limit of ‘AbnormalProcessTerminationCount’ of SPUserCodeService via Powershell
We have tried all possible workarounds from the following MSDN reference:
http://blogs.msdn.com/b/sharepointdev/archive/2011/02/08/error-the-sandboxed-code-execution-request-was-refused-because-the-sandboxed-code-host-service-was-too-busy-to-handle-the-request.aspx
ULS:
02/21/2014 05:24:50.64 SPUCHostService.exe (0x0230) 0x0F74 SharePoint Foundation Sandboxed Code Service              fe8a
Medium               - - Unable to activate worker process proxy object within the worker process: ipc://38432b45-2f32-4926-ade2-ef53ae1cd501:7000
02/21/2014 05:24:50.64 SPUCHostService.exe (0x0230) 0x0F74 SharePoint Foundation Sandboxed Code Service              fe8c
Medium               - - Error activating the worker process manager instance within the worker process. - Inner Exception: System.InvalidOperationException: Unable to activate worker
process proxy object within the worker process: ipc://38432b45-2f32-4926-ade2-ef53ae1cd501:7000     at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.CreateWorkerProcessProxies()
02/21/2014 05:24:50.64 SPUCHostService.exe (0x0230) 0x0F74 SharePoint Foundation Sandboxed Code Service              ei0t
Medium               - Process creation/initialization threw an exception. Stopping this process. "ipc://38432b45-2f32-4926-ade2-ef53ae1cd501:7000"
02/21/2014 05:24:50.65 SPUCHostService.exe (0x0230) 0x0F74 SharePoint Foundation Sandboxed Code Service
fe87                Medium               - - Error activating the worker process manager instance within
the worker process. - Starting worker process threw - Inner Exception: System.InvalidOperationException: Unable to activate worker process proxy object within the worker process: ipc://38432b45-2f32-4926-ade2-ef53ae1cd501:7000     at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.CreateWorkerProcessProxies()
Any other insights on how I can troubleshoot the issue described?
Thanks in advance!

Hi ,
For resolving your issue , you can do as the followings:
1. Logged into the Web Server with the Timer Service Account.
2. Ran the powershell command to check the SID of the account running the spucworkerprocessproxy.exe:
$(Get-SPManagedAccount -Identity "THE SERVICE ACCOUNT").Sid.Value
3. Checked the registry :
HKEY_USERS\[SID OF THE SERVICE ACCOUNT]\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing\State
4. Changed the value 0x00023c00 to 0x00023e00
In addition, here are some similar posts for you to take a look at:
http://social.technet.microsoft.com/Forums/en-US/aae497df-5f0d-4f86-a724-c7b805ccd07f/sharepoint-sandboxed-code-service-troubles?forum=sharepointgeneralprevious
http://blogs.technet.com/b/operationsguy/archive/2011/01/17/sharepoint-2010-sandboxed-code-solutions-and-web-proxy.aspx
http://social.msdn.microsoft.com/Forums/en-US/c21e2c3a-a259-4d5f-8071-eff52b7bddc3/issue-sandbox-solution-too-busy-to-handle-the-request?forum=sharepointgeneralprevious
I hope this helps.
Thanks,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Unable to install Sharepoint Foundation 2013 in Windows Server 2012 for FIM 2010 R2

HI,
I am Unable to install Sharepoint Foundation 2013 in Windows Server 2012 for FIM 2010 R2,
Before SharePoint Foundation 2013 installation I installed all prerequisite software that is required for SharePoint Foundation 2013 but when we run SharePoint Foundation 2013 setup that gives below error so I am requesting you please help on this.
Setup is unable to proceed due to the following error(s):
Windows Server Appfabric is not correctly configured.You should unistall Windows Server Appfabric and reinstall it using the SharePoint Products Preparation Tool.
Regards
Anil Kumar

You really need to do what error is suggesting.
Windows Server Appfabric is not correctly configured.You should unistall Windows Server Appfabric and reinstall it using the SharePoint Products Preparation Tool.
Nosh Mernacaj, Identity Management Specialist

Unable to activate "SharePoint Server Publishing Infrastructure"

Similar Messages

Maybe you are looking for