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

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)" } }

[Nathan2020-0126]

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

[alexkeh]

@wortelus TNSNAMES is on by default unless you specifically enable alternative DB naming methods. You can turn on ODP.NET tracing to see what naming methods have been enabled, whether intended or unintended.

I suspect you likely have TNSNAMES enabled and ODP.NET has found a tnsnames.ora file somewhere, not necessarily in your current ODP.NET directory.