I have several versions of SQL Server and have been using SQL 2008 on a regular basis due to this issue.

Our SQL 2014 when I do the Import Data process, it opens up the dialog window, hit next, and the data source is currently defaulting to ".NET Framework Data Provider for IBM i" - when it does this it immediately errors out with:

"An error occurred which the SQL Server Integration Services Wizard was not prepared to handle.

Additional Information:
> Exception has been thrown by the target of an invocation (mscrolib)
>> Failed to find or load the registered .NET Framework Data Provider (System.Data)"

It immediately crashes/closes the Import/Export wizard with me unable to change the data source to what I need it to be.

My 2008 defaults to SQL Server Native Client 10.0 and does allow me to change to that same option (at which point it errors) but it does not close the wizard.

I need a way to either:
> Default the starting Data Source to be something else
> Fix whatever error is causing it to crash - I am at a loss as to what the error is looking for
> Not have the wizard crash whenever it defaults to this source.

Any of the above solutions would work fine - but at the moment I am unable to use the Import/Export wizard at all in SQL 2014.

Thanks

Seems to be this is an Registry issue. Some dll file not register properly. I have face this issue couple of times

on lower version you can try with this:

Goto - Run -> cmd

type: regsvr32 dts.dll

But not sure this will help to fix your issue . Please try and do reply.. with output

Looks like I might need to look into something else as well.

I typed into the Command Prompt like you said and received an error:

"The module dts.dll was loaded but the call to DllRegisterServer failed with error code 0x80070005"

When I look online to look more into this, it looks like that error is a permission issue. I'm going to get with our IT and see if it something they can look into. I do appreciate the help - this has at least helped push me in another direction with this to get this resolved.

Thanks!

Yes looks like an Permission issue..

https://support.microsoft.com/en-us/kb/827659