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

Resolved Powerbuilder IDE stops working during build of application

  1. Issue
0
Votes
Undo
  1. Greg Heiner
    Greg Heiner
  2. PowerBuilder
  3. Friday, 23 February 2018 16:46 PM UTC

I installed PB2017 R2 fresh (after uninstalling PB2017) and migrated my source.  All went well.  I can run the app from the IDE and things look and perform perfectly, as far as I have tested.  I'm now trying to create an executable app so we can do more testing.  When I deploy the project all goes well again and it writes all the files (exe and pbd's) and at the very end the IDE crashes with "Appeon PowerBuilder 2017 R2 has stopped working".  All the pbd's are created and I can run the app from the exe so I think it finished the process but the IDE crashed.

I found a support case (Bug 496) that seems to describe the same problem and the person posted that they solved the issue saying:

"The problem was solved by adding pbdom17.pbx to the application.  pbdom125.pbx was still being referenced after the migration."

I'm not sure what "adding pbdom17.pbx to the application" means.  I found the file pbdom170.pbx in the Shared folder in "C:\Program Files (x86)\Appeon\Shared\PowerBuilder" and I put it in my source folder, and deleted the pbdom115.pbx, and that did not solve the problem.  I then added pbdom170.pbx to the Library list and that did not fix the problem either.

I'd appreciate any ideas that might help resolve this problem.

-Greg Heiner

 

  1. IDE
  2. Build
Opposite of OLE Control "InsertFile" method
Is TortoiseSVN 1.6.16 compatible with PB2017 R2?
Responses (2)
Greg Heiner
Greg Heiner Accepted Answer Pending Moderation
  1. Friday, 23 February 2018 17:59 PM UTC
  2. PowerBuilder
  3. # 1

I figured out what the issue was and fixed it.  All is well now and the app compiles fine.  There were references in the source code to "pbdom115.pbx" and I just needed to change the "PBDOM115.pbx" to "PBDOM170.pbx".

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 23 February 2018 18:29 PM UTC
Yes, that would have definitely corrupted your compile if you had not swapped out the PB 11.5 DOM with the PB 2017 DOM!



I am so glad that you found your issue! 

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 23 February 2018 17:36 PM UTC
  2. PowerBuilder
  3. # 2

Hi Greg;

       It sounds like this is a "red herring" for you. PB DOM isused to pase an XML schema and its data stream. The XML (like HTML) is formed using a "Document Object Model". Since you did not have any DOM library attached before you migrated, you do not need to add this library now to your Target. The reason the original ticket holder had the problem is that they used DOM processing and the DOM code changes with each PB release. They should have replaced the older DOM library with PB 2017's after the migration right away - otherwise, the compile and/or run-time will surely fail.

     In your case, its sounds like their is something amiss in your PB App's code line. However before we get deeper into that - I would first recommend that you "Optimize" all your Apps PBL's, do a Full Generate, close/re-open your PB IDE and then try the build process again. If that still fails, please open a support ticket for this issue.

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.