Installing ODBC on a TSE Server with MetaFrame

You have some incorrect permissions on a file. Some DLL files require RWX access (Read, Write, Execute access rights). You can use auditing in user manager or FileMon to help resolve this issue.

You installed the ODBC driver or the user Data Source Name (DSN) while in Execute mode instead of in Install mode.

The Microsoft article recommends that you check NTFS permissions, but they should be correct by default. NTFS permissions tell you the correct permission in case you have locked down your terminal server.

The Install mode issue is more likely the culprit. To check for this problem, search for the file odbc.ini, which contains ODBC settings. The file typically resides in the %SystemRoot% and in the administrative user's %HomeDrive%. The registry key HKEY_CURRENT_USERSOFTWAREodbc also contains ODBC settings. If you weren't in Install mode when you set up the ODBC connection, no .ini mapping occurred and the registry edits didn't copy to HKEY_LOCAL_MACHINESOFTWAREmicrosoftwindows ntcurrent versionterminal serverinstallsotware. If this is the case, you must uninstall the DSN configuration and driver and reinstall them in Install mode. Then run the compatibility script. The ODBC compatibility script calls the ODBC key, which changes the location pointer for the log file to each user's %rootdrive%. It then instructs you to run Change User /Install when you configure  a user DSN. If your software doesn't require a user DSN, you might be better off with a system DSN. The system DSN is automatically available for all users, so would avoid this issue. As a last resort, give the Everyone group full access to eliminate possible NTFS permissions problems.