Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

SSIS mysql to mssql Expand / Collapse
Author
Message
Posted Wednesday, September 18, 2013 9:14 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, May 12, 2014 2:58 AM
Points: 8, Visits: 50
I make same package ssis in visual studio 2010.
I load data from mysql to mssql 2012.
I created ADO.NET source(connect with mysql) and OLE DB (connect with mssql).
When I started debugging in visual studio date load from mysql to mssql without problems.
After I loaded ssis in mssql and make job in sql agnet.
When I start job I have "error ADO NET Source has failed to acquire to the connection with the following error message "Could not create a managed connection manager".

What should I do?
Post #1495974
Posted Wednesday, September 18, 2013 11:45 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, April 2, 2014 8:05 AM
Points: 285, Visits: 334
Hi
Did you set Run64BitRuntime as false?

Br.
Mike
Post #1496049
Posted Wednesday, September 18, 2013 2:10 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Tuesday, July 8, 2014 8:28 AM
Points: 3,099, Visits: 7,785
First thing that comes to mind is that when you were debugging the package, you were running it from your computer. Then you tried running it from the server.

Does the server have the required driver?




Alvin Ramard
Memphis PASS Chapter

All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.
Post #1496122
Posted Thursday, September 19, 2013 1:32 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:12 AM
Points: 13,199, Visits: 10,062
michal.lisinski (9/18/2013)
Hi
Did you set Run64BitRuntime as false?

Br.
Mike


This is a design time setting only and doesn't affect the execution of a package on the server.

However, you might be on the right track: it's possible the server is 64-bit and hasn't the 64-bit providers installed, something Alvin was also guessing at.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1496244
Posted Thursday, September 19, 2013 1:47 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, May 12, 2014 2:58 AM
Points: 8, Visits: 50
Ok I see problem.
First I ran package on my computer and I didn't problem.
When I ran on other server I had problem.
I thint than problem is with ODBC on server but I don't find mistake.
Post #1496246
Posted Thursday, September 19, 2013 2:18 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:12 AM
Points: 13,199, Visits: 10,062
Is the ODBC 32 or 64-bit?



How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1496258
Posted Thursday, September 19, 2013 2:42 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, April 2, 2014 8:05 AM
Points: 285, Visits: 334
Hi Koen

I've already met with that problem. Package tested on wkst with 32bit odbc and moved to 64bit environment, of course there were installed 32-bit odbc on the server. It started in 64bit mode first but unfortunately without success.

I'm not sure if that's it, but Imho it's a good thing to check first.

Br.
Mike
Post #1496267
Posted Friday, September 20, 2013 12:04 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, May 12, 2014 2:58 AM
Points: 8, Visits: 50
I tested on win7 64 and after i try run on win 2008 64. On win7 is ok but on win 2008 is problem.
On win 7 I have mysql odbc 5.1 driver. On win 2008 I have mysql odbc 5.2 ansi driver. In win 2008 I create DSN user and I tryed connect with datebase and I didn't problem. Why doesn't package run?
Post #1496715
Posted Friday, September 20, 2013 1:52 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, May 12, 2014 2:58 AM
Points: 8, Visits: 50
I changed in ADO NET provider from mysql data provider on odbc data provider.
Next I created DSN user and I ran test. Connect test DSN user the end succes.
I ran package on visual studio and succes but when I try run on mmsm I have error [im002].
Post #1496738
Posted Friday, September 20, 2013 2:12 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, April 2, 2014 8:05 AM
Points: 285, Visits: 334
Hi
Did you configure new DSN from C:\Windows\System32\odbcad32.exe or C:\Windows\SysWow64\odbcad32.exe?
And could you please answer Koen's question.

Regards
Mike
Post #1496745
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse