Unable to initialize provider. Missing or incorrect schema.

Question

Hello,

I have upgraded my server machine to use MySQL Connector 6.3.4 and in our website we also added Membership role provider.

When I run the website I am getting this error.

Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unable to initialize provider. Missing or incorrect schema.

My sql server is version 5.0.90 community-net.

Is there any setting which have to be changes on server side while upgrading connector

This is tag in my web.config file.

Since when I run the website on local machine it will run successfully, but on server I am not able to run it and getting above error. There is no mistake in connection string

What are server side setting which we to do while upgrading the connector....

thanks

Answer 1

Hi Aahushi,

I myself running into the same problem. I m using Mysql connector 6.3.0.0 So far I came across following suggestions when seaching on net:

1) Add "MySql.Data.dll" & "MySql.Web.dll" into your application  "bin" folder.
2) Add reference to above to dlls in your application .
3) Add autogenerateschema="true" in your web.config file for required sections.
4) Check your Mysql connector version - make sure that the one that is in your bin folder is mentioned in your web.config file. 
5) Check your connection string - make sure it is correct and connected successfully.
6) Check mysql membership related table structure.
7) Check schema version in "my_aspnet_schemaversion" table (e.g since you have upgraded to newer version I insist you should check this).
8) If the problem is on remote machine (e.g Production Server) you may wan to check this : http://www.reggieburnett.com/referencing-connectornet-on-a-remote-machine 

I m sure you may gone through this list but I would like you to check schema version in "my_aspnet_schemaversion" table (e.g compare "version" field value of your local and remote table) since your upgrading to newer version.

BTW: I have checked this list for my problem but it did not help. I hope it may be of some help to you.

Edit: Hi, We are able to fix this error by following:

1) Deleted the tables for memberships in the db and had the mysql membership provider regenerate them
2) than set the Aministration.config file to trust the Mysql Membership Provider (e.g related to IIS admin)

Regards,

Gaurav