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.
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.
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: