1. Lucia Radita
  2. PowerBuilder
  3. Tuesday, 2 March 2021 22:54 PM UTC

Hello Appeon team,

Currently we are using PowerBuider2017R3 with MSOLEDBSQL driver.

We are evaluating the new PowerBuilder 2019R3, fully supporting MSOLEDBSQL driver (according to release announcement)

For this evaluation we are using the trial PB2019R3 build #2670; the patch [19.2.0.2670_DLL] has been applied, mainly to have the fix for response windows open in the center of the screen instead of defined position. We are not using "theme" feature.

OS is Windows 10

The DB is SQL Server 2016.

We are observing that PB IDE is randomly "freezing" or simply closing (crashing).

Few ex, of such events from  Windows Event-viewer:

//**********************

The program PB190.exe version 19.2.0.2670 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 1c34
 Start Time: 01d70f87619c00b6
 Termination Time: 58
 Application Path: C:\Program Files (x86)\Appeon\PowerBuilder 19.0\PB190.exe
 Report Id: 6d40913b-0d7e-42a6-95fa-f9624043c664
 Faulting package full name:
 Faulting package-relative application ID:
 Hang type: Unknown

//**********************

Faulting application name: PB190.exe, version: 19.2.0.2670, time stamp: 0x6009628d
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x75165b20
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Faulting package full name: %14
Faulting package-relative application ID: %15

//*********************

Application: PB190.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 75165B20
Stack:

//***********************

Faulting application name: PB190.exe, version: 19.2.0.2670, time stamp: 0x6009628d
Faulting module name: PBVM.dll, version: 19.2.0.2670, time stamp: 0x601cef89
Exception code: 0xc000041d
Fault offset: 0x001c1ec9
Faulting process id: 0x2080
Faulting application start time: 0x01d70f759a58756a
Faulting application path: C:\Program Files (x86)\Appeon\PowerBuilder 19.0\PB190.exe
Faulting module path: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.2670\PBVM.dll
Report Id: 4bf16fca-e088-4743-8f29-095d67683244
Faulting package full name:
Faulting package-relative application ID:

//*******************************

Faulting application name: PB190.exe, version: 19.2.0.2670, time stamp: 0x6009628d
Faulting module name: MSVBVM60.DLL, version: 6.0.98.48, time stamp: 0x5ea8e7bc
Exception code: 0xc000041d
Fault offset: 0x00002fcb
Faulting process id: 0x1534
Faulting application start time: 0x01d70eb85ad4be2e
Faulting application path: C:\Program Files (x86)\Appeon\PowerBuilder 19.0\PB190.exe
Faulting module path: C:\Windows\System32\MSVBVM60.DLL
Report Id: 53a23d06-4f57-4e88-92cd-0d639fd6c963
Faulting package full name:
Faulting package-relative application ID:

//*******************************

Please advise.

Thank you

 

 

Lucia Radita Accepted Answer Pending Moderation
  1. Tuesday, 9 March 2021 16:37 PM UTC
  2. PowerBuilder
  3. # 1

We decided to renew our annual license by upgrading to PowerBuilder 2019R3 Professional.

Currently I have installed on my PC PowerBuilder 2017R3.

Do I need to uninstall first PB 2017R3 version and than install the new PB 2019R3?

thank you

Comment
  1. Armeen Mazda @Appeon
  2. Tuesday, 9 March 2021 16:45 PM UTC
No need to uninstall... major versions of PB can co-exist side by side. PB 2019 R3 supports the MSOLEDBSQL driver, and the Professional Edition you purchased has a great new feature called PowerClient: https://www.appeon.com/products/power-client
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 3 March 2021 18:26 PM UTC
  2. PowerBuilder
  3. # 2

Hi Lucia;

  I see from references to the "MSVBVM60" DLL that this could be using a really old legacy DLL, which is normally used to interface to the VB runtime. Do you have old VB components somewhere in your PB App that you are using (referencing)?

Regards ... Chris

Comment
  1. Lucia Radita
  2. Wednesday, 3 March 2021 21:34 PM UTC
Currently my problem is with PB IDE. I open an user object (ex. our transactional SQLCA ) and want to make changes. It takes time (2 sec) to fully display the code in editor, the mouse scroll is not working. If I move the cursor (pageUp/Down keys) or scroll bar it ends-up quickly by freezing.

The PC where this trial version is installed is a VM Windows 10 to which I connect via RDP.

I followed Olan's suggestion to uninstall / re-install PB2019R3 without applying the patch. There is no change in behavior, furthermore we need the patch since the opening of a response w. in the middle of the screen is an important drawback for clients.

To answer the question, yes we have some dlls in VB6 that are called by the application at runtime.

Currently the problem is not when the app is running but developing it.

Thank you.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Wednesday, 3 March 2021 21:49 PM UTC
Hi Lucia;

Yes, I would be very surprised if reinstalling the IDE would affect your stability issue for the IDE.

The VB6 controls could be the stability issues after a full build, deployment, running the App from the IDE etc. The PB run-time and IDE would handle these controls as a sub-task (external resource). If these error and do not catch a run-time issue - as a sub-task, the main task (ie IDE) is penalized by the O/S as the culprit. Hence the IDE crashes.

Another aspect is that the RDP session is creating an instability around your IDE by aggravating OCX, OLE, etc controls in the way that they are instantiated and/or destroyed. Its hard to say but I have seen that in the past.

Thought... What happens if you edit another PB Application - say one of the Appeon "Demo" apps. Any IDE instability there?

Regards ... Chris
  1. Helpful
There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Tuesday, 2 March 2021 22:59 PM UTC
  2. PowerBuilder
  3. # 3

Try reinstalling R3, only this time do NOT install the patch [19.2.0.2670_DLL].
I had a similar experience and this is what I did to resolve the issue.

Olan

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