There are some updates about this problem.
I've installed iAnywhere version 10.1 (with EBF#4157) and now I still not receive the error about the misusing of the dll.
But there is another error message:
"Error: System.IndexOutOfRangeException: Index was outside the bounds of the array"
I've selected ".NET Framework Data Provider for SQL Anywhere 12" and used a simple connection string relaying to an ODBC data source name: "datasourcename=myDataSourceName".
My suspect is that ORM is still using Sybase v.10.x data provider even if is selected v.12.
So, I've used a "manual" connection string, that is:
Provider=SAPROV.12;Server=myServer;DBN=myDatabasename;UID=DBA;PWD=myPwd;InitString=SET TEMPORARY OPTION CONNECTION_AUTHENTICATION='Company=MyCompany;Application=Infinity;Signature=00000000000000000000000';
Note that, as we are Sybase OEM vendor, there is a new connection string style to apply. That is a temporary option in which must be indicated the company, the application and the relative signature.
After applying this connection string, I receive this error:
"Connection error, ExceptionSystem.ArgumentException, Details:Invalid connection string. Error parsing connection parameter string"
This enforces my suspect: ORM still using Sybase v.10.x data provider.
ORM specifics are clear: it supports Sybase iAnywhere v.12 (http://www.telerik.com/help/openaccess-orm/getting-started-root-dbsupport-sql-anywhere.html
), so I think I'm not the first who encounters this problem. Have you a workaround?
This is a very important project; we have to expose as WCF services very critical functionalities of our application for all over the Country.
Thank you very much.