MySQL Bugs: #44460: "Failed to open connection to database"

Bug #44460	"Failed to open connection to database"
Submitted:	24 Apr 17:19	Modified:	26 May 15:15
Reporter:	Tonci Grgin
Status:	Closed
Category:	Connector/Net	Severity:	S2 (Serious)
Version:	6.0.3	OS:	Microsoft Windows (W2K8 x64)
Assigned to:	Reggie Burnett	Target Version:
Triage:	D2 (Serious)

Description:
While creating new dataset I get following error:
  Failed to open a connection to database.
  Cannot load type with name
  'MySQL.Data.VisualStudio.StoredProcedureColumnEnumerator'

How to repeat:
See attached image.

Suggested fix:
-

Everything shown on image.

Attachment: bug44460.jpg (image/jpeg, text), 139.00 KiB.

However, same connection (and stored procedures) work in server explorer. I tried varying
c-string options to no avail.

I observe the "Cannot load type with name
'MySql.Data.VisualStudio.StoredProcedureColumnEnumerator'." bug with VS 2008 only, not
with VS 2005.

I am connecting to a remote machine, specifying an IP address for the server.  The
database version on the remote machine is Community 5.0.67.

My environment is a WinXP 32-bit virtual machine with VS 2005 SP1 and VS 2008 SP1
installed side by side with a snapshot taken after the first run of each IDE (to perform
the initial environment setup).  I roll back to this snapshot to test new connectors.

i have the same error on make new connect from c# 2008
mysql.data.visualstudio.storedprocedurecolumnenumerator
to local mysql and to remote the same error

i cnot use the Mysql connector from c#

I have the same error for VS 2008
Win XP SP3 - 32 bit

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/73402

fixed in 6.0.4

I didn't see the errors listed in this bug report but when I tried to use an sproc in a
dataset the wizard dialog simply disappeared.  I also found that one of our ddex xml
files was referencing the StoredProcedureColumnEnumerator type that was no longer
available.  I have now fixed that and successfully used a sproc in a dataset.  If this
bug persists then please reopen but I think this fixes it.

how, can I get the patch ? is there any possibility to get it as a compiled version ?

you can get the source code from svn.mysql.com

thanks.. is there also a already compiled version ? I have problems compiling the
sources..

Not right now.  In the past we've tried to have an automated snapshot build facility and
I'll try again to set that up. Until then you'll have to build yourself or wait for my
release.

thanks.. is there any possibility to get around this bug? (without new version)
what do you think you will release this?

Compling still throws errors I can´t get around:
src\MySql.VisualStudio\Resources\PackageLoadKey.txt
isn´t found !

thank you..

Stephan, remove it from, I think, Assembly.info...

Is there any update on this, can we expect the complied patch in next few days or should
we look for some other alternative? Thanks. Aries

When will a new version that solves this problem? I have tried to compile the patch but I
get errors. 

Should we wait a long time? 

Thank you.

An entry was added to the 6.0.4 changelog:

When creating a new DataSet the following error was generated:

Failed to open a connection to database.
Cannot load type with name 'MySQL.Data.VisualStudio.StoredProcedureColumnEnumerator'

Hi
Do we know when the fix for this bug is gonna be rolled into the msi installer?
I get... 
Cannot load type with name 'MySQL.Data.VisualStudio.StoredProcedureColumnEnumerator' and
trying earlier versions of the connector throw up different issues.

Thanks

I am having the same issue with VS 2008 on windows vista 32 bit. I am not sure how to
compile the bug fix can some one please give me some instructions.

can someone point *where* is the information related on *how* to compile this so-called
patch ? because I have done the usual search on google and found nothing. been reading
the docs also, none useful.

Sarasa, I don't get it... 6.0.4 is out and available, why would you want to compile the
patch?