1. Matt Kulka
  2. PowerBuilder
  3. Wednesday, 1 July 2020 14:02 PM UTC

I'm running Powerbuilder 2017 R3 build 1880.  I can open Powerbuilder the standard way, by clicking the icon.  But if I go to Windows Explorer and double-click a PBW, PB starts to open but then gives an error "Attempt to open DataWindow failed."  I also get the error if I right-click the PB icon and select any but the latest workspace.  It's been this way since I installed PB on this machine.  Does anyone else have this problem?  Moreover, has anyone solved it without an uninstall/reinstall?

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 1 July 2020 16:50 PM UTC
  2. PowerBuilder
  3. # 1

Hi Matt;

  I've seen this issue a couple of times. One recently in a support ticket. When I had a virtual meeting with the customer, we recreated the same issue but could not on a different PC or with other developers.

   My guess is that it's a registry setting somewhere that's off but hard to pin down. Most people with this issue get it resolved when the IDE is upgraded - even with an MR.

  Speaking of MR's, your build is quite old. My suggestion would be to update to the lastest PB2107 - build 1915 which is R3 (the long term supported version). This "should" correct the workspace issue.

Regards ... Chris

Comment
  1. Matt Kulka
  2. Thursday, 2 July 2020 16:20 PM UTC
Thanks Chris. That's about what I expected.



And all of our devs are kept on the same build. It's probably a policy left over from some ancient version of PB. I'll ask management about coming up to 1915.
  1. Helpful
There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Wednesday, 1 July 2020 16:24 PM UTC
  2. PowerBuilder
  3. # 2

Does the PowerBuilder IDE get opened and THEN it dies?
 - That would indicate that the IDE opens, but fails when it's attempting to open a DW that was open when last the IDE was closed.

If that's the case, get into the INI file and delete everything under the [Application] section.

[Application]
DefLib=C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexamfe.pbl
WorkingDir=C:\Program Files (x86)\Appeon\PowerBuilder 19.0
$C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexamfe.pbl(examples)=C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexamfe.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexamw3.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexamd2.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexamfn.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexammn.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexamuo.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexamw1.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexamw2.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexamd1.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexamsa.pbl;
$C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexbm.pbl(benchmark)=C:\Users\Public\Documents\Appeon\PowerBuilder 19.0\Code Examples\Example App\pbexbm.pbl;

Comment
  1. Matt Kulka
  2. Thursday, 2 July 2020 16:17 PM UTC
I just retested to confirm. It happens even if the library painter was the only open window when that workspace was closed.
  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.