It’s been a while, but I been busy 🙂
Ever come across an error that requires you to actually go to the second page results of a Google search? Well this one had me going.
SharePoint 2013 site with Publishing features, sub site all with publishing features switched on.
Cause – I needed to test whether publishing features was causing a problem on my site so
naturally I think of resetting it with a quick switch on switch off..
I navigate to manage site features and deactivate – SharePoint Server Publishing
Next step activate it.
This is where it goes haywire:
I immediately get –
Sorry, something went wrong
Content type ‘XXX-Guid-XXX’ not found in web ‘http://xxxxx-xxx.xx’.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 33d6049c-eba3-50b1-f7a6-c3acadd665ff
Date and Time: 3/5/2013 5:40:53 PM
Go back to site
After couple tries I start getting a 401 error. So I log in with an account that had site collection administrator permissions and still the 401 error.
Naturally I turn to the ULS logs and I find this :
Event log message was: ‘Failed to create the ‘Pages’ library.’. Exception was: ‘Microsoft.SharePoint.SPException: Content type ‘xxxx-guid’ not found in web ‘http://xxxxx-xxx.xx’.
at Microsoft.SharePoint.Publishing.CommonUtilities.GetContentType(SPWeb web, SPContentTypeId contentTypeId)
at Microsoft.SharePoint.Publishing.Internal.AreaProvisioner.CreatePagesDocumentLibrary(SPList approvalTaskList)’
I could just feel myself falling to my knees with my arms up shouting whyyyyyyyyyyyyyyyy!!!!! SP, whyyyyyyyyy!!!! ??? 🙂
Crawling the internet didn’t help and the UI was giving me the 401.
Only options I had was rebuild or command line force the Publishing feature to start up.
Found a couple scripts that I hoped would work but didn’t. Last option REBILD.
But wait there is one more command line tool I haven’t tried, our old and not forgotten friend STSADM.
A quick check in the 15hive folder and to my great JOY MS did take it out.
crawled the internet again and found a script on this site :
stsadm -o activatefeature -name PublishingSite -url http://xxxxx-xxx.xx -force
stsadm -o activatefeature -name PublishingResources -url http://xxxxx-xxx.xx –force
Opened STSADM in command prompt, ran those scripts and voila SharePoint Server Publishing is not active.
This process made me think of something I heard not too long ago:
“All great changes are preceded by chaos.” Deepak Chopra