Bug #61734 Error "Unable to generate the model..." when configurin .edmx file from VS2010
Submitted: 4 Jul 2011 10:38 Modified: 4 Jul 2011 15:38
Reporter: Roberto Zanin Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / NET Severity:S2 (Serious)
Version:Connector 6.3.7, MySql 5.1.32 OS:Windows (Vista SP2 32bit)
Assigned to: Bogdan Degtyariov CPU Architecture:Any
Tags: entity framework, model generation, MySql Connector .NET 6.3.7

[4 Jul 2011 10:38] Roberto Zanin
Description:
After updated the connector to version 6.3.7, when I try to update model or creating new one, VS2010 EF designer returns me the follow error:

Unable to generate the model because of the following exception: 'An error occurred while executing the command definition. See the inner exception for details. Unknown table 'parameters' in information_schema'.

Other users have the same problem, see here: 
http://forums.mysql.com/read.php?38,424832,424832

How to repeat:
Install MySql Connector .NET 6.3.7

Run VS2010 (my version is with SP1)

Add new "ADO.NET Entity Data Model", in the wizard select "Create model from Database", set up the connection and select the tables, press finish and in the output appears the error and the model is empty.

Suggested fix:
To workarond at this problem I come back to version 6.3.6 but this isn't a solution.
[4 Jul 2011 13:00] Bogdan Degtyariov
Roberto,

I could not repeat the problem. 
The model generated without any problems for me (entity table and version of Connector/NET are outlined in red).
Please check the VS2010 screenshot (data_model_6.3.7.png).

Do you have any ideas what else I can try?

Also, the bug severity is incorrect. S1 means no workarounds exist at all. In your case installing 6.3.6 resolved the problem (it might be unacceptable in your particular case, but this is another thing).
[4 Jul 2011 13:01] Bogdan Degtyariov
screenshot of VS2010 and data model

Attachment: data_model_6.3.7.png (image/png, text), 115.50 KiB.

[4 Jul 2011 13:16] Roberto Zanin
I use (for some reasons) in my project the .NET runtime version 3.5 and then the EF1.

Maybe is this the problem?
[4 Jul 2011 15:38] Roberto Zanin
I reinstalled the version 6.3.7 and I did some tests.

- Target .net framework 3.5(EF1) or 4.0(EF4) any difference, same error.

- In my machine I also have VS2008 (SP1), I tried to create a new model but in the wizard after setted up my data connection appears the follow error:

---------------------------
Microsoft Visual Studio
---------------------------
An error occurred while connecting to the database. The database might be unavailable. An exception of type 'System.Data.ProviderIncompatibleException' occurred. The error message is: 'The store data provider failed to return information for the StoreSchemaMapping request. See the inner exception for details.

The inner exception caught was of type 'System.ArgumentNullException', with this error message: 'Il valore non può essere null.

Parameter name: stream'.'.
---------------------------
OK   
---------------------------

I attach the VS2008 error screenshot and a file with the sections of the machine.config file of my .net framekork that contain "mysql"(maybe this help).
[4 Jul 2011 15:39] Roberto Zanin
VS2008 EF model wizard error

Attachment: VS2008 connection error.jpg (image/jpeg, text), 54.66 KiB.

[4 Jul 2011 15:40] Roberto Zanin
Sections of machine.config that contain "mysql"

Attachment: machine.config sections.txt (text/plain), 8.03 KiB.

[7 Jul 2011 21:40] Leandro Lustosa
Hello, I have the same problem, when I generate the model generate this error:

An error occurred while executing the command definition. See the inner exception for details.
	Unknown table 'PARAMETERS' in information_schema

My configuratiions:
VS2010
Connector 6.3.7.0 or Connector 6.4.3.0
MySql Server 5.1x
Win 7 64bits

If I use the MySql Server 5.5 with the configurations above works fine.

I read the documentation of connectors and see that version 6.3.7.0 works with MySql Server 5.1, so whats get wrong?
[12 Aug 2011 19:14] John Lee
Had this same problem and ended up upgrading to the latest MySql connector. Everything works fine now. Seems like it was a bug in version 6.3.7...