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

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

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

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

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

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

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

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.

My iphone won`t activate after updating to ios 5.1 plz help

my iphone 3gs won`t activate after updating to ios 5.1 plz help

I got mine sorted. Turns out because i got it unlocked the first time getting updates via itunes causes it to restart again. Had to get it unlocked at managed to get eveything back after restoring it from itunes. Very happy cause the guy in the apple shop told me i had to call apple and pay 35euro just to talk to them! I manged to get it unlocked for only 20 and its just like it was.
hope you're able to get yours sorted

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/

TS1717 my iphone 4s won't activate after updating to ios 7?

my iphone 4s won't activate after updating to ios 7?

Same here. I heard of some way to bypass the activation but it was patched .

Powerbuilder won't activate after upgrade

We currently have PowerBuilder 12.5 installed on a Windows XP machine. This was licensed and activated properly. So we tried to install 12.5.2 on a new Windows 7 machine. After upgrade, when I ran Powerbuilder, it came up as unlicensed (or as evaluation version). I went to the SAP site and regenerated a new license key for my machine and applied it, but it just won't activate. There are three options for us to choose:
New System
Display System
Edit System
We first tried the 'New System' option since it is an upgrade to 12.5.2 on a new machine (which we intend to move to). However, the option for us to choose from the 'Product version' or 'System Type' simply won't show any drop down option for us to choose, nor does it allow us to enter. Hence, we tried the 'Display System' and downloaded the license to update license. It just won't activate.
Has anybody ran into this issue and how was it solved?

Hi All,
I finally got a response from Nina who gave me the instruction on how to upgrade. I followed the instruction to 'Edit System' instead of 'New System', and not use IE. The reason I could not see drop down was due to IE 11 (have to use IE9 or before). Now my PowerBuilder 12.5.2 was upgraded successfully.
Thanks all, especially Nina.
Regards

IPhone won't activate after updating to iOS7... even after connecting to iTunes...

my iOS7 wouldn't budge after updating so I performed the silly mistake of doing a system restore. It updated but now my iPhone won't activate! Do you think it's the servers? I'm perfectly connected to my wifi and my phone is connected to iTunes!

Yeah... Thanks! It finally managed to pull through... ugh... was getting slightly worried because I needed it for something important at the moment... but thankfully it's okay now.

4S won't activate after iOS 5.1 update

Updated yesterday.
Update finished but my iphone 4s keeps asking me for configuration and won't activate.
I select the wireless network. Connection is fine. Even SIM unlock happens.
It says it is OK to use it now. I click on it and it returns back to configure screen again.
It is in a loop.
Configure-You can use it-Configure-You can use it-Configure and on and on.
I restored the iphone using iTunes but no lock. If I restore it from backup or icloud backup the situation is the same.
If I set it up as new iphone I can open it but this time I loose everything.
I have backups but I cannot use the phone if I install them.
This is really frustrating.
Can I get back to 5.01 somehow. I want to use my phone and I don't want to lose my data.
Any ideas?
Thank you.

The backup you have does matter (icloud or itunes. The moment you restore from it, you are in the loop. I don't know if Siri has anything to do with it or not but mine was off.
I talked to Apple for 50 minutes. We tried many things, no joy. The last words were that there were more people like us and if the number were enough Apple would develop and publish an update. What they suggested is to wait until the update is released, install the update and then make the restore from backup. It would work then.
Please call Apple and create a case. We need numbers.
I hope they take us seriously and correct this grave mistake as soon as possible.
For those who have iCloud backup, the following works:
Set the phone up as new device.
Go to Settings and iCloud.
Enter your iCloud account.
It will ask if you would like to merge.
If you say yes, you could at least get your contacts back.

Sharepoint Server Publishing Won't Activate After Deactivating

Similar Messages

Maybe you are looking for