1. Sally D
  2. PowerBuilder
  3. Thursday, 30 May 2019 10:59 AM UTC

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)

 

Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 4 June 2019 08:49 AM UTC
  2. PowerBuilder
  3. # 1

Hi Sally,

Based on our analysis, this is caused by that the Sybase.AdoNet2.AseClient.dll is missing from your PB assembly dll of the .NET project. 

You may contact SAP and ask for the Sybase.AdoNet2.AseClient.dll or you may download and install ASE ADO.NET Data Provider to include the DLL into your .NET project.

Please refer to the blow links for more:

https://www.connectionstrings.com/ase-ado-net-data-provider/info-and-download/

https://wiki.scn.sap.com/wiki/display/SYBCON/All+you+need+to+know+about+the+ADO.net+provider

 

You may also refer to the below link for using ADO.NET in PowerBuilder:

https://www.appeon.com/support/documents/appeon_online_help/pb2017r3/connecting_to_your_database/ch05s02.html

Regards,

Mark Lee

 

Comment
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 30 May 2019 15:20 PM UTC
  2. PowerBuilder
  3. # 2

Hi Sally, I don't recommend you use this feature.  It is obsolete feature now that is not even eligible for tech support.  The new feature replacing this is the C# Web API and .NET DataStore of PB 2019 (included in Cloud Edition or higher).

Comment
  1. Topher Chen
  2. 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?
  1. Helpful
  1. Armeen Mazda @Appeon
  2. 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.
  1. Helpful
  1. Topher Chen
  2. Friday, 31 May 2019 03:27 AM UTC
ok, thanks Armeen
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.