Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

Import from MySQL worked via 64 bit Import/Export Wizard, saved that working version, but can't run the saved one

$
0
0

Although in the end I gave up and took the long way around (installed 32 bit drivers, recreated in BIDS using the 32 bit drivers, etc., and was successful in the end using THAT method), I'm still left wondering why and how it worked directly while using the Import/Export wizard, but the saved package from that same successful import/export never ran.

What I did try: (Outcome always Error: 0xC0047062, "Could not create a managed connection manager")

  • Environment = Win7 64 bit, running 64 bit Import/Export wizard from start menu, with 64 bit MySQL drivers, the MySQL driver configured with the INITIAL STATEMENT configured to "Set sql_mode='STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,ANSI_QUOTES';"
  • Created a very simple import/export process, and saved to file system (in parallel, the import/export SUCCESSFULLY ran from the wizard).   (Separately, also tried saving to SQL Server) 
  • Find and run the 64 bit DTExec version from the command line
  • Tried running that saved version, got the error listed above.
  • Also tried.. a bunch of other things, 32 bit DTExec, the UI version of DTExec from double clicking the package, everything I could think of, including:
    - Encrypt the package (since the MySQL driver has sensitive data (username/pw for the MySQL driver)),
    - and Saving to SQL server.  Neither of those worked.

Keep in mind, this isn't the more common question, "It ran in BIDS but not as a package", this is "It ran in Import/Export Wizard but not as a package.  (Or in BIDS, until I installed 32 bit drivers).

So, for my own education.. why?  Thanks in advance.







Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>