ERROR#0:
—————————
Microsoft SQL Server DSN Configuration
—————————
IMADirectory is not an existing data source name.
—————————
OK
—————————
—————————
Driver’s ConfigDSN, ConfigDriver, or ConfigTranslator failed
—————————
Errors Found:
Invalid DSN
—————————
OK
—————————
CAUSE:
This error usually indicates that respective registry path for ODBC is no longer available (must have been previously existed). The general case for this is an admin/application renamed it’s registry path.
TROUBLESHOOTING:
Ensure that respective (HKLM-for System DSN;HKCU-for User DSN) registry entry exists for the reported DSN.
System DSN: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBC.INI<ODBC Name>
User DSN: HKEY_CURRENT_USERSoftwareODBCODBC.INI<ODBC Name>
Also there should exist below entry which appears in the odbcad32.exe
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBC.INIODBC Data Sources<ODBC Name>
HKEY_CURRENT_USERSoftwareODBCODBC.INIODBC Data Sources<ODBC Name>
Example:
Incorrect:
C:>reg query HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBC.INI
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBC.INIIMADirectory_OLD
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBC.INIODBC Data Sources
C:>
Correct:
C:>reg query HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBC.INI
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBC.INIIMADirectory
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBC.INIODBC Data Sources
C:>
FIX: Update the respective registry entry to reflect the name of DSN.
