'system.web.security.sqlmembershipprovider' Requires A Database Schema Compatible With Schema Version '1'

I want to use profiles and was able to use aspent_regsql -A p to install the tables. I can see them throughout SQL management studio. I'm actually using SQLExpress 2005, and my db

Solution 1:

Well, fool of me. I was quite sure it was a problem with SQLExpress database but it was actually my web.config file that was totally weird. I got it to work by adding the correct properties to the providers:

<connectionStrings><addname="RGConnectionString"connectionString="Data Source=(local)\SQLExpress;Initial Catalog=aspnetdb;Integrated Security=true"providerName="System.Data.SqlClient" /></connectionStrings><system.web><membership><providers><removename="AspNetSqlMembershipProvider" /><addname="AspNetSqlMembershipProvider"type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"connectionStringName="RGConnectionString"enablePasswordRetrieval="true"enablePasswordReset="true"requiresQuestionAndAnswer="true"requiresUniqueEmail="true"passwordFormat="Clear"maxInvalidPasswordAttempts="5"minRequiredPasswordLength="8"minRequiredNonalphanumericCharacters="0"passwordAttemptWindow="10"passwordStrengthRegularExpression=""applicationName="/" /></providers></membership><profile><providers><addname="ProfileProvider"type="System.Web.Profile.SqlProfileProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"connectionStringName="RGConnectionString"applicationName="/" /></providers></profile></system.web>

Solution 2:

This may happen if you script your database and not populate [aspnet_SchemaVersions] table. This table holds information about membership table schema. If this table empty, you will see error about membership version.