Hello
I'm using impersonation for my asp.net application in the following way (web.config):
<identity impersonate="true" userName="registry:HKLM\Software\WebApplications\C1.SPT\ASPNET_SETREG,userName" password="registry:HKLM\Software\WebApplications\C1.SPT\ASPNET_SETREG,password"/>
The service account used has normal user rights on the server.
When starting the application, I get an "access denied" error on Connection.Open.
If I set impersonate="false" OR add the service account to the local administrators group on the server, the application works fine (but both is NOT possible inside our company!)
The error probably occurs in the managed odp.net driver in the line accessing .MainModule in class TTCAuthenticate
this.m_programName = base.m_marshallingEngine.m_dbCharSetConv.ConvertStringToBytes(ProviderConfig.CurrentProcess.MainModule.ModuleName, 0, ProviderConfig.CurrentProcess.MainModule.ModuleName.Length, true);
It seems that ProviderConfig.CurrentProcess shows the current process correctly.
Is there still a Bug in managed odp.net beta 2? (Version 4.11.2.3.60)