Bug 6620

Failed to load pbsys.dll 14 June, 2021

Matt Balent
18 May, 2021
Product: PowerBuilder Category: Installation
Version: 2019 R3 Build: 2703
Classification: Issue Publishing: Public
Priority: P2
Status: Closed Reason: RESOLVED
Aubrey Lin @Appeon 14 June, 2021
#26
Hi Matt,

Thanks for the feedback! Since the issue is solved, we are now going to close this ticket but please remember that you can always open a new one if any issues happen in the future.

Have a good day!

Regards,
Aubrey
Matt Balent 14 June, 2021
#25
I was able to install PB2019 R3 MR successfully and it runs fine.
Aubrey Lin @Appeon 11 June, 2021
#24
Hi Matt,

Carbon Black has marked PB 2019 R3 pbshr.dll as 0 threat.

Please update Carbon Black or update its virus database and you can do a installation for verification.

Regards,
Aubrey
Aubrey Lin @Appeon 28 May, 2021
#23
Hi Matt,

Our developers are analyzing the issue of DLLs failed to register. Could you help provide the 2021 installation log for us? It's named PB_2021_Install.log which can be found at C:\Windows\SysWOW64\AppeonInstallLog\PB_2021_Install.log.

Could you also help check the antivirus interception/block records and see if there's info of operation of it stopping files from registering? Thanks in advance!

Regards,
Aubrey
Aubrey Lin @Appeon 26 May, 2021
#22
Hi Matt,

Thanks for the information!

Since PowerBuilder 2021 installed and worked fine, we won't make extra change to it for now but will try to find out why the DLLs fail to register and enhance it in subsequent version.

And for the pbshr.dll of PowerBuilder 2019 R3 blocked by Carbon Black, we will contact the related vendor to whitelist this file.

We will update here if we need more information. Thanks!

Regards,
Aubrey
Matt Balent 25 May, 2021
#21
Well that's the funny thing.  2021 installed and worked fine, it was only 2019 that had the problem with pbsys.dll.
Aubrey Lin @Appeon 24 May, 2021
#20
Hi Matt,

I checked with the developers and the dll files prompted not registered do rely on pbshr.dll.

From the information you provided, it was pbsys.dll of PowerBuilder 2019 R3 that was blocked. Can you help confirm if pbshr.dll/pbsys.dll of PowerBuilder 2021 Beta was blocked too?

Regards,
Aubrey
Matt Balent 24 May, 2021
#19
When the file was whitelisted for the Carbon Black anti-virus PowerBuilder 2019 R3 now launches correctly.  This may have had something to do with the other files not properly registering as well.  In any event I am able to run both 2019 and the beta at this time.
Aubrey Lin @Appeon 24 May, 2021
#18
Hi Matt,

Thanks for the feedback and the information provided.

For the issue of R3 IDE not working:
According to the phenomenon described, if it prompted pbwsdlclient.dll, pbjdb.dll, pbjvm.dll, pbole.dll and pbmsoledsql.dll not registered when you installed PB 2021 Beta, then PB 2021 Beta IDE should be the one not running correctly, not PB 2019 R3 IDE. Our engineer is hoping that we can check it out on the problematic machine to locate the issue. Can you try if you can reproduce the issue with the "pbwsdlclient.dll, pbjdb.dll, pbjvm.dll, pbole.dll and pbmsoledsql.dll" message and the R3 IDE not working? It would be the best if the issue can be reproduced on a virtual machine so that you can take some snapshots of the scenarios below and provide the virtual machine for our engineer.
1. Before install any PowerBuilder products.
2. After install PowerBuilder 2019 R3 2703.
3. After install PowerBuilder 2021 Beta with PowerBuilder 2019 R3 2703 already existed.


For the issue of cannot load pbsys.dll:
It seems like pbsys.dll cannot be loaded because it was blocked by Carbon Black. Can you try storing/releasing pbsys.dll from quarantine and then run PowerBuilder 2019 R3 MR IDE again and see if the issue perists?

Regards,
Aubrey
Chris Pollach @Appeon 21 May, 2021
#17
Thanks Matt .. good to know. Worthwhile checking in with them though on why the AV is flagging this.

I the mean-time, let's see what Support/Engineering says.
Matt Balent 21 May, 2021
#16
Carbon Black is the antivirus.
Chris Pollach @Appeon 21 May, 2021
#15
Hi Matt;

   Ahhh .. that would do it! I wonder why though that a "pbshr190.dll" would work in case of PB 2019 GA/R2 and the same DLL without the 190 suffix is flagged? You might want to check with your operations support team at Concentra.

  BTW: This DLL does a lot of the "C" calls to the O/S on behalf of the PBRT.

  What Anti-Virus software is it that you using?

Regards ... Chris
Matt Balent 21 May, 2021
#14
Just noticed I'm getting this from the corporate anti-virus on my machine.

Threats Blocked
APC is known malware and was blocked (load)
c:\program files (x86)\appeon\powerbuilder\runtime 19.2.0.2703\pbshr.dll
Chris Pollach @Appeon 19 May, 2021
#13
Bummer! Let's see what the main support guys say about this.  :-(
Matt Balent 19 May, 2021
#12
No, there were no pb2021 artifacts left (either files or registry entries I found).  PB2019 R3 IDE does not run.  PB2021 IDE does run.
Chris Pollach @Appeon 19 May, 2021
#11
Hi Matt;

  Sounds like you still had parts of PB/PS2021 Beta on your system.

  Are the PB2021 Beta and PB2019R3 IDE's working OK now?

Regards ... Chris
Matt Balent 19 May, 2021
#10
Reloaded Beta and PB2021 comes up fine. ;)
Chris Pollach @Appeon 19 May, 2021
#9
Hi Matt;

  Thank you for trying that last step. That is the end of my suggestions. Sounds like the PB R3 installation is not yet 100%.

  I will now transfer this ticket over to the main Support / Engineering team for their review & suggestions on this re-installation not working scenario.

Regards ... Chris
Matt Balent 19 May, 2021
#8
I added those folders to my PATH but the IDE still will not start.  Still can't find pbsys.dll.
Chris Pollach @Appeon 19 May, 2021
#7
Thanks for checking on those registry entries!

Do you have your R3 files in your machine's *System* Path?

Here is what I have for R3 in my system path on my test PC's ...

C:\Program Files (x86)\Appeon2019\PowerBuilder 19.0\IDE;
C:\Program Files (x86)\Appeon2019\PowerBuilder 19.0\DotNET\bin;

HTH
Matt Balent 19 May, 2021
#6
They are all correct. (C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.2703)  However, there is no "pbsys.dll" in that location.
The PBSYS.DLL is in: c:\Program Files (x86)\Appeon\PowerBuilderCompiler 19.0 and in c:\Program Files (x86)\Appeon|PowerBuilder 19.0\IDE
Chris Pollach @Appeon 19 May, 2021
#5
Hi Matt;

  Can you check ....

"PowerBuilder Runtime" is always installed to %AppeonInstallPath%\Common\PowerBuilder\Runtime [version], for example, C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.2388 ("19.2" indicates 2019 R3); and its version number and installation directory are recorded in the system registry path:

The 32-bit apps in 32-bit OS search for this registry: HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\PowerBuilder Runtime

The 32-bit apps in 64-bit OS search for this registry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sybase\PowerBuilder Runtime

The 64-bit apps in 64-bit OS search for this registry: HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\PowerBuilder Runtime

  Please make sure that the registry entries above are pointing to where the PB runtime is actually located and is of the correct build.

Regards ... Chris
Matt Balent 19 May, 2021
#4
This happens when I attempt to launch the PowerBuilder IDE.
Chris Pollach @Appeon 19 May, 2021
#3
Hi Matt;

  Sounds like you were able to now install PB2019R3 and MR01. So that should bring you up to build 2703.

  Is this error happening in your PB App when running from the IDE, an EXE, or both?

Regards ... Chris
Matt Balent 19 May, 2021
#2
Cleared the registry and then re-installed the 2019 R3 MR but still the same error.  Can't load pbsys.dll.
Chris Pollach @Appeon 18 May, 2021
#1
Hi Matt;

   FWIW: I have PB2021 and PB2019R3 on a test machine. The new PB2021 beta messes up the R3 workspace and sometimes vice versa on my test PC. This looks like a new “beta” bug. This was not there in the PB2021 preview edition. Personally, I would not put any beta software on an R3 machine where you depend that other PB version to be 100% usable. Just my $0.02.


Regards … Chris
Matt Balent 18 May, 2021
*Phenomenon: cannot run PB after installing Beta 2021 then uninstalling both Beta and PB2019R3 and reinstalling PB2019 R3


*Reproduce Steps:


Remarks: During installation received dialog that pbwsdlclient.dll, pbjdb.dll, pbjvm.dll, pbole.dll and pbmsoledsql.dll "did not self-register or unregister'
OS:
Windows 10
Platform:
64-bit
Database Type:
SAP ASE
Database Version:
15