locked
GUID Error when Activating Sharepoint Enterprise Server Site Collection Features RRS feed

  • Question

  • I am trying to implement the Enterprise Site Collection feature set on my school's Sharepoint 2013 Enterprise implementation, but when I go into Site Settings -> Site Collection Features -> Activate "Sharepoint Server Enterprise Site Collection Features"

    I get the following Error:

    The field with Id {d4a6af1d-c6d7-4045-8def-cefa25b9ec31} defined in feature {0c8a9a47-22a9-4798-82f1-00e62a96006e} was found in the current site collection or in a subsite.

    Could someone walk me through a solution for this? Note that I am not a Sharepoint developer, nor administrator but have been given agency to implement this to utilize InfoPath for form deployment at our Support Center.

    Thanks for your help!

    Thursday, October 1, 2015 11:04 PM

Answers

All replies

  • Disable document set feature in all subsite and site collection and try to enable it again. 

    sachin

    Thursday, October 1, 2015 11:28 PM
  • The Document Sets feature (which is what I think you are referring to) is not currently activated. 

    Any other suggestions or clarifications?

    Friday, October 2, 2015 7:54 PM
  • Did it give you a correlation ID with the error? Do you have access to the server/sharepoint management shell?

    If you have a correlation ID, run:

    Merge-SPLogFile -Path C:\error.log -Correlation guidguid-guid-guid-guid-guidguidguid

    it will create a text file at the paths location so you can view the log and find the exact error

    filter by errors/critical or unexpected


    https://chaddtalks.wordpress.com/

    Friday, October 2, 2015 8:29 PM
  • http://yoursite/RoutingRules/Group%20by%20Content%20Type.aspx

    Do you have any rules in place on any sites?


    https://chaddtalks.wordpress.com/

    Friday, October 2, 2015 8:32 PM
  • I got the correlation ID as well as the logs. Here are the entry's that seem pertinent:

    10/5/2015 14:12 ##### w3wp.exe (0x2A28) 7116 SharePoint Foundation Feature Infrastructure ajppe High [Forced due to logging gap, cached @ 10/05/2015 14:12:48.24, Original Level: Verbose] Skip initializating feature definition reservse lookup table and use delayed initialization. 87b9349d-5d90-d0d9-453b-bb0c9be1b470

    10/5/2015 14:12 ##### w3wp.exe (0x2A28) 7116 SharePoint Foundation Feature Infrastructure eu0m Monitorable SPException thrown: Message: The field with Id {d4a6af1d-c6d7-4045-8def-cefa25b9ec31} defined in feature {0c8a9a47-22a9-4798-82f1-00e62a96006e} was found in the current site collection or in a subsite.. Stack:    at Microsoft.SharePoint.Utilities.SPUtility.ThrowSPExceptionWithTraceTag(UInt32 tagId, ULSCat traceCategory, String resourceId, Object[] resourceArgs)     at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionFieldsAndContentTypes(SPFeaturePropertyCollection props, SPSite site, SPWeb web, SPFeatureActivateFlags activateFlags, Boolean fForce)     at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionElements(SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, SPFeatureActivateFlags activateFlags, Boolean fForce)     at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, SPFeatureActivateFlags activateFlags, Boolean fForce)     at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly)     at Microsoft.SharePoint.SPFeatureCollection.CheckSameScopeDependency(SPFeatureDefinition featdefDependant, SPFeatureDependency featdep, SPFeatureDefinition featdefDependency, Boolean fActivateHidden, Boolean fUpgrade, Boolean fForce, Boolean fMarkOnly)     at Microsoft.SharePoint.SPFeatureCollection.CheckFeatureDependency(SPFeatureDefinition featdefDependant, SPFeatureDependency featdep, Boolean fActivateHidden, Boolean fUpgrade, Boolean fForce, Boolean fMarkOnly, FailureReason& errType)     at Microsoft.SharePoint.SPFeatureCollection.CheckFeatureDependencies(SPFeatureDefinition featdef, Boolean fActivateHidden, Boolean fUpgrade, Boolean fForce, Boolean fThrowError, Boolean fMarkOnly, List`1& missingFeatures)     at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly)     at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, Int32 compatibilityLevel, String featureName, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly, Boolean fIgnoreMissing, SPFeatureDefinitionScope featdefScope)     at Microsoft.SharePoint.WebControls.FeatureActivator.ActivateFeature(Guid featid, Int32 compatibilityLevel, SPFeatureDefinitionScope featdefScope)     at Microsoft.SharePoint.WebControls.FeatureActivatorItem.ToggleFeatureActivation()     at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)     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) 87b9349d-5d90-d0d9-453b-bb0c9be1b470

    Friday, October 9, 2015 10:30 PM
  • Hi doulost,

    Please try to activate the feature via Enable-SPFeature PowerShell cmdlet with -Force parameter.

    More information about the cmdlet, you can refer to:

    https://technet.microsoft.com/en-us/library/ff607803.aspx?f=255&MSPPError=-2147217396

    A blog about this similar topic for your reference:

    http://www.thorntontechnical.com/tech/sharepoint/the-field-with-id-defined-in-feature-was-found-in-the-current-site-collection-or-in-a-subsite#.ViCzfnnouM9

    Thanks,

    Wendy


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Proposed as answer by Victoria Xia Thursday, October 22, 2015 8:48 AM
    • Marked as answer by Victoria Xia Monday, October 26, 2015 6:54 AM
    Friday, October 16, 2015 8:22 AM