Tell Us About Your Business

Your name:
Business name:
E-mail address:
Phone number:
Comments or questions:
Subscribe to our newsletter:
Tickets |  Project Management |  207-347-7360

Search

Popular Tags

Archive

About Dirigo

Dirigo's roots are in retail, catalog, television and radio direct response marketing. We're responsible for multi-million dollar web businesses. Whether its sharing our experience and expertise or helping connect you to some of the best thinkers in our industry, we dig deep to find opportunities that drive revenue.

How to fix the error The SystemWebSecuritySqlMembershipProvider requires a database schema compatible with schema version 1

July 01 / Payson Welch, Sr. Tech

Recently while upgrading an ASP.NET 2.0 project to ASP.NET 4.0 I ran into a database issue. After creating a new Sql Server 2008 database project and setting up my isolated work environment, I received the following error:

The 'System.Web.Security.SqlMembershipProvider' requires a database schema compatible with schema version '1'. However, the current database schema is not compatible with this version. You may need to either install a compatible schema with aspnet_regsql.exe (available in the framework installation directory), or upgrade the provider to a newer version.

According to several sources on the Net you need to add an applicationName attribute to your provider definitions in web.config. So any Membership Framework provider definition that has for instance "connectionStringName" will also have to have this attribute: applicationName="NoSingleSlash". The caveat is that you cannot use applicationName="/". You have to provide a multiple word name.