Oracle.ManagedDataAccess.Client.OracleException (0x80004005): Connection request timed out

[Nathan2020-0126]

I can success get data from oracle when running in visual studio. but after I deployed to IIS, I always get error information like below.
I have tryed version with 2.19.101 and 2.19.80, but none of them worked.
{ "Error":{ "Code":"Exception", "Message":"Connection request timed out", "Details":"Oracle.ManagedDataAccess.Client.OracleException (0x80004005): Connection request timed out at OracleInternal.ConnectionPool.PoolManager3.Get(ConnectionString csWithDiffOrNewPwd, Boolean bGetForApp, OracleConnection connRefForCriteria, String affinityInstanceName, Boolean bForceMatch)
at OracleInternal.ConnectionPool.OraclePoolManager.Get(ConnectionString csWithNewPassword, Boolean bGetForApp, OracleConnection connRefForCriteria, String affinityInstanceName, Boolean bForceMatch)
at OracleInternal.ConnectionPool.OracleConnectionDispenser3.Get(ConnectionString cs, PM conPM, ConnectionString pmCS, SecureString securedPassword, SecureString securedProxyPassword, OracleConnection connRefForCriteria) at Oracle.ManagedDataAccess.Client.OracleConnection.Open() at Serenity.Data.WrappedConnection.Open() at Serenity.Data.SqlConnections.EnsureOpen(IDbConnection connection) at Serenity.Data.SqlHelper.ExecuteScalar(IDbConnection connection, String commandText, IDictionary2 param)
at Serenity.Data.EntitySqlHelper.ForEach(SqlQuery query, IDbConnection connection, Action callBack)
at Serenity.Services.ListRequestHandler3.Process(IDbConnection connection, TListRequest request) at lambda_method(Closure , Object , Object[] ) at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target, Object[] parameters) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync() --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync() --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextExceptionFilterAsync>g__Awaited|25_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)" } }

[alexkeh]

Can you increase the connection string Connection Timeout value to some high, such as 600 (i.e. ten minutes)? The default value is 15 seconds, which means it could be hit before the actual error you are hitting can trigger if it has a longer timeout value.

When you run the app again, the real problem's error should manifest itself and we should see it in the exception message.

I assume you are connecting to the same DB from IIS and VS.

[Nathan2020-0126]

I increased the timout value, still, it work in visual studio, but I got new error as below.
System.TypeLoadException:“Could not load type 'System.Security.Principal.WindowsImpersonationContext' from assembly 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.”

[alexkeh]

Two things to check:

1. Add the NuGet package System.Security,Principal to the IIS deployment if it's not there.
2. Make sure your deployed app uses ODP.NET Core or managed ODP.NET as intended. They share the same namespace and APIs, but they are two different assemblies. ODP.NET Core is for .NET Core/5 and managed ODP.NET is for .NET FW primarily. It looks like you are using .NET Core.

[Nathan2020-0126]

@alexkeh, thanks for your feedback, I checked two points.

1. System.Security.Principal.Windows.dll is there
   
2. Installed ODP.NetCore(version 2.0.12),before I was using Oracle.ManagedDataAccess.Core(version 3.21.1), but I got same error information
   

Error:

[alexkeh]

@Nathan2020-0126 I don't see the System.Security.Principal assembly. It's not the same assembly as System.Security.Principal.Windows. Can you try adding System.Security.Principal from NuGet Gallery?

[Nathan2020-0126]

I just installed the System.Security.Principal, still not work.

[alexkeh]

Looks like the WindowsImpersonationContext class is only available in .NET FW. And you are using .NET Core.

Were there any configuration changes made between your VS configuration setup and IIS configuration setup, such as in how they use Active Directory usage? My guess is that Windows impersonation has been enabled in IIS.

[Nathan2020-0126]

I didnot change any configuration. and the windows impersonation is disabled

[Nathan2020-0126]

I searched in githhub and find this page.
dotnet/runtime#35389
WindowsImpersonationContext is not in .NET Core. It was an intentional decision since it has number of security problems. The discussion about this is at #20647 (comment)

[alexkeh]

Which .NET Core version are you using?

The ODP.NetCore package is not distributed by Oracle. It may include an assembly that Oracle distributed in the past, but we can't vouch for its authenticity because it was packaged by a third-party. Can you go back to use ODP.NET Core 3.21.1 package, which will work with .NET Core 3.1 and 5. If you need .NET Core 2.1 support, use the ODP.NET Core 2.19.110 version.

[Nathan2020-0126]

@alexkeh after I go back to use Oracle.ManagedDataAccess.Core version 3.21.1, the problem is solved. thanks very much

[alexkeh]

That's great!

[salahrzzaz]

#243

i have same issue if anyone can help

[AstorSkywalker]

Going back to Oracle.ManagedDataAccess.Core version 3.21.1 was the answer