Instead of trying to import directly from DBF, could you install the ACE OLEDB 12 drivers and try this

http://www.sqlservercentral.com/Forums/Topic1286522-2799-1.aspx

I'm getting this error on one of our SQL 2008 RTM servers right now.

I've had it 2 days in a row at exactly 1am in the morning.

Rebooting gets the worker...

This is a thank you to simonspring for finding this

"This additionally can cause issues:

http://stackoverflow.com/questions/8148774/error-quering-microsoft-ace-oledb-12-0-provider-from-sql-server

"

I remember running into an issue similar to this years ago with Advantage drivers.

Nevermind.

I just found that VS 2010 SP1 doesn't work properly with SQL 2012 CLR.

You have to install this overtop of your VS 2010 SP1 installation:

http://msdn.microsoft.com/en-us/data/hh297027

What's weird...

I actually loop, about every few seconds, requesting the agent job status. Once the status says it's complete, you are good to continue.

It might be easier to create an Agent Job that calls the powershell script.

Then from the Stored Procedure, call the job to run.

I've gotten this to work in our new SQL 2012 RTM 64-bit servers:

This retrives data from DBase, Advantage DB, Sybase .dbf files directly using the Microsoft ACE OLEDB 12.0 64-bit...