Most of the
sharepoint problems revolves around features, activations, publishing,
enterprise, solutions and so on…Today I was working
with one user and he was facing some error message while activating publishing
feature at the site level.
What exactly those error
messages: (3 different error messages)
Specified
argument was out of the range of valid values.
Parameter
name: ContentTypeId at
Microsoft.SharePoint.SPContentTypeBindingElement.EnsureContentTypeExists(SPWeb
web)
at Microsoft.SharePoint.SPContentTypeBindingElement.ElementActivated(SPFeaturePropertyCollection
props, SPSqlCommand sqlcmdAppendOnly, SPWebApplication webApp, SPSite site,
SPWeb web, Boolean fForce)
at
Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionContentTypeAndEventReceiverBindings(SPFeaturePropertyCollection
props, SPSite site, SPWeb web, Boolean fForce)
at
Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionElements(SPFeaturePropertyCollection
props, SPWebApplication webapp, SPSite site, SPWeb web, Boolean fForce)
at
Microsoft.SharePoint.SPFeature.ProvisionElements(SPFeaturePropertyCollection
props, SPWebApplication webapp, SPSite site, SPWeb web, Boolean fForce)
at
Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent,
SPFeaturePropertyCollection props, Boolean fForce)
at
Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId,
SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
at Microsoft.SharePoint.SPFeatureCollection.Add(Guid
featureId, Boolean force)
at
Microsoft.SharePoint.SPFeatureCollection.CheckSameScopeDependency(SPFeatureDefinition
featdefDependant, SPFeatureDefinition featdefDependency, Boolean
fActivateHidden, Boolean fForce)
at Microsoft.SharePoint.SPFeatureCollection.CheckFeatureDependency(SPFeatureDefinition
featdefDependant, SPFeatureDependency featdep, Boolean fActivateHidden, Boolean
fForce)
at
Microsoft.SharePoint.SPFeatureCollection.CheckFeatureDependencies(Guid featidDependee,
Boolean fActivateHidden, Boolean fForce)
at
Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId,
SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
at
Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId)
at
Microsoft.SharePoint.WebControls.FeatureActivator.BtnActivateFeature_Click(Object
objSender, EventArgs evtargs)
at
System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at
System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
at
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl,
String eventArgument)
at
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint)
Provisioning
did not succeed. Details: Failed to create the 'Pages' library. Ori
ginalException:
Content type '0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130E
C3DB064584E219954237AF39'
not found in web 'https://sharepointknowledgemanagement.net/sites/DemoSite'.
The
feature failed to activate because a list at 'Documents' already exists in this
site. Delete or rename the list and try
activating the feature again. at
Microsoft.SharePoint.Publishing.Internal.ProvisioningHelper.AddList(SPListCollection
lists, String urlName, String title, String description, Guid featureId, Int32
templateType, Boolean& newListCreated)
at
Microsoft.SharePoint.Publishing.Internal.ProvisioningHelper.AddList(SPListCollection
lists, String urlName, String title, String description, Guid featureId,
SPListTemplateType templateType, Boolean& newListCreated)
at
Microsoft.SharePoint.Publishing.Internal.AreaProvisioner.CreateDocumentsDocumentLibrary(SPList
approvalTaskList)
Troubleshooting steps:
Try
activating the publishing feature at the site collection level. If it’s
successful then forthcoming issues will also gets resolved and you can
successfully activates the feature at the subsite level too.
If the error message
stated that the list is already exist then open the site (on which you are
facing problems) in SPD (SharePoint Designer). You will see the same list that
was reflected in the error message. Either delete it or rename it and then try
to activate the feature. It will be successful.
If you are facing
problems by means of GUI then try to activate the same by means of stsadm
command.
Check the ULS logs for
detail error messages
Check event logs for any
specific event ID’s
Isolate the problem
specific to a site, site collection, list, and particular feature at which
level.
If
you have any queries/questions regarding the above mentioned information then
please let me know. I would be more than happy to help you as well as resolves
your issues. Thank you
No comments:
Post a Comment