ADO connection issue in .net assembly

Hi all,

Could you help me see that why i use the ADO.net in the .net assembly, then it couldn't connect success. I set it as 'Sybase.Data.AseClient', but the error relates to '''Sybase.AdoNet2.AseClient". Do i need to add any additional dll?

DBMS:ADO.NET

DBParm:Namespace='Sybase.Data.AseClient',Database='****',DataSource=***',ADORelease='1.15.325.0',PROVIDERSTRING='Pooling=TRUE;Max Pool Size=1; Min Pool Size=1; Connection Lifetime=120;Connection Timeout=60;Incr Pool Size=1;Decr Pool Size=1'

Error Code:-1

Error Text:System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileLoadException: Could not load file or assembly 'Sybase.AdoNet2.AseClient, Version=2.155.1015.0, Culture=neutral, PublicKeyToken=95d94fac46c88e1e' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: Could not load file or assembly 'Sybase.AdoNet2.AseClient, Version=1.15.325.0, Culture=neutral, PublicKeyToken=95d94fac46c88e1e' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Comment

Load more comments

Topher Chen
Friday, 31 May 2019 02:54 AM UTC

I am her colleague, the project manager of the project she is working on, we wouldn't have decided to use 2017 if 2019 was ready in Dec last year, as you can imagine, how can our business wait that long without knowing a committed release date and without knowing if it would really work, the project was already started with 2017 in Jan this year, much development work has been done, I don't think we can at this point turn to 2019 unless there is a very quick way to convert everything without having to code too much, we have a project deadline to meet, that is the end of July this year, can you please help us resolve the DLL issue?

Helpful 0

Armeen Mazda @Appeon
Friday, 31 May 2019 03:12 AM UTC

If the deadline is in July it would not be realistic to convert all your PowerScript-based SOAP services to C# REST APIs with PB 2019. In that case, I would recommend to stay with PB 2017 R3 until you are able to migrate to C# REST APIs. As far as the issue you are having, please open a support ticket.

Topher Chen
Friday, 31 May 2019 03:27 AM UTC

ok, thanks Armeen

There are no comments made yet.

Resolved ADO connection issue in .net assembly