Original Post
hi,
In my application, if I do not impersonate a certain user, and run process as is, all works and my assemblies get loaded.
But when I log and impersonate the certain user, I get "could not load assembly or one of its dependencies, access denied".
I am realizing that some of dependencies may not by accessible to the user policy. Before I started investigating which and where, I added the user to Administrators group and removed the user from previous group. I still get the access denied if my proccess impersonates to that user. I am so lost, the user is administrator after all. Do you have any suggestions? If I do not impersonate to the user all works.
In my application, if I do not impersonate a certain user, and run process as is, all works and my assemblies get loaded.
But when I log and impersonate the certain user, I get "could not load assembly or one of its dependencies, access denied".
I am realizing that some of dependencies may not by accessible to the user policy. Before I started investigating which and where, I added the user to Administrators group and removed the user from previous group. I still get the access denied if my proccess impersonates to that user. I am so lost, the user is administrator after all. Do you have any suggestions? If I do not impersonate to the user all works.