• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 650
  • Last Modified:

Can't create MySQL Connection Manager for BIDS 2012 project

I am trying to read data from a MySQL database by creating an SSIS package in BIDS (MS Visual Studio). Here's the environment:

Development Machine is Windows 7 64 bit.
MS Visual Studio 2012
MySQL Version 5.0.80
MySQL ODBC 5.3 ANSI Driver version 5.03.04.00 or MySQL ODBC 5.3 Unicode Driver version 5.03.04.00

I was able to create a System DSN and a User DSN both of which test successfully when I use Test Connection button on ODBC dialog. I believe I created both DSNs from the Administrator Tools Data Sources (ODBC) program. I've seen references about having to use the 32 bit version and I've run c:\windows\syswow64\odbcad32.exe but it just opens the same interface and both DSN appear.

Attempt using ODBC provider:
1. Create a new Connection Manager from BIDS
2. Select ODBC manager type
3. Configure ODBC Connection Manager dialog appears. I click New
4. The Provider drop down says ODBC and is disabled.
5. I select the User DSN (The System DSN doesn't appear) and enter the user name and password and press Test Connection.
6. I get an error that the connection failed ERROR [IM014][Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application.


Attempt using ADO.NET provider:
1. Create a new Connection Manager from BIDS
2. Select ADO.NET manager type
3. Configure ADO.NET Connection Manager dialog appears. I click New
4. I select .Net Providers\ODBC Data Provider.
5. I select the User DSN (The System DSN doesn't appear) and enter the user name and password and press Test Connection.
6. I get an error that the connection failed ERROR [IM014][Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application.

I tried both of the above methods by entering the connection string directly (specifying server, port, database, uid and pwd) but that results in an error stating "The ConnectionString property has not been initialized".

I'm at a loss as to what to try next.

Thanks for your assistance.
0
ZekeLA
Asked:
ZekeLA
  • 2
1 Solution
 
Alpesh PatelAssistant ConsultantCommented:
Make sure both are on same platform (32 or 64 bit).

Here, if driver is not available then Download and install drivers  (32 or 64 bit).
0
 
ZekeLAAuthor Commented:
Still no luck but here's what I tried"

1. I checked the source MySQL database and according to MySQL Workbench 6.1 Server Status, my source is compiled for Win64. So I assume both need to use 64 bit.
2. I uninstalled all of the MySQL drivers.
3. I rechecked MySQL documentation and downloaded MySQL Driver for Connector / ODBC version 5.2.7 (http://dev.mysql.com/downloads/connector/odbc/5.2.html) since other documentation says it supports MySQL 4.1 and later while ODBC version 5.3.4 said MySQL 5.5 and later. (http://forums.mysql.com/read.php?3,614123,614123#msg-614123 and http://forums.mysql.com/read.php?3,617691,617691#msg-617691)
4. I created a new User DSN using %systemdrive%\Windows\System32\Odbcad32.exe which should generate 64 bit DSN. (http://support2.microsoft.com/kb/942976)
5. I repeated my attempt to create a new ODBC connection manager. And I got the same error as before: Architecture mismatch.

Suggestions?
0
 
ZekeLAAuthor Commented:
Finally got it. There were two issues:

1. The source is 32 bit, not 64 bit as MySQL Workbench seemed to indicate.
2. The original driver I downloaded was either the wrong version (5.3.4) or the wrong OS (64 bit). Per MySQL documentation, version 5.3.4 is for MySQL 5.5 or later but the error message was architecture mismatch.

Correct solution was to uninstall previous attempts and download 32 bit version of MySQL ODBC 5.2.7 driver. I was able to connect with a User DSN.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now