1. Shilpa Rani Bansal
  2. PowerBuilder
  3. Thursday, 15 April 2021 17:53 PM UTC

PBCRYPT.dll provided in Runtime package of 2019 R3 is not working. And this DLL is taking precedence over our existing dll. Please let us know the resolution for this.

This is our existing declaration and call to a function of this DLL

FUNCTION long Sec_3DesCryptApi(string input, long len, ref string output) LIBRARY "pbCrypt.DLL" alias for "Sec_3DesCryptApi;Ansi";

This.Sec_3DesCryptApi(as_password, ll_len, ref ls_password_output)

PFA DecyptionError.PNG

Attachments (1)
Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Saturday, 17 April 2021 01:20 AM UTC
  2. PowerBuilder
  3. # 1

Hi Shilpa,

Is the PBCRYPT.dll your application called provided from an external company?
We found that PBCRYPT.dll doesn't exist in PB 2017 R2, and in PB 2019 R3, you can't call this function in this DLL.
So if this PBCRYPT.dll is from another company, it is suggested you rename this DLL to avoid the name conflict with the one in the PB 2019 R3 Runtime.


There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 15 April 2021 18:10 PM UTC
  2. PowerBuilder
  3. # 2

Hi Shilpa;

  I am not sure why your App is calling a function *directly* in this PB runtime DLL vs using the CryptorObject class's methods? Otherwise, your Apps would be at the mercy of internal runtime changes.

  For 3DES, you can use the SymetricEncrypt and the SymetricDecrypt commands with the 3DES! argument setting.

Regards ... Chris

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.