Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Need to remove ODBC Data Source - dBASE files - getting error.

Posted on 2010-01-08
26
Medium Priority
?
1,635 Views
Last Modified: 2013-11-24
I am installing a 3rd party application for a client that needs the Microsoft FoxPro VFP Driver installed. I installed this without issue.

Another requirement is that you can not have any User Data Sources (under the User DSN tab in ODBC Data Source Administrator) named dBASE Files.When I click on this and click remove, I get the following error:

The setup routines for Microsoft Access dBASE Driver ODBC driver could not be found. Please reinstall the driver.

When I click OK, it then says: Errors Found: Component not found in the registry

I looked in the registry editor and do not see the dBASE driver listed. I do not need this data source, but can not remove it entirely either. I've done a lot of research and can not find an answer specific to this.

Any help would be appreciated.

This is for a server running Windows Server 2008, 64 bit. The users run the required app through Terminal Services. Miscrosoft Acces is not installed, Microsoft Office Small Business is installed

Thanks,
Mike
0
Comment
Question by:mknol
  • 14
  • 12
26 Comments
 
LVL 43

Accepted Solution

by:
pcelba earned 2000 total points
ID: 26214870
First of all, application having such stupid requirements is not good application.
Second, VFP ODBC driver is 32 bit software and it cannot cooperate with 64 bit software.

But it is still possible to use 32 bit ODBC drivers under 64 OS to work with other 32 bit software. It is just installed in a separate folder -  c:\windows\syswow64\  and the ODBC administrator is  odbcad32.exe

So, did you use this 32 bit administrator? Probably yes.

DSN definition is just a Registry entry and you have to look for DSN name "dBASE Files" in registry. If you see "dBASE Files" DSN in ODBC administrator then you have to find it in registry. It should occur several times. If you delete all these "dBASE Files" occurences from registry then it should disappear from DSN list.

The dBase driver itself is MS Access driver in fact and it should remain installed after DSN deletion. If you decide to reinstall it then you may find it packed together with MS Office.

0
 

Author Comment

by:mknol
ID: 26215958
Thanks I will try this.

I agree, the application requirement is stupid, but we are forced to install it for a client - its an Insurance specific app - it also has lots of other stupid requirements that have made the installation painful and lengthy and very frustrating.

And I am using the 32 bit administrator as you suspected.

Do you have any suggestions on how to ensure I delete all the dBASE files in the registry, meaning what parts of the registry to look in?



0
 
LVL 43

Expert Comment

by:pcelba
ID: 26223433
I don't know 64 bit OS registry in all details but analogy with 32 bit says all DSN definitions are at one place and you'll see all User DSNs together like in ODBC administrator. If you delete all info related to "dBASE Files" DSN and leave everything other related to other DSNs then it should work. But remember this info is placed in several copies at different places in registry and you should delete all occurences.

You may also create new DSN and look what everything was added to registry. It could help to better understand the logic behind this process.

The Registry backup is highly recommended before you start to delete dBASE Files DSN from registry. You could also think about Access driver reinstallation as the first attempt to fix your problems.
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 

Author Comment

by:mknol
ID: 26224917
I think the safest bet would be to reinstall the Access driver, and then hopefully then be able to Remove it properly from the ODBC administrator.

Do you know where I can get the install files for this? I've looked, but haven't found anything for server 2008.

thanks.
0
 
LVL 43

Expert Comment

by:pcelba
ID: 26227023
This driver is a part of MS Access 2007 or Office 2007. Standalone driver installation is here: http://www.microsoft.com/downloads/details.aspx?familyid=7554F536-8C28-4598-9B72-EF94E038C891&displaylang=en
0
 
LVL 43

Expert Comment

by:pcelba
ID: 26227283
The latest driver version is 12.00.6423.1000. I am not sure if the above link points to it or to one step older version.
0
 

Author Comment

by:mknol
ID: 26232445
I downloaded and installed the driver. It installed successfully, but unfortunately I am getting the same error when trying to remove from the ODBC administrator.
0
 
LVL 43

Expert Comment

by:pcelba
ID: 26273364
So, it seems the registry hack is the only solution... You could ask Microsoft for a fix, of course.
0
 

Author Comment

by:mknol
ID: 26274038
Thanks for all the help so far. I've looked through the registry editor, found where these entries should be, and they are not there.

Is there any way, or repair tool, that would put these in the editor properly, so then maybe the Remove function would work?
0
 

Author Comment

by:mknol
ID: 26274080
My apologies, I did find them, not where i expected. They were under

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Borland

What's the safest way to back up the Registry before attempting to remove these?
0
 
LVL 43

Expert Comment

by:pcelba
ID: 26274088
If the registry entry is not there or on the right place then you could not see it in the ODBC manager. But as I understand it is visible. The problem must be somewhere else... Did you search registry as Admin?

