Error when activating site feature

Trying to get newest version of ExCM working. Feature at Site Collection level activates with no problems. However, when I try and activate the feature at the site level I get the following file not found error.

File Not Found.   at System.ModuleHandle.ResolveMethod(Int32 methodToken, RuntimeTypeHandle* typeInstArgs, Int32 typeInstCount, RuntimeTypeHandle* methodInstArgs, Int32 methodInstCount)
   at System.ModuleHandle.ResolveMethodHandle(Int32 methodToken, RuntimeTypeHandle[ typeInstantiationContext, RuntimeTypeHandle[ methodInstantiationContext)
   at System.ModuleHandle.ResolveMethodHandle(Int32 methodToken)
   at System.RuntimeType.GetMethodBase(ModuleHandle scope, Int32 typeMetadataToken)
   at System.RuntimeType.GetMethodBase(Module scope, Int32 typeMetadataToken)
   at System.Reflection.CustomAttributeData..ctor(Module scope, CustomAttributeRecord caRecord)
   at System.Reflection.CustomAttributeData.GetCustomAttributes(Module module, Int32 tkTarget)
   at System.Reflection.CustomAttributeData.GetCustomAttributes(Assembly target)
   at System.Resources.ResourceManager.GetNeutralResourcesLanguage(Assembly a, UltimateResourceFallbackLocation& fallbackLocation)
   at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents)
   at System.Resources.ResourceManager.GetString(String name, CultureInfo culture)
   at SPSolutions.SharePoint.Delegation.DelegationWebComponentsFeatureReceiver.EnsurePermissionComponents()
   at SPSolutions.SharePoint.Delegation.DelegationWebComponentsFeatureReceiver.OnFeatureActivated(SPFeatureReceiverProperties properties)
   at SPSolutions.SharePoint.SPEquippedFeatureReceiver.FeatureActivated(SPFeatureReceiverProperties properties)
   at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, 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)
   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.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Ideas?

Thanks

Have more questions? Submit a request

7 Comments

  • 0
    Avatar
    Matthew McBride

    Understood. However, as I stated the second site I tried to activate the feature on was never configured to inherit permissions. When I created that site I configured it for "unique permissions" and still when I try and activate the ExCM feature at that site level it tells me "You cannot customize permission levels in a web site with inherited permission levels permission".

    At no point in time did this site inherit permissions.

    As a rule I don't allow inheritance on any of my SharePoint sites in my production portal.

    Hope that calrifies what I see going on.

  • 0
    Avatar
    Matthew McBride

    Is ExCM installed an working in any other site in the same site collection? If so can you send a screen shot of the Delegation Tree (Site Actions -> Delegation Settings -> Modify All Delegation Settings -> Delegation Tree) to softwaresupport@sharepointsolutions.com?

    In addition, can you confirm SharePoint sees this site as a permission parent? The best way to check this would be to try and edit permissions of the site and see if SharePoint informs you that this site is inheriting permissions.

  • 0
    Avatar
    Matthew McBride

    Ok, figured it out. I didn't activate the "Delegation Web Components" feature at the site collection level. I don't recall having to do that in the previous version of ExCM, that's been almost a year ago though so I may have just bricked it.

    Thanks for your help.

  • 0
    Avatar
    Matthew McBride

    In our latest ExCM release (1.0.8346.3) we have added a dependency from to the Delegation Web Components Site feature to the Delegation Components Site Collection feature. Hopefully this will make things a bit more intuitive in the future.

  • 0
    Avatar
    Matthew McBride

    Check that you have .Net Framework 3.5 installed. If not, download it from http://www.microsoft.com/downloads/details.aspx?FamilyID=333325fd-ae52-4e35-b531-508d977d32a6&DisplayLang=en, install and try to activate the feature again.

    Otherwise, make sure your .dll's in the GAC are the latest. Go to C:\Windows\assembly and look for SPSolutions.SharePoint.Delegation. Right click and go to properties, then the Version tab. The latest should be 1.0.8340.1 or later. If they are not, deactivate the Site Collection Feature, then go to Central Administration and click Solution Mangement from the Opertations tab. You may see 1 or 2 solutions beginning with spsolutions.sharepoint.delegation. Click each one and then click Retract Solution and leave the drop down menu for the web applications set to "All content web applications" and click OK. Go back to C:\Windows\assembly and right click on each of the 3 dll's SPSolutions.Common, SPSolutions.SharePoint, SPSolutions.SharePoint.Delegation that exist and click Uninstall. Then go back to Central Administration and click on spsolutions.sharepoint.delegation.wsp and then click Deploy Solution and select the content web application to deploy to. If spsolutions.sharepoint.delegation.templates.membership.wsp still exists on the Solution Management page, you can now retract it from all content web applications and then click Remove Solution - it is no longer used in the latest version of ExCM.

    You should now be able to activate both features.

    David Fisher
    Software Engineer
    SharePoint Solutions
  • 0
    Avatar
    Matthew McBride

    Thanks David, I did not have 3.5 installed (not sure how I missed that). Anyway now I get a different error message when I try and activate the feature at the site level. Activation at the site collection level works with no errors..

     You cannot customize permission levels in a web site with inherited permission levels.   at Microsoft.SharePoint.SPRoleDefinitionCollection.Add(SPRoleDefinition role)
       at SPSolutions.SharePoint.SPSecurityUtil.EnsureRoleDefinition(SPWeb web, String name, String description, SPBasePermissions permissions)
       at SPSolutions.SharePoint.SPEquippedFeatureReceiver.EnsureRoleDefinition(SPWeb web, String name, String description, SPBasePermissions permissions)
       at SPSolutions.SharePoint.Delegation.DelegationWebComponentsFeatureReceiver.EnsurePermissionComponents()
       at SPSolutions.SharePoint.Delegation.DelegationWebComponentsFeatureReceiver.OnFeatureActivated(SPFeatureReceiverProperties properties)
       at SPSolutions.SharePoint.SPEquippedFeatureReceiver.FeatureActivated(SPFeatureReceiverProperties properties)
       at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, 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)
       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.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
       at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
       at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    I definitely do not have the site set up to inherit permissions. The first time I tried it I did so I went in and broke the inheritance. That didn't work so I created a new site with unique permissions from the get-go and get the same error message.

     

    Thanks.

  • 0
    Avatar
    Matthew McBride

    I think you found a small bug in the Delegation Web Components feature activation. This feature should only be allowed to be activated at the permission parent and cannot be activated by a sub-web inheriting permissions. Certainly a better error message can be presented. We will look into adding this behavior into our Q1 2009 release.

    Sub-webs using ExCM always look to the parent permission site for the ExCM components. If they are not installed there then no ExCM feature will be available from the sub-web. This is due to the relations ship ExCM has with SharePoint permissions. We feel trouble could arise if we would allow the ExCM features on sites that are not permission parents.

    For example, you could invite a user to a sub-web. The registering user would then but placed in a SharePoint group, say Members. The registering user would now have access to the sub-web and any resources available to the Members group of any parent site. Potentially, the user could access information that was not intended for them.

Please sign in to leave a comment.