Hi Chris,

I installed the Powerbuilder build 2670 on a new virtual machine, packed the runtimes and delivered them with the program. Unfortunately, the stability has not changed. There are 3 examples in the appendix.
Do we have the option to reset from PB2019R2 to PB2019? We have been using R2 since April 2020. Are the DW’s from PB2019R2 compatible with PB2019? We would expand the ribbon bar again

Regards   Rudi

Thanks Rudolf;

  Your event log definitely states that your App is running a PB2019 R2 build 2353 based App. So you you do not have to worry about PBVM DLL's from R3 crashing your PB App EXE.

  What could be your problem though is:

1. There are some lower version based PBVM DLL's (say from release - build 2323) or even the GA release of PB in your App's EXE environment. That would allow your app to start but could "derail" it once further execution starts. So make sure that all the PBXXX190.dll's in the deployment machine match your PB IDE development environment build - for example their date/time stamps and sizes match exactly.
2. The next issue could be the DLL's that are provided in the PB IDE's runtime that are not of the PBxxxnnn.dll format. These DLL's are for example: LIBxxxx.dll, MSCVPxxx.dll, etc. These are all well documented in the PB Help file under the "runtime" deployment list of DLL's. If you mix these non-numbered DLL's from PB 2019 Rx or event from PB2017Rx - as they are the same names - your App's could definitely have random runtime crashing issues. So this would also be another "deployment" consideration to make sure that these DLLs come from the proper PB build.

HTH

Regards ... Chris

Hi Rudi,

I'm a bit confused: You are saying "

We have massive problems after switching from 2019 R2 to 2019 R3

"

Is your customer running an executable made with R2 or R3?

It could be someone forgot to install the runtime for R3 or maybe someone forgot to install the new application compiled against R3?

regards

Miguel is right: this is most likely due to running the new 2019R3 EXE with 2019R2 DLLs.

1. Uninstall PB2019R2.
2. Manually check the various folders to ensure that R2 has been deleted.
3. Reboot the PC/VM.
4. Install R3.
5. Install your app.
6. Test.

That should resolve the issues you are experiencing.


Olan

Hi Chris,

my customer made this event log available to me

Regards

Hi Rudolf，

Currently it is hard for us to locate the issue based on your description. I suggest you:
1. Reinstall PB, make sure the PB runtime files are correct and see if it is OK.
2. Or use a clean machine that doesn’t have any PB products installed before and then install PB 2019 R3 directly to see if the issue still exists.
3. In the directory where yourapp.exe resides, create a pb.ini file with the below content and then run your application to see if it is OK.
[Data Window]
ACCESSIBILITY=0

If the issue still exists after trying the above steps, could you please provide a test case for us to analyze?

Regards,
Ken

Hi Chris

Line 90
Function uf_tracefilter("destroy lds_help")
********
integer li_file
li_file=fileopen("_planungfilter.txt",LineMode! ,Write! ,Shared! ,Replace! )
filewrite(li_file,as_expr)
fileclose(li_file)

mostly no entry in event log
I'll check it out with the customer tomorrow

No change of DBMS version or build

The program ran for several hours without interruption

the crash in IDE and runtime

I run some .. /debug in the past. most crashes near an destroy

regards

Hi Rudolf;

   Can you tell us ...

1. What command is at line 90?
2. Did you get any mini-dumps when the App crash occurred?
3. Can you check and see what is in the O/S Event log around that App crash?
4. Have you run a /PBTRACE on the PB App EXE?
5. Did you change a DBMS version or build?
6. Did you change a DB Client used to connect to the DBMS?

Regards ... Chris