Hi !

Trying to connect to an existing MySQL database from LLBLGen (using the wizard).

It works on my colleague's PC not on mine. Unfortunately, not possible at this time to obtain the precise MySQL version on his PC.

I have uninstalled the previous MySQL version (5.5.13) and replaced by the latest (5.5.17).

The database IS functional; can add and query data, etc. (with MySQL Workbench) AND from an ASP.Net app.

Wanting to eliminate the possibility of a MySQL driver version incompatibility between the LLBLGen project created on my partner's PC, I start a brand new LLBGEn project and try to connect to an existing schema : throughout the entire ordeal... the same error message : Bad handshake.

I also get the same message from the ASP.Net app using the LLBLGen entities (on the CreateConnection call)

Details below :

Exception information.

LLBLGen Pro version: v3.1. Build: June 17th, 2011

Exception details:

Message: Bad handshake Source: Devart.Data.MySql Stack trace: at Devart.Data.MySql.a9.p() at Devart.Data.MySql.a9.c() at Devart.Data.MySql.s.f(String A_0) at Devart.Data.MySql.s.a(String A_0, String A_1, String A_2, String A_3, Int32 A_4, String A_5, Int32 A_6) at Devart.Data.MySql.a7.a(MySqlConnection A_0, String A_1, String A_2, String A_3, String A_4, Int32 A_5, Int32 A_6, MySqlProtocol A_7, Boolean A_8, Boolean A_9) at Devart.Data.MySql.a7..ctor(m A_0, MySqlConnection A_1) at Devart.Data.MySql.ao.a(DbConnectionOptions A_0, Object A_1, DbConnectionBase A_2) at Devart.Common.DbConnectionFactory.a(DbConnectionPool A_0, DbConnectionOptions A_1, DbConnectionBase A_2) at Devart.Common.DbConnectionPoolGroup.a(DbConnectionPool A_0, DbConnectionBase A_1) at Devart.Common.DbConnectionPool.a(DbConnectionBase A_0) at Devart.Common.DbConnectionPool.GetObject(DbConnectionBase owningConnection) at Devart.Common.DbConnectionFactory.a(DbConnectionBase A_0) at Devart.Common.DbConnectionClosed.Open(DbConnectionBase outerConnection) at Devart.Common.DbConnectionBase.Open() at Devart.Data.MySql.MySqlConnection.Open() at SD.LLBLGen.Pro.Gui.Controls.WizardPages.MetaDataRetrievalWizard_Step_ConnectionData.TestConnectionData()

Inner exception: <null>

Seen on the Relational Model Data Retrieval wizard : Driver Version : 3.1.05242011.

Couldn't find anything in your forum with the Bad Handshake keywords nor on the web by adding the llblgen keyword... Could I be the only one with the issue....?!

Can you please help....?!

Thank you !

Ben

This seems to happen with some versions of dotConnect in conjunction with some versions of MySql. See this: http://www.devart.com/dotconnect/mysql/revision_history.html

Devart wrote:

6.30.160 17-May-11 ... - The bug with "Bad handshake" exception when connecting to MySQL servers v 5.1.57 and 5.5.12 is fixed

So, I would either update my devart connector, or change my MySql version.

Ben, if an error occurs inside an ADO.NET provider, you also should contact the supplier of the ADO.NET provider to see whether they made a mistake and need to fix something

Gentlemen,

I have updated the Devart "drivers" and my connection problem is solved !

I thank you very much for your support and prompt reply !

I didn't know anything about Devart and that it had a role in accessing MySQL from LLBLGen and I can't help but to wonder why installing the latest version of LLBLGen did not automatically carried that updated versions but given the amount of time spent trying to go through that hurdle..... at this stage, as long as it works..... I'm happy !

I thank you again !

Regards,

Benoit

PS : RE "Ben, if an error occurs inside an ADO.NET provider"; Otis, the call directly to MySQL from ASP.Net worked fine. But I was getting the Bad Handshake error when calling the db via the LLBLGen objects and classes !

AussieBen wrote:

Gentlemen,

I have updated the Devart "drivers" and my connection problem is solved !

Hi Benoit. Good for you!

AussieBen wrote:

I thank you very much for your support and prompt reply !

You're welcome!

AussieBen wrote:

I didn't know anything about Devart and that it had a role in accessing MySQL from LLBLGen and I can't help but to wonder why installing the latest version of LLBLGen did not automatically carried that updated versions but given the amount of time spent trying to go through that hurdle..... at this stage, as long as it works..... I'm happy !

LLBLGen is not responsible for the required 3rd. party software. Normally you have this already installed as you need it to use MySql and .Net. Also LLBLGen can't just drop a dotConnet assembly on your PC: you may want to use another version for some other applications compatibility. Also, the assemblies you use depends on what dotConnect edition you bought.

Anyway, good you have it working now