When this exact situation happened to me, it turned out to be a bad compile - and the application itself was just hosed.

To resolve this, I did a FULL BUILD on the app, then went through each PBL, selecting and REGENERATING the objects.
Sure enough, several of the windows had been messed up and had to be restored from back-up. Once they regenerated correctly, and once ALL ofthe hosed objects were corrected, everything returned to normal.

Hi Mark.

Thank you very much for your suggestions. I had completely forgotten that we could disable the workspace on startup. Changing the settings as you suggested has allowed me to open other workspaces again. Now I am able to look into the other applications as Chris mentioned.

Unfortunately the IDE still has problems running the applications.  Attached is a screen shot of the Task Manager while running the app from both the PB 2019 R3 and PB 12.5 IDEs.  The 12.5 IDE is operating as expected.

I will try one or two other workspaces, but at this point I would be surprised if I don't ultimately end up reinstalling the IDE.

Thank you again for the workspace suggestion.  It is much appreciated.

Hi Craig,

I can't offer too much at this point with the problem of why this may be happening with that particular Workspace, but I wonder if you changed your settings to not open a Workspace upon starting the IDE if that will help you to continue trouble-shooting by switching Workspaces, per Chris' suggestion. Assuming the IDE is not so unstable that you can't access the menus, then click on Tools, System Options then go to the Workspaces tab and uncheck Reopen workspace on startup.

If it is so unstable such that you can't even access the menus to change this option before it crashes, then navigate to where your PB.INI file is located. This may depend upon where/ how you installed PowerBuilder but on my machine, for example, it's located in "C:\Users\Mark\AppData\Local\Appeon\PowerBuilder 19.0". Then locate the line "ReopenWorkspace=1" and change the 1 to a 0, then try and start PowerBuilder again. You could also leave the setting as 1 but change the line in the PB.INI file that points to the last open Workspace ("LastWorkspace=........") and change it to a known working Workspace.

From there hopefully you would be able to open another Workspace, or maybe the previous working version of the Workspace in question, and continue trouble-shooting. However, if you still have a problem with the IDE crashing without a Workspace even open, or a known working Workspace open, then I would consider re-installing PowerBuilder.

PS...before you try and open a known working Workspace I would recommend making backups first.

HTH...regards,

Mark

Hi Craig;

  Do you have another workspace / target that allows you to run the App without any Enable libraries attached in order to rule out your App vs Enable as the issue?

Regards ... Chris

Hi Chris.

As it turns out, I was incorrect in my initial assumption about what I was seeing.  The application didn't hang in the IDE.  It became extremely slow though.  We are using Enable from Novalys.  When I run the application from the IDE and I have the Enable functionality enabled, it takes almost 10 minutes to display the login splash screen.  If I disable the Enable functionality it gets to the login splash screen much faster, but the application still runs considerably slower than it used to from the IDE.  This seems to be limited to the IDE.  The deployed application seems to run fine.

There is another side-effect that I noticed.  Now when I try to close the workspace, the IDE crashes as well.  So I cannot even switch to another workspace now.  When I bring the IDE back up, it still comes up in the same workspace.  Do you think it would help to uninstall and re-install PB 2019 R3 or is there something else that I should be looking into?

Thank you.

Craig

Hi Craig;

   Have you tried performing an "Optimize" on all your App PBLs, Full Build & then recycle the IDE to correct this issue?

Regards ... Chris