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

Unable to see system DSNs in ODBC Data Source administrator

windows XP PRo SP2 -  ODBC Data Source Administrator

I have set up several DSNs for us with variousMS Access Databases and I have very recently noticed that they are no being displayed in the System DSNs in ODBC Data Source Administrator.  The DSNs are used to connect ASP web pages to MS Access Databases and the connections still function perfectly.

I have looked in the ODBC.ini file and can see the DSNs in there.  I have also set up a Test DSN which shows in the ODBC Data Source Administrator and the ODBC.ini file.

I have checked the code in the ODBC.ini file and cannot see any obvious difference between the Test DSN and the DSNs that are not showing in ODBC Data Source Administrator.

I have tried the various solutions I have found on this site that claim to fix 'missing' DSNs but none work

Please can anyone offer a solution to this problem?

Below is the content of the odbc.ini file:

[ODBC 32 bit Data Sources]
prices=Microsoft Access Driver (*.mdb) (32 bit)
iimia_employees=Microsoft Access Driver (*.mdb) (32 bit)
Trackit=SQL Server (32 bit)
Tutorial=Microsoft Access Driver (*.mdb) (32 bit)
people=Microsoft Access Driver (*.mdb) (32 bit)
Visual FoxPro Database=Microsoft Visual FoxPro Driver (32 bit)
Visual FoxPro Tables=Microsoft Visual FoxPro Driver (32 bit)
iisweb=Microsoft Access Driver (*.mdb) (32 bit)
aspticker=Microsoft Access Driver (*.mdb) (32 bit)
MS Access Database=Microsoft Access Driver (*.mdb) (32 bit)
Excel Files=Microsoft Excel Driver (*.xls) (32 bit)
dBASE Files=Microsoft dBase Driver (*.dbf) (32 bit)
catch22=Microsoft Access Driver (*.mdb) (32 bit)
test=Microsoft Access Driver (*.mdb) (32 bit)
[ODBC Data Sources]
CTPNEW=Watcom SQL 4.0
CTPEDI=Watcom SQL 4.0
PNOTES10=Watcom SQL 4.0
[CTPNEW]
Description=CTP Watcom Database (Local)
Driver=C:\CTP\WOD40W.DLL
Start=DBENG40W -d
AutoStop=Yes
Database=C:\CTP\CTP2DD40.DB
DatabaseFile=C:\CTP\CTP2DD40.DB
DatabaseName=CTP2DD40
[PNOTES10]
Description=CTP Watcom Database (Local)
Driver=C:\CTP\WOD40W.DLL
Start=DBENG40W -d
AutoStop=Yes
Database=C:\CTP\PNOTDD11.DB
DatabaseFile=C:\CTP\PNOTDD11.DB
DatabaseName=PNOTDD11
[CTPEDI]
Description=CTP EDI Version 2 Database (Local)
Driver=C:\CTP\WOD40W.DLL
Start=DBENG40W -d
AutoStop=Yes
Database=C:\CTP\CTPEDI20.DB
DatabaseFile=C:\CTP\CTPEDI20.DB
DatabaseName=CTPEDI20
[prices]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
[iimia_employees]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
[Trackit]
Driver32=C:\WINDOWS\system32\SQLSRV32.dll
[Tutorial]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
[people]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
[Visual FoxPro Database]
Driver32=C:\WINDOWS\system32\vfpodbc.dll
[Visual FoxPro Tables]
Driver32=C:\WINDOWS\system32\vfpodbc.dll
[iisweb]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
[aspticker]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
[MS Access Database]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
[Excel Files]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
[dBASE Files]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
[catch22]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
[test]
Driver32=C:\WINDOWS\system32\odbcjt32.dll
0
iimiaIT
Asked:
iimiaIT
3 Solutions
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:

  The ODBC.ini file is just there for compatability for older programs.  The real entries are in the registry.  Fire up regedit and do a search on that Test DSN you created.  Then look for one of the others and compare.

JimD
0
 
deathtospamCommented:
IimiaIT --

Open up the registry by typing "regedit" in the "Start > Run" window, and then navigate to the following area in the left pane of the registry window:

=========================================================
HKEY_LOCAL_MACHINE > SOFTWARE > ODBC > ODBC.INI
=========================================================

If you expand that folder, you'll see all of the System DSNs' info in that folder.  And in the "ODBC Data Sources" folder beneath it, you'll see all of the entries that appear in the System DSN tabbed interface.


-= DeathToSpam =-
0
 
iimiaITAuthor Commented:
Thanks JDettman and deathtospam, unfortunately, I have tried both and have found all the system DSNs in the registry and the only thing that seems to be different in any of them is the path to the database they connect to.  And I would expect that.

They are just not appearing under the System DSN tab in ODBC Data Source Administration
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<They are just not appearing under the System DSN tab in ODBC Data Source Administration>>

  The ODBC registry is probably corrupt in some way.  Try eporting that kep out, then check the .REG file for any strange characters.  Edit them out (make SURE you keep a copy of the original export file in case you need to import it) and then import the edited file.  See if the entires show up then.

  Also, before doing that, if you create a brand new entry now in the system DSN tab, does it show up?  If yes, then you'll see what a clean DSN entry should look like in the .REG file when you export the ODBC key.

JimD
0
 
iimiaITAuthor Commented:
Thank JDettman,

Here is the code from TEST.reg (export)  This on is visible in ODBC Data Source admin.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\test]
"Driver"="C:\\WINDOWS\\system32\\odbcjt32.dll"
"DBQ"="C:\\Inetpub\\webdb\\iis.mdb"
"DriverId"=dword:00000019
"FIL"="MS Access;"
"SafeTransactions"=dword:00000000
"UID"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\test\Engines]

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\test\Engines\Jet]
"ImplicitCommitSync"=""
"MaxBufferSize"=dword:00000800
"PageTimeout"=dword:00000005
"Threads"=dword:00000003
"UserCommitSync"="Yes"

and here is the code from the prices.reg (export) and this is not visible in the ODBC data source Admin.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\prices]
"Driver"="C:\\WINDOWS\\system32\\odbcjt32.dll"
"DBQ"="C:\\Inetpub\\wwwroot\\IIG Website\\prices-db\\iimia-prices.mdb"
"DriverId"=dword:00000019
"FIL"="MS Access;"
"SafeTransactions"=dword:00000000
"UID"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\prices\Engines]

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\prices\Engines\Jet]
"ImplicitCommitSync"=""
"MaxBufferSize"=dword:00000800
"PageTimeout"=dword:00000005
"Threads"=dword:00000003
"UserCommitSync"="Yes"

I have looked 3 times and can't see anything different between the 2 other than the path to the database.

could there be something corrupt with the ODBC Data Source Administration app?
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
Make sure there are no extra character on the end of anything.  Then try and import the .reg file.  See if that cleans it up.

JimD
0
 
iimiaITAuthor Commented:
Thanks again for that.
Checked for extra characters. None.
imported back into the registry - still not appearing.
0
 
nvr8981Commented:
I had the same issue and found the following to be a solution to my problem.

Depending on whether you have the settings in HKLM or HKC, delete the (Default) key under

SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources

Once I deleted it, Windows had the (Default) value showing (value not set) under the Data column.  I apparently had a white space or another value which caused all of the issues.  
0

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

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