Nice pleasant surprising update..

I renamed the existing windows user to another name and created a new windows user in the same old user name and continuing my development.   The old [corrupted ?] windows user is there in another name.

When I started creating an external DW as suggested by Mark, I got a pleasant surprise.   Yes I could create the dw.  Then I tried to open existing DW, that too I could open.  Only thing it takes around 30 seconds to 60 seconds to open / create dw from that [ renamed corrupted ] user.  [  Earlier we waited for around 15 min. with no success ].

The same dw could be opened / created from other users from the same machine almost instantly.

Hi,

You've had some great responses from Miguel, John and René so these questions/ suggestions may not add much insight. It just seems that it has to be something more specific (to PowerBuilder) than a generally corrupted user account. Are there other apps etc. for this user account that are not working?

Anyway, here are mine:

1) Can this user right click on a datawindow and select Edit Source without an error (make changes and actually save it, regenerate it...obviously do this on a DWO that is not important or make a minor change but be very careful here)?

2) Can this user create an external datawindow without an issue?

3) Can this user connect to a completely different database (EG PB Demo DB) on this machine and create a datawindow (via tutor_pb.pbl, or maybe it was appeontutor.pbl for 2017)?

4) One of the suggestions from Miguel I think was replacing the pb.ini with one from a working user account...which unfortunately didn't work. How are you currently connecting to your databases? Is it via an ODBC connection? I would also look at changing/ swapping out the pbodb.ini file in the specific user's path (probably something like C:\Users\Sivaprakash\AppData\Local\Appeon\PowerBuilder 17.0)...especially if the modified date on this file is around the day/time this became a problem.

Again, not too hopeful on the above but just my thoughts.

Regards,
Mark

Hi BKR;

   This sounds like a corrupt DWO source to me. My suggestion would be to either return to a stable backup copy or recreate the DWO from scratch all together.

Regards ... Chris

Let's try to remove the DataWindow Painter from the scenario for a minute...

Are you able to open/use the Database Painter on the machine having the problem?

Can you successfully open the DB Profile dialog and connect with an existing profile?

Can you set up a new database profile?

If you run an application from within the IDE, does it connect to the database successfully, retrieve data, etc.?

Do you get any information from the windows eventviewer?

Have you tried opening powerbuilder with "Run as Administrator" from right mouse button menu?

Update:  

Same issue in PB  11.5 also.  Just now checked.

I don't think this will be the problem, but you never know:

If it's only happening with one specific datawindow, maybe it's to do with access rights on the table(s) used in the datawindow for that user? Also, check with what user the user is connected to the db in the db profile in the pb IDE.

If the same user tries on another machine, does it still happen?

Check the pb.ini file and set these 2 values:

[Data Window]
PreviewOnNew=no
PreviewRetrieve=0

regards

Maybe something is wrong with the saved painter layout settings in the registry. You could try to delete this settings from registry.

https://community.appeon.com/index.php/qna/q-a/cannot-open-any-datawindows