1. Alexander Skorokhodov
  2. PowerBuilder
  3. Thursday, 24 June 2021 18:14 PM UTC

Dear Appeon:

i have a generic PBL timer event defined in my main app window

calling a window function. Timer interval is set to 1 min.

I released my system to two win 10 servers.

On one server, timer works fine. On another server, timer does not kick off.

Can this issue be related to Win 10 server settings?

Please advise, thank you.

sasha

 

 

 

 

 

Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 24 June 2021 19:34 PM UTC
  2. PowerBuilder
  3. # 1

PB2019R3, build 2703
Windows 10

Funny, as in not "ha -ha", you should mention this.

I just tried to set a timer in my MDI application on the FRAME window (of type MAIN), and it failed to trigger.
Yes, I have all of the Microsoft DLLs included.

I have successfully used the TIMER event and TIMER() function calls in other windows and objects so I know the DLL collection I need to have is present.

Maybe I did something incorrectly, but I suspect this has something to do with the fact that this is my frame window. I'll research this later when I get some time.

Comment
  1. Olan Knight
  2. Monday, 28 June 2021 22:11 PM UTC
My post has been updated again. :)

  1. Helpful
  1. Chris Pollach @Appeon
  2. Tuesday, 29 June 2021 15:32 PM UTC
Hi Olan;

FWIW: I tested the Timer feature on a few of my MDI Frame based Apps and had no issues with its functionality. My PB is of the same build (2703) and I am using W10 version 21H1, build 19043.1052.

Regards ... Chris
  1. Helpful
  1. Olan Knight
  2. Tuesday, 29 June 2021 17:37 PM UTC
Thanks Chris!

I'll check this out with more attention to detail, and will report on my results.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 24 June 2021 18:23 PM UTC
  2. PowerBuilder
  3. # 2

Hi Sasha;

   FWIW: I have seen this issue before in a Support Ticket where the customer did not deploy all the non-PB runtime DLLs as listed in the PB Help. The PB runtime DLLs have dependencies on these Microsoft DLL's and if missing them or they are too old, that can cause timer issues like you are observing.

  My suggestion is to look into the PB Help under the keyword search for "runtime" and then take the resulting link over to the list of files you need to deploy with your App's EXE. Also take note though about the non-PB DLL dependencies that you need to deploy as well.

HTH

Regards ... Chris

Comment
  1. Alexander Skorokhodov
  2. Friday, 25 June 2021 04:30 AM UTC
Chris:

Thank you for the response.

It turned out that the issue was different here. I do not fully control releases to that client, I only provide the system ,pbds, and someone else (SE) rolls the system out on site. It turned out, that SE replaced the newly complied system .exe in one place and forgot to do so in the other. So, timer event failed because of old .exe, probably compiled under PBL 2019R1, Once this old .exe has been replaced with the new one, system started to work correctly.

sasha

  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 25 June 2021 13:22 PM UTC
Hi Sasha;

I am super glad that you located the source of the problem! ;-)

Regards ... Chris
  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.