This content has been marked as final. Show 10 replies
Can you email a test case to the following email address: dotnet_us(at)oracle.com? The Oracle .NET dev team can investigate the cause of the problem.
I could provide you with a test case, but honestly it's as simple as it gets - just a blank web forms app that includes the managed provider! Here is the code I have to open the connection:
public class CatalogDB : IDisposable
private readonly OracleConnection _conn;
private OracleCommand _oCmd;
private OracleDataAdapter _oDA;
private DataTable _dt;
string connString = ConfigurationManager.ConnectionStrings["connCBSProd"].ConnectionString;
_conn = new OracleConnection(connString);
_conn.Open(); // EXCEPTION THROWN HERE
Could this be a medium trust issue? The server we're deploying to is also manged by plesk, so there is a virtual guarantee that there is some non-standard setting applied.
Are you using impersonation in your web app?
No, we're not using impersonation. If it helps though, locally my app pool in IIS is set to Identity = ApplicationPoolIdentity, while on our test/prod servers Identity = Custom Account (so a specific account for each app pool).
Are you able to verify if "Load User Profile" is set to true or false for the identities that are not working?
If needed, you can find the value by doing the following within IIS Manager:
- Select Application Pools from the tree under the server name
- Under the listed Application Pools right-click the pool of interest and select Advanced Settings... from the context menu
- Scroll down to the Process Model section and verify the value for "Load User Profile"
I believe you can encounter this situation if "Load User Profile" is set to "false".
As ever, any additions, corrections, clarifications, etc. are welcome.
That was the trick! Thanks.
We believe we have developed a fix such that you wouldn't need to change your "Load User Profile" for managed ODP.NET to work. Can you send an email to dotnet_us(at)oracle.com? I will email you back with a test drop of the software. You would then be able to verify whether managed ODP.NET would work with your original configuration.
We believe this issue will be fixed in the next ODP.NET, Managed Driver beta release (Beta 2) such that you won't need to modify your "Load User Profile". If anyone does hit this problem with the upcoming Beta 2, please post to this forum thread and/or email the dotnet_us email alias.
Beta 2 is now available with the Load User Profile fix.
I have encountered this problem，this is Effective，thanks