Link to home
Start Free TrialLog in
Avatar of CalBob
CalBob

asked on

MS OLEDB Provider for Visual FoxPro missing from Connection Manager SSIS

This week I noticed that my SSIS jobs fail that are using Visual FoxPro tables as a data source.  I am using SQL 2005 Enterprise Edition on a Windows Server 2003 box.

After looking around I noticed that "The Microsoft OLEDB Provider for Visual FoxPro" is missing from Connection Manager in SSIS (under the Native OLE DB providers).

Several months ago I created these SSIS jobs to import the Visual FoxPro (free) tables.  I only run the jobs once a month.  I'm not 100% sure but I assume I must have used the MS OLEDB provider for Visual FoxPro when I created the jobs.  And the jobs have worked well for months. However, last weekend we moved the server to a new domain.  (All the data, source and destination, is on the server so I wouldn't think that moving it would have anything to do with it but I thought I should mention is since it is the only change I can think of that has been made.)

Now when I try to open and edit the connection to determine the problem I get an error stating "The specified provider is not supported.  Please choose different provider in connection manager."  Related errors state the SourceConnectionOLEDB failed, etc.  Of course, as I mentioned there is no Visual FoxPro driver in Connection Manager.  But I'm guessing there must have been at some point.  

Assuming the MS OLEDB Provider for Visual FoxPro was once a choice, since I don't know what else I would have used, what would cause it to disappear?  And more importantly how do I get it/one back?  I'm hoping if I could do that my jobs would start working again.

Thank you so much for any help.

ASKER CERTIFIED SOLUTION
Avatar of Olaf Doschke
Olaf Doschke
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of CalBob
CalBob

ASKER

Olaf Doschke:

I will be reinstalling the VFP OLEDB provider, but in the meantime to answer your question regarding the System account the SSIS runs on...I did change that because of the domain change.  However, I simply made a new domain account on the new DC.  I added the account to the admin group on the db/SSIS server and that didn't seem to make a diffenence.  By the way, no other jobs were affected by the domain change as far as drives are concerned.  Should changing the account make a difference in this case?
Avatar of CalBob

ASKER

Thanks!  Even though the VFPOLEDB provider was still on the server, apparently it wasn't working correctly in the new domain.  I guess since I installed it under a diffrent account it didn't continue to work until I reinstalled it in the new domain.

Thanks again.
You are welcome. And, yes, it could be the security issue.
Yes, chaging the SSIS account of course changes the account the OLEDB provider is used. And as DBF data acess mainly is file access it also changes what files SSIS and the OLDB provider can access. It even may be a misleading error, that the OLEDB provider is missing, it may simply be, that the new account does not have access to DBF files, especially if those DBF files are still in another domain.

Bye, Olaf.