Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved bad runtime reference to ImportJson

  1. Issue
0
Votes
Undo
  1. Alexander Skorokhodov
    Alexander Skorokhodov
  2. PowerBuilder
  3. Wednesday, 27 May 2020 06:12 AM UTC

Dear Appeon:

when i run a released system, i get a bad runtime reference on 

  l_RowCount = dw_1.ImportJson(l_License_Json)

this error does not pop up when i run the system from the development environment.

most likely, i am missing a required  DLLs in the release  environment.

i copied over the full content of

C:\Program Files\Appeon\PowerBuilder 17.0\SharedExtensions

directory, still getting the error.

 please help.

thank you in advance.

sasha

How to migrate a PB desktop application to PB Web/...
Concurrency issues with SQL server different with ...
Responses (4)
Alexander Skorokhodov
Alexander Skorokhodov Accepted Answer Pending Moderation
  1. Friday, 29 May 2020 00:45 AM UTC
  2. PowerBuilder
  3. # 1

oh, sorry, my typo, shall be PBL 2017R3 build 1915, not 1951

from release

PWRBLDR-2017R3LTS-MR07-1915-EN.zip

 

sasha  

 

 

Comment
There are no comments made yet.
Alexander Skorokhodov
Alexander Skorokhodov Accepted Answer Pending Moderation
  1. Thursday, 28 May 2020 20:43 PM UTC
  2. PowerBuilder
  3. # 2

Chris:

Having the ability to  dw_1.ImportJson(l_License_Json) is a nice feature, but not a necessity. 

I can write a simple function to parse l_License_Json bypassing the ImportJson,

so i m not dead in the water here.

for completeness, i filed a general bug report on the matter.

 pls close this question, and thank you for help.

sasha

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 28 May 2020 22:47 PM UTC
Hi Sasha ... I see your ticket - # 4713 - but, it refers to the Japanese version of PB. Is that really the case?
  1. Helpful
There are no comments made yet.
Alexander Skorokhodov
Alexander Skorokhodov Accepted Answer Pending Moderation
  1. Thursday, 28 May 2020 06:57 AM UTC
  2. PowerBuilder
  3. # 3

Chris:

these shared files pbjson170.dll, pbhttpclient170.dll, pbrestclient170.dll 

were there in the released system root directory on client machine along with all other files,

and the system was core dumping.

then, i downloaded the latest  PBL 2017R3 build 1915, recompiled the system and placed all shared files from this build

in the system root. Still, no luck, same error   bad runtime reference on  dw_1.ImportJson(l_License_Json).

 

system runs fine from the development environment, and it runs fine as .exe on my development machine,

ImportJson works as it should, so there must be additional setup that i am still missing on the client machine.

pls advise further, if you can.

thank you for help.

sasha

 

 

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 28 May 2020 14:30 PM UTC
Hi Sasha;

That should be all that you need AFAIK. Please open a Support Ticket for this issue and attach a small Test Case PB App so that we can help you further in this mystery.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 27 May 2020 19:15 PM UTC
  2. PowerBuilder
  3. # 4

Hi Alexander;

  Did you copy the following DLL's from the "Shared" PB2017R3 folder over to your deployment PC?

pbjson170.dll, pbhttpclient170.dll, pbrestclient170.dll

  They are required for JSON processing.

HTH

Regards ... Chris

Comment
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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.