ASP.NET Membership error: requires a database schema compatible with schema version '1'

Author → Asif → in .Net → on May 30 2008 11:37PM

Tags: Tags dotnet Tags dotnet Tags Membership Tags error Tags Schema Tags MSSQL

This includes a membership API for managing usernames/passwords and secure credential management, a roles API that supports mapping users into logical groups, a profile API for storing arbitrary properties about both authenticated and anonymous users visiting a web site, a personalization API for storing control customization preferences, a health monitoring API that can track and collect information about the running state and any errors that occur within a web application, and a site navigation API for defining hierarchy within an application and constructing navigation UI (menus, treeviews, bread-crumbs) that can be context specific based on where the current incoming user is in the site.
 
I came across this error when trying to setup .net membership without having asp.net create its own membership database.  Essentially, you need to make sure the following table is in your database:
 
aspnet_SchemaVersions
 
with the following columns and related data:
 
common 1 True
health monitoring 1 True
membership 1 True
personalization 1 True
profile 1 True
role manager 1 True
 
If you add this in your DB that error should go away. Hopefully, this helps someone out there after I nearly pulled my hair out trying to figure it out.


 
Comments RSS

Leave a Comment

Comments (3)

Your welcome
:)

asif said on Nov 18 2008 3:03PM

Worked for me
I copied a database but didn't include the data because I didn't want to transfer over all the users. Got this error and found your fix. It worked! I'll remember to copy that table from now on. Thanks.

Jeff said on Nov 18 2008 2:26PM

Thank you
I've been pulling my hair out on this one. Thank you.

Brad said on Oct 26 2008 8:32PM