+1-888-365-2779
Try Now
More in this section

Forums / Set-up & Installation / Role feture is not enabled.

Role feture is not enabled.

9 posts, 0 answered
  1. Bob Howard
    Bob Howard avatar
    22 posts
    Registered:
    06 Jan 2008
    07 Jan 2008
    Link to this post
    During the DB creation process, I get the following error:

    Role feture is not enabled.


    Yup, that's not a typo from me, "feture" is the actual spelling the error had.  I don't know the cause of this error.  It appears after asking me for what database I would like.  I am using the Community Edition.
  2. Rebecca
    Rebecca avatar
    536 posts
    Registered:
    24 Sep 2012
    07 Jan 2008
    Link to this post
    Hi Bob Howard,

    It is odd that you get the 'Role feature is not enabled' error. The roles are not disabled for the Community edition of Sitefinity. Actually, they are set to false in the web.config file, but set to true programmatically at the second step of the project creation wizard, that is, when you are asked to choose the database.

    Perhaps a workaround would be to open the web.config file with some text editor and change the property to true (when this error occurs). You should change 

    <roleManager enabled="false" cacheRolesInCookie="true" defaultProvider="Sitefinity">

    to

    <roleManager enabled="true" cacheRolesInCookie="true" defaultProvider="Sitefinity">


    Save the web.config and refresh the page. Hope this would help.

    Please let us know whether this helps and whether this happens on each new project creation. Looking forward to hearing from you.

    Sincerely yours,

    Rebecca
    the Telerik team


    Instantly find answers to your questions at the new Telerik Support Center
  3. Bob Howard
    Bob Howard avatar
    22 posts
    Registered:
    06 Jan 2008
    07 Jan 2008
    Link to this post
    It now works, but I found that the roles were enabled.  The wizard may changed this setting  during the process and refreshing the page made it work, or the other possible solution may have something to do with me creating an application name in IIS for the virtual directory. I had set a name because I couldn't get the installation process to run through. Removing the application name in IIS could have solved the problem.  What may have caused it?
  4. Rebecca
    Rebecca avatar
    536 posts
    Registered:
    24 Sep 2012
    08 Jan 2008
    Link to this post
    Hello Bob Howard,

    Glad to know it works now.
    We will definitely need more time to investigate the possible cause of this error. It may have occurred because you had a virtual directory with the project name you wanted.
    Please
    let us know if you encounter this exception the next time when you try to create a new project.

    Regards,
    Rebecca
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  5. Thomas
    Thomas avatar
    1 posts
    Registered:
    09 Jan 2008
    10 Mar 2008
    Link to this post
    Just an FYI:  I too received this error when creating a project in community edition.  I also received after patching 3.1 with the 3.2 patch attempting to log into the site.  The fix in the config file did fix the problem though.
  6. Rebecca
    Rebecca avatar
    536 posts
    Registered:
    24 Sep 2012
    10 Mar 2008
    Link to this post
    Hello Thomas,

    Thanks for letting us know about this. We also get this error quite often, even with the 3.2 Standard edition. It seems the web.config takes a little longer to update, so a page refresh does the trick.
    So far, we haven't been able to find a solution for this.

    Regards,
    Rebecca
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  7. Josef Rogovsky
    Josef Rogovsky avatar
    39 posts
    Registered:
    04 Sep 2012
    03 Apr 2008
    Link to this post
    Just got this same error.

    A page refresh solved it.

    Thanks for the tip, Rebecca.
  8. Brook
    Brook avatar
    39 posts
    Registered:
    21 Mar 2007
    06 Jul 2008
    Link to this post
    I received this error during initial set-up (right after entering the DB conection settings to use SQL2005) using the Standard Edition project on a Vista Ultimate machine with the latest 3.2 1616 release.  I do not get the error when installing the same way on an XP machine, just an FYI.  The page refresh lets you continue and it does not appear to miss any thing as far as application settings etc...
  9. John
    John avatar
    4 posts
    Registered:
    05 Aug 2008
    09 Nov 2009
    Link to this post
    Same issue here.... Clean install, on a clean OS, with Standard Edition 3.7. got the error right after entering DB info. Hit refresh and it worked.... didnt do anything other than look the issue up here.
Register for webinar
9 posts, 0 answered