MySQL Bugs: #43294: MySQL Connector/Net 5.2 on W2K Advanced Server does not make registry entries

Bug #43294	MySQL Connector/Net 5.2 on W2K Advanced Server does not make registry entries
Submitted:	1 Mar 2009 22:51	Modified:	5 Mar 2009 17:31
Reporter:	Pierre Landau	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / NET	Severity:	S1 (Critical)
Version:	5.2	OS:	Windows (2000 Advanced Server)
Assigned to:		CPU Architecture:	Any
Tags:	Connector/Net, W2K, Windows 2000 Server

Description:
I would like to use the MySql/Net Connector on our Windows 2000 cluster (the old ODBC one worked just fine but won't work with newer .NET code).  Running the installer seems to work, but the provider does not get listed.  Examining the registry shows that none of the required entries is made.  I would make them by hand, but don't have an exhaustive list.

How to repeat:
Install MySql/Net Connector 5.2 on Windows 2000 Advanced Server.  Use "Connection Editor.hta" or similar tool to list the available connectors.  MySql OLEDB connection is not listed and not available.

Suggested fix:
At the very least, document the specific list of registry entries or provide a .REG file for manual installation.

Hi Pierre and thanks for your report.

> I would like to use the MySql/Net Connector on our Windows 2000 cluster (the old ODBC one worked just fine but won't work with newer .NET code).

Two things; I do not have Windows2000 cluster (and, afaik, it's EOL-ed) and what is "new" and "old" .NET code? This is no description of problem, right?

> Running the installer seems to work, but the provider does not get listed. Examining the registry shows that none of the required entries is made. I would make them by hand, but don't have an exhaustive list.

Ok.

> Install MySql/Net Connector 5.2 on Windows 2000 Advanced Server. Use "Connection Editor.hta" or similar tool to list the available connectors. MySql OLEDB connection is not listed and not available.

I can't install c/NET on W2KAS, see above. Also, there is no such thing as "MySql OLEDB connection", ie. Sun does not provide MySQL OleDB driver. OleDB used is one from OS. So I'd look for:
  DataSource: Microsoft ODBC Data Source
and
  Data provider: .NET Framework Data Provider for ODBC
as this is the only way to mix ODBC with .NET. In any case, it works on my box (Win2K8x64 server).

> At the very least, document the specific list of registry entries or provide a .REG file for manual installation.

This is not possible as most of the install work is done in GAC. Please check .NET framework config and see what's wrong there.

Please clear up the report and fill in huge gaps for me. I'm also wondering over this unnatural mix of ODBC and .NET... Why are you implementing things this way?

Clarification: We were running a service on a Windows 2000 cluster. C++ code called COM objects which in turn called ODBC MySQL 3.51 driver, which worked just fine.  I recently rebuilt the service under VS2008, and wanted to use the OleDbConnection class to simplify the architecture.  I installed the MySql connector on my dev machine (xp sp3), and this worked just fine, so I was surprised when the install of the MySql connector on the cluster worked, but the OLEDB connector was not available.  Looking at the registry on my local machine, there are a number of entries in HKCU and HKCR that are not in the Windows 2000 registry after install.

Ahhhh, finally something I can live with... Microsoft removed default OleDB provider from x64 versions of their OS. However you might be able to get it somewhere on their site...

In the end, I gave up on OleDB and went back to Odbc, which works like a charm.  Thanks.

Pierre, was it x64 OS after all?