Other idea is: If the dBase files driver is not on the right place in registry then the software which does not like it cannot see it also...

You could also try to access some DBF file via this (probably) invalid dBase driver and if it will work the problem is again somewhere else...
0
 

Author Comment

by:mknol
ID: 26274307
I installed FoxPro drivers, and they are listed here too, so I think I'm in the right place:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Borland\Database Engine\Settings\DRIVERS

I downloaded a small DBF file off the web, tried to open it, and it worked. I don't have Access, so I opened in Excel, so I don't know if it was actually trying to use via the dBase driver. As you can probably tell this DB stuff is a bit over my head.

Is it safe to assume that its just the dBASE listing under User DSN is just pointing to the wrong location? Is there a way to fix that if it is?
0
 

Author Comment

by:mknol
ID: 26274321
Just noticed as well that the User DSN, that the Microsoft Access Data base source (Microsoft Access Driver *.mdb, *.accdb) can not be modified or removed either.

We installed MS Office Small Business for the client, so Access was never installed (this was a brand new server).

Is there a trial version of Access we could install that maybe would fix these sources?
0
 

Author Comment

by:mknol
ID: 26274335
Sorry for so many follow ups here, but I may just have discovered another issue. I can not Modify any of the entries in the User DSN, all give the same error message as in my original question.

This includes Excel and FoxPro VFP Driver (*.dbf). The FoxPro driver is the one I had to install as part of the initial setup of the 3rd party app, so I know this is working.

It seems like the error is more with the ODBC Administrator? I did add FoxPro through ODBC Administrator after installing the drivers.
0
 
LVL 43

Expert Comment

by:pcelba
ID: 26274344
I am almost sure  Borland\Database Engine\Settings\DRIVERS  key cannot contain Microsoft Access dBase driver and/or DSN definition.

DBF file opening in Excel does not use ODBC driver. ODBC driver is used when you try to open DBF files as "External data" via ODBC in e.g. Microfoft Query.
0
 

Author Comment

by:mknol
ID: 26274365
Also found it here:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0\User Settings\Ace_OdbcCurrentUser\Create\SOFTWARE\ODBC\ODBC.INI
0
 
LVL 43

Expert Comment

by:pcelba
ID: 26274397
The problem could be just in access rights... Did you try everything as administrator?

And did you try the third party app without dBase DSN deletion?
0
 
LVL 43

Expert Comment

by:pcelba
ID: 26274413
Access trial version does not exist.
0
 

Author Comment

by:mknol
ID: 26274418
And here:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0\User Settings\Ace_OdbcCurrentUser\Create\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources

And here:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\Driver do Microsoft dBase (*.dbf)

And here:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\Microsoft dBase Driver (*.dbf)

Andr here:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\Microsoft dBase VFP Driver (*.dbf)

And all the installed drivers are listed here:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ODBC Drivers
0
 

Author Comment

by:mknol
ID: 26274437
I am logged in as administrator when looking at ODBC Administrator

The 3rd part app partly works, but them sometimes get an error, and when I use that error code and look at the 3rd party app website, it says its related to have dBASE in User DSN.
0
 
LVL 43

Expert Comment

by:pcelba
ID: 26274444
You should read again what you have to delete...

NOT the driver!!!   But DSN definition named "dBase Files" only.
0
 

Author Comment

by:mknol
ID: 26274483
Do you have any idea why ODBC administrator is not letting me Remove these? Is there another way to remove the DSN definition outside of the ODBC administrator.

Will removing it from the registry work?

If so, what is your recommendation for backing up the registry first?
0
 
LVL 43

Expert Comment

by:pcelba
ID: 26274586
0
 

Author Closing Comment

by:mknol
ID: 31674814
Greatly appreciate the effort and quick, thorough response. This was my first question on this site, I'm sold on the value presented here. Thanks!
0
 
LVL 43

Expert Comment

by:pcelba
ID: 26274953
Hope you have been successful with registry update and the application works correctly now.

I totally forgot one option - you could rename all "dBase Files" occurences in registry to something else which does not cause problems.
0
 

Author Comment

by:mknol
ID: 26274973
Thanks - I have it fixed - it is no longer showing up undeer User DSN

I have to wait until the client is back to work Monday to test it out and see if the error message goes away. I'm not familiar enough with the app to test it out myself.

Thanks for all your help.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Windows Explorer let you handle zip folders nearly as any other folder: Copy, move, change, and delete, etc. In VBA you can also handle normal files and folders, but zip folders takes a little more - and that you'll find here.
In a use case, a user needs to close an opened report by simply pressing the Escape (Esc) key. This can be done by adding macro code in Report_KeyPress or Report_KeyDown event.
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…

581 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question