Invalid request on pooled connection

[Former Member]

I recently deployed an application using SQL Anywhere v 12.0.1.3942 with the .Net Dataprovider and using Entity Framework 5.

Since deployment a few days ago I've noticed that I'm intermittently getting the following error - iAnywhere.Data.SQLAnywhere.SAException: Run time SQL error -- *** ERROR *** Assertion failed: 104909 (12.0.1.3942)[] Invalid request on pooled connection

Here is the complete stack trace - http://pastebin.com/rsbChVXN

So far I haven't been able to find any details on what the potential cause of this may be as I am wrapping my context's in using blocks.

Like I said earlier, its only happened a total of 3 times, but I'd prefer to get to the bottom of this before things potentially get out of hand. Thanks in advance.

[jeff_albion · Accepted solution]

This is a known issue. This can potentially happen if you have a newer version of the database server than the ADO.NET provider.

Specifically, CR #742355 is implemented on the database server (the server is a higher build than 12.0.1.3924 or 16.0.0.1588), but CR #741707 is not implemented on the ADO.NET provider (the ADO.NET provider is a lower version than 12.0.1.3924 or 16.0.0.1588).

Deploying the same version of the ADO.NET provider to match the database server version (e.g. 12.0.1.3942) to the client should resolve this issue.

[Former Member · Accepted solution]

Thanks for the info! We updated the data provider within the application and so far we haven't seen anymore connection pooling errors.

[former_SQLA_member1694979 · Accepted solution]

I had the same exception with EF6, Server 12.0.1.4165, Ado.NET Provider 12.0.1.41654 ?, but in my case it was caused by different threads accessing the same db context which of course is not supported. The scenario can easily be reproduced by starting several threads accessing the same context.

[Former Member]

Same error with driver version 16.0.0.20764 and db version 16.0.0.2038. Any suggestion?

[Breck_Carter]

> Any suggestion?

Yes. Please make the effort to start a new question, with all the supporting information (error message, etcetera). It is unlikely to be the "Same error" because the other error has a solution.