1. Sivaprakash BKR
  2. PowerBuilder
  3. Friday, 9 April 2021 05:48 AM UTC

Hellol

PB 2017R3

Suddenly I could not create / open datawindow in PB IDE for one particular windows user [Windows 10].  When I double click the datawindow, the PB IDE just goes into loop [ cursor changes to circle as if long operation is going on]. It was working fine till a couple of days back.

Could open / create datawindow from other windows users [switch user, select other users] from the same machine.   Could open /create datawindow from other machines in the same application.

Only from this machine / user combo, I could not open datawindow.  No issues with other PB objects.

What could have went wrong ?  Any suggestion to rectify this issue ?

Happiness Always
BKR Sivaprakash

 Update:  Same issue in PB 11.5 also.

René Ullrich Accepted Answer Pending Moderation
  1. Friday, 9 April 2021 08:17 AM UTC
  2. PowerBuilder
  3. # 1

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

 

Comment
  1. Sivaprakash BKR
  2. Friday, 9 April 2021 08:49 AM UTC
Thanks Rene Ullrich.

It didn't solve this issue. Here PB doesn't closing, but goes into a loop (hangs ?). Cursor changes to circle as if long process is happening. We have to force close PB.

  1. Helpful
  1. René Ullrich
  2. Friday, 9 April 2021 09:43 AM UTC
Is it only ony specific datawindow or with all datawindows.

Maybe there is a problem with the preview retrieval?
  1. Helpful
  1. Sivaprakash BKR
  2. Friday, 9 April 2021 13:12 PM UTC
With all Datawindows in all projects.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Friday, 9 April 2021 10:16 AM UTC
  2. PowerBuilder
  3. # 2

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

Comment
  1. Sivaprakash BKR
  2. Saturday, 10 April 2021 05:02 AM UTC
Yes Miguel, since PB works fine with other windows users, I did rename the [corrupt] windows user and created a new windows user in the same name and proceeding. It's working. Still trying to figure out anything could be done to rectify this issue..
  1. Helpful
  1. Miguel Leeuwe
  2. Saturday, 10 April 2021 08:06 AM UTC
Glad to hear that. I think that maybe you should start looking for a solution with Microsoft forums.

If you temporarily rename the new user and rename back the old user, you can try things like

SFC /scannow and use Dism:

https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/sfc-scannow-and-dismexe-online-cleanup-image/db3b24de-a261-403e-9d11-8141d13f7954

regards
  1. Helpful
  1. Miguel Leeuwe
  2. Saturday, 10 April 2021 14:59 PM UTC
Another thing you could try, instead of trying to fix the old user, is to re-install one of you powerbuilder versions and see if the problem goes away for that version. If that works, then re-installing might be a better solution than having to re-install all the other non powerbuilder apps and configurations you might not want to lose.



As a last maybe a silly thing that comes to mind:

Windows has these "virtualstore" entries in the registry, which many times have caused all kinds of problems. Most of the time, simply deleting them from the registry can fix problems (do a backup of the registry first though).

You could also try to run a registry cleaner like CCleaner, but in my experience some versions of Appeon stopped working properly after running it. (so again, do a backup copy first with CCleaner itself).

regards
  1. Helpful
There are no comments made yet.
Sivaprakash BKR Accepted Answer Pending Moderation
  1. Friday, 9 April 2021 13:21 PM UTC
  2. PowerBuilder
  3. # 3

Update:  

Same issue in PB  11.5 also.  Just now checked.

Comment
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Friday, 9 April 2021 13:26 PM UTC
  2. PowerBuilder
  3. # 4

Do you get any information from the windows eventviewer?

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

 

 

Comment
  1. Sivaprakash BKR
  2. Friday, 9 April 2021 13:44 PM UTC
Already checked. Nothing unusual in windows event viewer.

Already the mentioned user's type is Administrator. Nevertheless tried with 'Run as Administrator', no success.

Seems this issue is there in all PB that I use, PB 10.5, PB 11.5, PB 2017R3.

  1. Helpful
There are no comments made yet.
John Fauss Accepted Answer Pending Moderation
  1. Friday, 9 April 2021 14:34 PM UTC
  2. PowerBuilder
  3. # 5

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.?

Comment
  1. Sivaprakash BKR
  2. Saturday, 10 April 2021 04:49 AM UTC
Thanks John Fauss...

1. No issues in Database painter.

2. No issues in DB Profile dialog

3. Yes, can edit and create new database profiles without any issues.

4. Yes, I could run the application without any issues.

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Saturday, 10 April 2021 13:40 PM UTC
  2. PowerBuilder
  3. # 6

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

Comment
  1. Chris Pollach @Appeon
  2. Saturday, 10 April 2021 14:30 PM UTC
Thanks Mark ... I finally saw that at the very end reply. Since it's accross multiple versions of PB, this sounds like it's totally environmental maybe.
  1. Helpful
  1. Mark Goldsmith
  2. Saturday, 10 April 2021 14:39 PM UTC
Agreed...which I think is why when the current user account was renamed and a new user account was created using the old user account name it worked. This is also why I wasn't too hopeful on my pbodb.ini idea since there would be multiple pbodb.ini(s) across multiple versions of PB...unless by subsequently trying each version of PB it corrupted the respective pbodb.ini file.
  1. Helpful
  1. Sivaprakash BKR
  2. Sunday, 11 April 2021 04:16 AM UTC
Thanks Chris,

Same DWOs works fine when opened from other computers. Also from the same computer in another windows user.

So no chance for any corruption issue, IMO.
  1. Helpful
There are no comments made yet.
Mark Goldsmith Accepted Answer Pending Moderation
  1. Saturday, 10 April 2021 14:21 PM UTC
  2. PowerBuilder
  3. # 7

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

Comment
There are no comments made yet.
Sivaprakash BKR Accepted Answer Pending Moderation
  1. Sunday, 11 April 2021 04:40 AM UTC
  2. PowerBuilder
  3. # 8

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.

 

Comment
  1. Sivaprakash BKR
  2. Monday, 12 April 2021 08:40 AM UTC
Miguel,

Same application works fine from other machines with same named user or different user. No issue of slowness is there.



Arnd,

I'll use the procmon and let you know the results.

  1. Helpful
  1. Miguel Leeuwe
  2. Monday, 12 April 2021 15:32 PM UTC
Hi,

If any objects different than datawindows, open up fine (not slow), that would make me think it has something to do with your database client installation. That would also explain that you have the problem on each and every version of powerbuilder.

Good Luck!
  1. Helpful
  1. Sivaprakash BKR
  2. Tuesday, 13 April 2021 05:53 AM UTC
Slowness is there when I connect different database [ SQL Server, PostgreSQL] from that particular user only. When I connect the same database from another windows user [from the same machine] it works fine [ no slowness]. IMO, I don't think database client installation will be the issue.

Tried connecting SQL Server via OLE DB and SQL Native Client and Postgres with ODBC.

  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.