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

Resolved Migrate Webservice from 12.5.2 build 5602 to 2017 R3 build 1880

  1. How-to
0
Votes
Undo
  1. MARKOVIC Marko
    MARKOVIC Marko
  2. PowerBuilder
  3. Tuesday, 26 February 2019 10:10 AM UTC

Hi everyone,

we are in our migration phase of PB 12.5.2 to 2017 R3. I'm imported the workpsace and target without problems.  I've deplpyed the webservice to create the new dll of my webservice. Trying to run the application in desgin mode and got system error message "21 Bad runtime function reference at line ... ".

I know there is a problem with Dll's but i didn't found yet which is missing or in conflict. i've tried to copy the version of "shared " directory of appeon of Dll's: msvcp100.dll, msvcr100.dll, atl100.dll in System32 and SysWOW64, but nothing changed.

Some advices what i've missed?

This is what is installed on my developper machine.

 

Regards

Migration - From PB 11.5 to Appeon PB 2017
Changing to latest SQL Server ODBC Driver
Responses (5)
MARKOVIC Marko
MARKOVIC Marko Accepted Answer Pending Moderation
  1. Wednesday, 27 February 2019 10:08 AM UTC
  2. PowerBuilder
  3. # 1

Solution found here:

https://www.appeon.com/developers/get-help/knowledgebase/calling-soapconnection-results-bad-runtime-function-reference.html

 

There was a version conflict with libeay32.dll in syswow64 windows folder. Renamed, now it works.

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 26 February 2019 19:07 PM UTC
  2. PowerBuilder
  3. # 2

Hi Marco;

   I would suggest placing a break point near the beginning of the failing script and then use the IDE's debugger to step through your code to see what internal / external resource(s) is being referenced just before the command line number that fails is executed.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Tuesday, 26 February 2019 14:48 PM UTC
  2. PowerBuilder
  3. # 3

A Bad Runtime Function error has nothing to do with the runtime dll files.

It tried to call a function in your code but the function wasn't found. Perhaps the object wasn't instantiated or the signature was different than expected. There a lot of possibilities.

Comment
There are no comments made yet.
MARKOVIC Marko
MARKOVIC Marko Accepted Answer Pending Moderation
  1. Tuesday, 26 February 2019 14:44 PM UTC
  2. PowerBuilder
  3. # 4

Sorry don't helped.

i've put it in the application path then try in SysWOW64 and then try in System32. Still got the error.

Something else?

Comment
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Tuesday, 26 February 2019 14:32 PM UTC
  2. PowerBuilder
  3. # 5

You'll need these:

libjcc.dll
libsybunic.dll
libjutils.dll
libjtml.dll
nlwnsck.dll

 

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.