mknol
asked on
Need to remove ODBC Data Source - dBASE files - getting error.
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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.
ASKER
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.
Do you know where I can get the install files for this? I've looked, but haven't found anything for server 2008.
thanks.
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
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.
ASKER
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.
So, it seems the registry hack is the only solution... You could ask Microsoft for a fix, of course.
ASKER
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?
Is there any way, or repair tool, that would put these in the editor properly, so then maybe the Remove function would work?
ASKER
My apologies, I did find them, not where i expected. They were under
HKEY_LOCAL_MACHINE\SOFTWAR
What's the safest way to back up the Registry before attempting to remove these?
HKEY_LOCAL_MACHINE\SOFTWAR
What's the safest way to back up the Registry before attempting to remove these?
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...
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...
ASKER
I installed FoxPro drivers, and they are listed here too, so I think I'm in the right place:
HKEY_LOCAL_MACHINE\SOFTWAR
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?
HKEY_LOCAL_MACHINE\SOFTWAR
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?
ASKER
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?
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?
ASKER
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.
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.
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.
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.
ASKER
Also found it here:
HKEY_LOCAL_MACHINE\SOFTWAR
HKEY_LOCAL_MACHINE\SOFTWAR
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?
And did you try the third party app without dBase DSN deletion?
Access trial version does not exist.
ASKER
And here:
HKEY_LOCAL_MACHINE\SOFTWAR
And here:
HKEY_LOCAL_MACHINE\SOFTWAR
And here:
HKEY_LOCAL_MACHINE\SOFTWAR
Andr here:
HKEY_LOCAL_MACHINE\SOFTWAR
And all the installed drivers are listed here:
HKEY_LOCAL_MACHINE\SOFTWAR
HKEY_LOCAL_MACHINE\SOFTWAR
And here:
HKEY_LOCAL_MACHINE\SOFTWAR
And here:
HKEY_LOCAL_MACHINE\SOFTWAR
Andr here:
HKEY_LOCAL_MACHINE\SOFTWAR
And all the installed drivers are listed here:
HKEY_LOCAL_MACHINE\SOFTWAR
ASKER
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.
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.
You should read again what you have to delete...
NOT the driver!!! But DSN definition named "dBase Files" only.
NOT the driver!!! But DSN definition named "dBase Files" only.
ASKER
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?
Will removing it from the registry work?
If so, what is your recommendation for backing up the registry first?
The registry backup/restore is described e.g. here: http://www.askvg.com/how-to-back-up-and-restore-registry-in-windows-xp-vista-and-server-2008/
ASKER
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!
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.
I totally forgot one option - you could rename all "dBase Files" occurences in registry to something else which does not cause problems.
ASKER
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.
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.
ASKER
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?