• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1720
  • Last Modified:

Corrupted ODBC

We have a machine with an ODBC entry showing in the list of existing System Data Source.  However, no one can connect using it.  We cannot delete it or modify it; when we attempt to do so, we get an error telling us that it "is not an existing data source."

Huh?  If it shows on the list, it's got to exist, right?  Obviously, something has gotten corrupted and I don't want to charge in there like Atilla the Hun.  Has anyone ever encountered this before and if so, what did you do to fix it?

3 Solutions
Eugene ZCommented:
well its very irrelevent subject to MS SQL :) but anyway

check you got all the core components in the list

then try to log in as an admin on that machine and see if you can get it deleted or created as an admin.
ClothahumpAuthor Commented:
Eugene - virus clean, most current MDAC was already installed.

FD - everything is there.  All of the other ODBC entries work correctly, it's just this one entry that's gonzoed.
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

See if this article helps: http://support.microsoft.com/default.aspx?scid=kb;en-us;95012
Check out the file comparisons at the bottom.

I would still re-install Mdac.  I seem to remember having the same problem, but I just can't put my finger on it. I think another program came in and updated one of those files and the mdac re-install did not correct the problem. I had to manually replace the file.... I think.
Eugene ZCommented:
use tjhis link below  as idea to create and delete hive with your "bad" DSN



WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Find the hive that corresponds to your data source name. There you will find the keyword pairs. Warning, manually editing registry values can cause system instability and perhaps an unrecoverable failure.
Eugene ZCommented:
BTW: use regedt32 to check security of your ODBC DSN - maybe it is problem
ClothahumpAuthor Commented:
Eugene - aha!  I went in with regedit.  The registry itself is apparently corrupted.  I can't edit or delete the entry with regedit.

If I were a detective, I would be thinking "This is a clue!"  :-)
Eugene ZCommented:
check Security -> permissions - by using regedt32
Eugene ZCommented:
one more:
 try login as administrator ( account) and delete DSN ...
Then login as usually - and create new DSN...
ClothahumpAuthor Commented:
We wound up reformatting, reinstalling and reloading everything.

I appreciate the effort everyone made.  Even though I didn't really get an answer, I'm going to split points with everyone that tried to help as a way of saying thanks for your efforts.
I used regedt32 in a DOS window and deleted the corrupt entries in my System DSN ODBC by going to HKEY_LOCAL_SOFTWARE\SOFTWARE\ODBC\ODBC.INI. I deleted all folders corresponding to corrupt entries. And in ODBC Data Sources under the ODBC.INI - also deleted entries corresponding to corrupt entries. That fixed it.

My entries got corrupted when I deleted older versions of Oracle from my PC. I had 9i, 10g and 11g installed. When I removed 9i and 10g all System DSN ODBC entries using those two versions became corrupted and couldn't be used or deleted.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now