This project is read-only.

CKS:FBA Self Management Fix

Topics: Internet/Extranet Edition
Mar 24, 2009 at 4:05 PM
Many people report there's a problem installing/activating the FBA self managment feature. If you try, you get a message like this ""Dependency feature with id 01aa8d8b-000a-4c35-8f4f-5d1280377650 for feature 'FBAManagementSelf' (id: 23c44729-fb03-4882-a0bf-c6fb3ddd81fd) is not installed."

The self management feature can be found in the source tree but was cut from the release (not sure why).

To activate the feature find the FBAManagementSelf folder in your FEATURES folder in the 12 hive. Edit Feature.xml with a text editor and remove the last line in the ActivationDependencies section:

    <ActivationDependency FeatureId="8AF74562-1972-4373-A427-EA9F700088EC" /> <!-- Change Password Webpart -->
    <ActivationDependency FeatureId="311B4577-4677-459d-9B10-8989DA574017" /> <!-- Login Webpart -->
    <ActivationDependency FeatureId="68080064-E494-4807-A6A7-4A92DEDD7CE5" /> <!-- Membership Request Webpart -->
    <ActivationDependency FeatureId="39855F49-B8E5-492a-AFE8-FE93BF139F57" /> <!-- Password Recovery Webpart -->
    <ActivationDependency FeatureId="01AA8D8B-000A-4c35-8F4F-5D1280377650" /> <!-- My Settings Save Override -->    

Remove the last line with the feature id starting with "01AA8..."

You can now activate the feature from the site collection features screen.

Mar 26, 2009 at 8:59 PM
I followed these steps and got past the dependency error.  Thank you.

Now, when I add the web part to a page, there is an unexpected error thrown. 

I found others have posted this issue in the Issues list and Discussions, but no one seems to have a solution.

Oct 1, 2009 at 4:41 AM

I had removed the last line activation dependency in the feature.xml, then I save the file and I try to activate it again from the Site Collection features screen. However, the error message "Dependency feature with id 01aa8d8b-000a-4c35-8f4f-5d1280377650 for feature 'FBAManagementSelf' (id: 23c44729-fb03-4882-a0bf-c6fb3ddd81fd) is not installed." still occur. Why? Any idea how to solve it?

Dec 13, 2009 at 8:06 AM

cindytan, it might be the same thing problem I had. I.e. I modified the features.xml but repeated restarts of the IIS Web site for the SharePoint Web Application of interest refused to acknowledge the modifications.  I finally stopped the IIS server and then restarted it and SHAZAM, the dependency error went away.  Next problem was that attempts to use the page with the FBA Web parts errored, but I determined this was because the SP site collection that the CKS:FBA featue had been deployed to (i.e. the -url parameter used for the install script of the feature (see its "deploy.cmd" file) was NOT what I was using to access the SharePoint site.  Once I added an alternate access mapping in central administration for the URL (i.e. an externally DNS domain name for the MOSS server), it worked. 

Dec 15, 2009 at 9:44 AM

bsimer, the issues found with alot of people installing CKS FBA has now been resolved in the next patch update release that I've uploaded back up here (see ID 4664 to download the patch)

Hopefully this will be in the next release when it has been approved by the community.

This patch upgrade contains the following changes from the previous version back in Oct 2 2008.


1. Customise email messages (12\template\features\layouts\fba\emails\*.xslt) that gets sent to  users upon pending for new membership request, membership approval email, membership rejection  email and password recovery emails has been updated with meaningful message and new variables


2. Feature.xml under FBAManagementSelf folder contains error when people tried to install and  activiate the FBA self management feature (see So the featureID (23c44729-fb03-4882-a0bf-c6fb3ddd81fd) has been commented out 

3.The following code has been updated:


3.1 membershiprequest.cs


3.2 MembershipRequestControl.cs

Oct 22, 2010 at 5:13 AM

Today I've found a solution to this issue.

In visual studio, select "display all files", this way you'll see some hidden files, and the missing feature.xml and user control are in a filder called "CUT".

Move the feature and user control to their respective folders and build the solution, deploy and the "self management" feature now can be activated.

Also this makes to appear the self management web parts (login, change pwd, etc) and they work fine.

Don't delete or comment the feature because that breaks other stuff.

I google this and nobody seems to find out those hidden files, they just drop the feature line.

I downloaded the latest change set before doing this.

Hope this helps,