Home/ Questions/Q 6382527
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T02:32:01+00:00

here’s another strange behaviour I’m currently facing. I have an application deployed on a

  • 0

here’s another strange behaviour I’m currently facing. I have an application deployed on a network-drive with full-trust. This application checks for existing ODBC-Connections.

On my machine everything is fine and works as expected.

On the machine of a colleague it is not working and states the message, that he isn’t able to access the key. In “regedit” he is able to access and change it. He’s like me a local admin.

The Key the application is accessing is:

var odbcKey = Registry.LocalMachine.CreateSubKey("SOFTWARE\\ODBC\\ODBC.INI");

Starting the same application with the *.exe everything is fine.

Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You have to edit the permission of this registry key by going to the registry key then right click on it, then permissions .. then give the user permission to read from it. ( assuming u are using windows 7 ).

    I have faced the same problem, and it is fixed by giving the “write” permission for the correct user on this key, as you are trying to create a sub key in the registry which need permission.

    • 0