Network Error: 200

[SqlTechMike]

I am getting a "Network Error: 200" exception when debugging my application. The application uses Entity Framework and was originally set to use SQL Server as the data source. I have made the needed changes to the Entity Data Model to use the DevArt provider for Oracle, but when I run the application I get the following exception. Is there any way to dig deeper into the exception, such as verbose logging or tracing, to determine it's cause?

Message: "Network error: 200"
Stack Trace: " at Devart.Data.Oracle.DirectUtils.b(Int32 A_0)\r\n at Devart.Data.Oracle.c3.m()\r\n at Devart.Data.Oracle.c3.k()\r\n at Devart.Data.Oracle.OracleInternalConnection.Rollback()\r\n at Devart.Common.k.a(Enlistment A_0)\r\n at System.Transactions.VolatileEnlistmentAborting.EnterState(InternalEnlistment enlistment)\r\n at System.Transactions.VolatileEnlistmentActive.InternalAborted(InternalEnlistment enlistment)\r\n at System.Transactions.TransactionStateAborted.EnterState(InternalTransaction tx)\r\n at System.Transactions.TransactionStateActive.Rollback(InternalTransaction tx, Exception e)\r\n at System.Transactions.Transaction.Rollback()\r\n at System.Transactions.TransactionScope.InternalDispose()\r\n at System.Transactions.TransactionScope.Dispose()\r\n at RJ.ODS.Common.Repository`3.ExecuteQuery(ObjectQuery query, TIncl[] includes, Int32& totalCount, TRtnEtyType returnEntityType, Int32 skip, Int32 take) in C:\\Dev\\ODS\\DEV\\code\\Services\\RJ.ODS.Common\\Repository.cs:line 248"

[Shalex]

"Network error: 200" is an internal error of our provider which says "connection is not established". Possible reasons:
a) code which tries to use previously closed connection
b) server terminates the connection (server's problem)
c) bug of the provider

We need to reproduce the problem in our environment to find out the true reason. If possible, try to localize the issue and send us a small test project with the corresponding DDL/DML script.

General recommendations:
1) try using the "Validate Connection=true;" connection string parameter to validate connections that are being got from the pool;
2) upgrade to the latest (7.4.146) version of dotConnect for Oracle;
3) try using the OCI mode (via Oracle client).