![]() So I guess that would be what is preventing the end user from accessing the settings vs. Whilst my administrative account's looked like this: Then in the resulting `Advanced Security Settings for ODBC.INI` dialog, I clicked the `Effective Access` tab and was able to select the machine's user account using the `Select a user` link, and afterwards I clicked the `View effective access` button (you have to click that again to refresh it if you change the user) and the permissions for the end user looked like the following: This error also occurs if attempting to install a. I found deep deep in the GUI settings.I found where I can test the effective permissions for the user, by following most of the previous link and then clicking the `Advanced` button to the right of the `For special permissions or advanced settings, click Advanced.` label at the bottom of the `Permissions for ODBC.INI` (refers to the key) dialog. Cause: An attempt was made to change the current username or password without the appropriate privilege. Then grand FC to 'System', and, if you like, to 'Administrators' also. Regedit, select you key, right-click->Permissions->Advanced->Owner, select Administrators, Apply. You have to set you as owner of the key first and give you full writing permissions. ![]() A bit of time has passed though, and I believe the System Admin on site has fixed the issue, at least for my admin account based on what I found in the ACLs for the ODBC.INI key. Some keys are protected by trusted installer. Okay so after going through the hassle trying to elevate the my regedit's permissions I am now able to edit the ODBC.INI on the other machine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |