Error Setting Registry Key for HKEY Local Machine Software ODBC when Attempting to Install ODBC Configuration for Users
- 28 Mar 2023
- Contributors
- Print
- DarkLight
- PDF
Error Setting Registry Key for HKEY Local Machine Software ODBC when Attempting to Install ODBC Configuration for Users
- Updated on 28 Mar 2023
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
When attempting to install the ODBC driver for a user on a workstation, the following error occurs "Error setting registry for HKEY_LOCAL_MACHINE Software\ODBC\ODBCINST.ini ODBC Drivers Progress OpenEdge 10.2b driver. Try re-running this process from Right-click on FIMS | Run As Administrator"
Answer:
Cause 1: The Windows login of the user running the program does not have sufficient rights to write to the Windows registry or at least to the LOCAL-MACHINE hive in the registry.
Cause 2: If it is a Windows 7 Client; Windows 7 introduced new security features that can prevent an application (like FIMS) from making certain changes to your computer (like writing to the registry). Even if the user’s Windows login has privileges, the FIMS application might be restricted.
https://knowledgebase.progress.com/articles/Article/P141118
Cause 2: If it is a Windows 7 Client; Windows 7 introduced new security features that can prevent an application (like FIMS) from making certain changes to your computer (like writing to the registry). Even if the user’s Windows login has privileges, the FIMS application might be restricted.
Solution 1: Have an administrator run the ODBC setup program or give the user permissions.
Solution 2:
Option 1:
1. Right-click on the FIMS icon and select Properties > Advanced, and check the 'Run as Admin' box.
2. Open FIMS and set up the ODBC Data Sources (gui\system\d-odbc92.w).
3. When you're finished, go back into the shortcut properties and un-check the box.
Option 2: Turn off or choose a lower setting on the User Account Control (UAC). Here is a link to a Microsoft Knowledgebase article about UAC.
http://support.microsoft.com/kb/975787
Cause 3: This can also occur if the workstation in question is a 64bit machine. The installation attempted to create registry keys in HKLM\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers (which is the 32bit location) but should have created keys in HKLM\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ODBC Drivers for 64bit machines. See the following which was an issue with the 10.2 A driver, which should not occur with the 10.2B driver, but it appears that sometimes it may still be an issue:Solution 2:
Option 1:
1. Right-click on the FIMS icon and select Properties > Advanced, and check the 'Run as Admin' box.
2. Open FIMS and set up the ODBC Data Sources (gui\system\d-odbc92.w).
3. When you're finished, go back into the shortcut properties and un-check the box.
Option 2: Turn off or choose a lower setting on the User Account Control (UAC). Here is a link to a Microsoft Knowledgebase article about UAC.
http://support.microsoft.com/kb/975787
https://knowledgebase.progress.com/articles/Article/P141118
Was this article helpful?
