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

Resolved Deployed PB2019R2 application strange behavior

  1. Issue
0
Votes
Undo
  1. Pierre DETE
    Pierre DETE
  2. PowerBuilder
  3. Tuesday, 24 November 2020 14:09 PM UTC

Hi PB users,

 

We are facing a strange behavior with deployment of our PB2019R2 application (KTP).

On some laptop, in our login window, the code seems to try to close the window after open.

When we activate /PBDEBUG (parameter after .exe file) the problem disappear.

This almost the same old login window we used with all PB versions, working properly in 11.5,12.5 and 2017.

There is open event (pbm_open) posting a custom event by "this.PostEvent("init_fenetre")".

In the "init_fenetre" event the user choose an .ini file, some variable and transactions are initialized and there is a test on commandParm() parameters.

parametres = CommandParm ()

parametres = Trim (parametres) 

IF parametres = "" AND sle_user.Text = "/" THEN PostEvent (pb_connect, Clicked!)
IF parametres = "" THEN RETURN

 

The only way to trace is to insert messagebox and recompil and reproduce on laptop with the issue.

Here is the conclusion :

After the RETURN, instead of staying on the window, the code is firing a close event, in which there is an HALT CLOSE just after an error message "Transaction not connect".

The PC with the issue on deployed application, are working in IDE mode and /PBDEBUG mode.

For now this version is not deployed to client's environments, but we are sure some of them will have the issue.

We need help to understand where is the problem. We check DLL, .NET, Visual C++ Redist, ... etc without founding a difference between the Laptops OK and those which have the issue.

 

Do you have any idea on what we do to correct this? We don't have any more :(

 

Best Regards,

 

Pierre

 

 

 

 

 

 

 

 

 

Will PowerServer support non-visual PBNI extension...
PB 19R2 Run and Debug fails
Responses (2)
Benjamin Gaesslein
Benjamin Gaesslein Accepted Answer Pending Moderation
  1. Thursday, 3 December 2020 11:15 AM UTC
  2. PowerBuilder
  3. # 1

There's clearly some race condition error at work here but it's impossible to know what's happening with the available code snippets. Maybe try triggering instead of posting events unless they absolutely need to be posted. Posting multiple events that might need to run in a specific order is often a recipe for unforseen consequences.

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 24 November 2020 16:34 PM UTC
  2. PowerBuilder
  3. # 2

Hi Pierre;

   Does the App's EXE work OK on the Development workstation but falter on the deployment machine?

Note: Running the App via the PB IDE's Debugger or an EXE using the /PBDebug option can change the timing / order of when certain events fire.

Regards ... Chris

Comment
Pierre DETE
  1. Pierre DETE
  2. Thursday, 3 December 2020 10:46 AM UTC
Hi Chris,

The App's EXE work on dev workstation and many others (about ten workstations DEV and QA). For now there is only 3 BA laptops already working fine with PB2017 EXE and not able to use new PB2019 deployments, very strange.



Regards... Pierre
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 3 December 2020 18:34 PM UTC
Very strange indeed. How does the O/S version / build compare on the PC's that work vs the ones where the App does not? Also, what about hardware differences between the two?

FWIW: I once found a few issues like this where a certain CPU type was the problem or another where video cards used caused another.
  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.