If unable to delete the key, double-click the key and erase the Data value entered. February 1, at 5: If you have any feedback, please tell us. Monday, October 5, Then we can know what registry nodes to find the certain DSN information.

Uploader: Akinot
Date Added: 18 May 2018
File Size: 34.58 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 3560
Price: Free* [*Free Regsitration Required]

Keep up the good work.

Registry Entries for ODBC Components – SQL Server | Microsoft Docs

Use one of the following methods to resolve softwaree problem: You are not able to view and configure some or all of the existing DSNs. January 4, at However, when moving their applications from their legacy bit x86 Windows systems, administrators are frequently confused – how should they set up the new ODBC database connections for their legacy application? Best Regards, Lingzhi Sun. Surely one of those classes will return micrpsoft list of installed drivers, right?

Skip to main content.

All hope seemed lost, but then one of the Scripting Guys decided to apply the Upstairs Closet theory to the problem. Help us improve MSDN.

System DSN Entries Do Not Appear in ODBC Data Source Administrator (odbcad32.exe)

Exporting the registry branches and looking at it with a text editor that shows non-printable characters will find machjne quickly. INI Has anyone found a better way to handle it other than grabbing from all three sources?


Go to the following path C: Sign in to vote. Yes, I’m a huge L.

When you’ve double clicked on ” Default ” you’ll get “Edit String” dialog box like below if the value is really ” value not set “; you should see nothing in “Value data” textbox:. Above screenshot is taken from a x64 bit system for a x64 bit driver We realized that the values for the following registry keys should always be value not set and if the value is set to an empty string or any other value either by Third party application or open this registry and close it without any changes we will run into gkey kind of issues where the drivers are not listed in ODBC Data Source Administrator odbcad32 On a x64 bit system for a x64 bit drivers: May 13, at 9: If you have any feedback, please tell us.

ODBC drivers not visible in the ODBC Data Source Administrator (odbcad32.exe)

There might be a convoluted way of getting at this information, but we Scripting Guys try to avoid convoluted ways whenever possible. December 18, at 7: Inside the loop, we assign the name of the first registry value to a variable named strValueName:.


Then, you can restore the registry if a problem occurs. This site uses cookies for analytics, personalized content and ads. As it turns out, the installed ODBC drivers are stored as individual registry values within this registry key, something like this:.

You can run the following command: July 29, at obcinst.ini Please feel free to let me know if you have any questions. But of course, you can enter this ” value not set ” string by manually and the value looks same with the “real” ” value not set “. This post includes information about a product that was not formally released. Navigate to the following location: Did this solve your problem?

Monday, October 5, 5: But differently the value ” value not set ” has been entered manually. This is one of those questions that end up driving us crazy. But it was like below in the problematic keys; the ” value not set ” string value has been added there manually like that: