Database Schema not compatible

Last post 05-17-2008 6:25 AM by st_. 5 replies.

Sort Posts:

  • Database Schema not compatible

    06-21-2006, 11:32 AM

    Hi,

    I get the following message when trying to run the Time Tracker pages.

    The 'System.Web.Security.SqlRoleProvider' 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.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.Configuration.Provider.ProviderException: The 'System.Web.Security.SqlRoleProvider' 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.

    Source Error:

    Line 11:         if (Roles.Enabled)
    Line 12:         {
    Line 13:             if (!Roles.RoleExists("ProjectAdministrator"))
    Line 14:             {
    Line 15:                 Roles.CreateRole("ProjectAdministrator");

    Source File: e:\MISintranet\TimeTracker\Global.asax    Line: 13

    Stack Trace:

    [ProviderException: The 'System.Web.Security.SqlRoleProvider' 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.]
       System.Web.Util.SecUtility.CheckSchemaVersion(ProviderBase provider, SqlConnection connection, String[] features, String version, Int32& schemaVersionCheck) +589
       System.Web.Security.SqlRoleProvider.CheckSchemaVersion(SqlConnection connection) +65
       System.Web.Security.SqlRoleProvider.RoleExists(String roleName) +482
       System.Web.Security.Roles.RoleExists(String roleName) +242
       ASP.global_asax.Application_Start(Object sender, EventArgs e) in e:\MISintranet\TimeTracker\Global.asax:13
    


    Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

    I have check the aspnet_SchemaVersions table, which is currently populated with '1'.

    And when I run aspnet_regsql.exe I get the following message:

    Sql error 446: Cannot resolve collation conflict for equal to operation.

    Is there a solution to this?

    Thanks

  • Re: Database Schema not compatible

    06-22-2006, 3:49 AM
    Answer

    It seems not an asp.net issue but a sql server issue. The collation of the which is created by aspnet_regsql doesn't match that of the sql server.

    Do you use Sql Server 2000 or 2005?

    If you use sql express, can it work fine?

    You can also try to change the collation of the SQL server to solve the problem. You can serach for how to do it.

  • Re: Database Schema not compatible

    06-22-2006, 6:31 AM

    Thanks.  I am trying to get this running on SQL Server 2000.

    I have looked at the collation on the server, and tried to use the ALTER DATABASE syntax to change the collation on the database, but this still hasn't worked and when I run aspnet_regsql it still has the same issue.

  • Re: Database Schema not compatible

    06-22-2006, 7:15 AM
    Got it sorted now, had to do it on each table as well.
  • Re: Database Schema not compatible

    10-12-2006, 9:41 AM

    Hi,

    I would appreciate a bit of help as I am having the same problems when using the  ASP.Net Sql Server Registration Tool.  Do I have to change the collation for each of the new tables created in my application db, after the tool has run?

    Many thanks for your help.

    Polly Anna

  • Re: Database Schema not compatible

    05-17-2008, 6:25 AM
    • Loading...
    • st_
    • Joined on 01-21-2006, 7:00 AM
    • Bulgaria
    • Posts 9

    I had this issue but found an easy solution: 

    You just need to take the web application offline and then online using Web Site Administration Tool. That makes some changes in web.config in the pages tag and globalization if needed. Then you can go Smile

Page 1 of 1 (6 items)
Microsoft Communities
Page view counter