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

Resolved PowerBuilder Runtime Deployment

  1. How-to
0
Votes
Undo
  1. Thomas Rolseth
    Thomas Rolseth
  2. PowerBuilder
  3. Tuesday, 25 May 2021 13:38 PM UTC

We are migrating an application using Oracle from PB9 to PB 2019 R3 build 2703.  They have a test version of the application that users can launch directly from a network share via a batch file that is called from a shortcut.  I created a new folder on the network and put a new R3 build there along with all supporting files and the runtime.  

When I run the application I get the attached error.  I'm certain this is due to runtime path specified in the xml file that gets created as part of the build process now.  The PB help (see below) talks about how to set the path.  I've tried several different ways but none of them work.  How do you set this correctly given that the exe is launched from a network share similar to the following?

\\server\vol1\INST\Test_UAT.bat

The batch file launches the exe that is in the INST folder.  At the moment, the runtime files are in their own folder:

\\server\vol1\INST\Runtime

I've also tried it with the runtime co-mingled with the exe and PBDs and have deleted the the xml.  Unfortunately it always tries to find the PBVM.dll file but never does.

 

From PB Help:

For example, if the "Runtime" folder is in the same folder as the executable file:

<RuntimePath>\Runtime\Runtime 19.2.0.2588</RuntimePath>

or if the "Runtime" folder is placed next to the folder which contains the executable file:

<RuntimePath>..\Runtime\Runtime 19.2.0.2588</RuntimePath>


Thanks, Tom
Attachments (1)
pbvm_error.JPG pbvm_error.JPG
  1. Deployment
  2. PowerBuilder (Appeon)
  3. Runtime Packager
  4. PowerBuilder Runtime
How to Create External Datawindow dynamically with...
Extract all source code from a workspace
Responses (11)
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Thursday, 10 June 2021 02:15 AM UTC
  2. PowerBuilder
  3. # 1

Hi Thomas,

 

As far as I know, another customer reported this issue to Carbon Black and Carbon Black has recently marked PB 2019 R3 2703 pbshr.dll as 0 threat.

 

So I suggest you can update Carbon Black on both the Client and the Server first and then copy an original pbshr.dll to the server again and see if it works

 

Regards,

Ken

Comment
There are no comments made yet.
Thomas Rolseth
Thomas Rolseth Accepted Answer Pending Moderation
  1. Thursday, 3 June 2021 16:07 PM UTC
  2. PowerBuilder
  3. # 2

Zip error with pbshr.dll 

Attachments (1)
pbshr_dll_zip_error.JPG pbshr_dll_zip_error.JPG
Comment
There are no comments made yet.
Thomas Rolseth
Thomas Rolseth Accepted Answer Pending Moderation
  1. Thursday, 3 June 2021 16:07 PM UTC
  2. PowerBuilder
  3. # 3

AV error message

Attachments (1)
CbDefense_warning.JPG CbDefense_warning.JPG
Comment
Ken Guo @Appeon
  1. Ken Guo @Appeon
  2. Friday, 4 June 2021 02:47 AM UTC
Hi Thomas,



From the screenshot you provided, it’s Carbon Black that blocked or corrupted the pbshr.dll file.

I suggest:

1. Please contact Carbon Black to file an appeal. The pbshr.dll file has a valid signature certification and has passed our rigorous security tests where each Appeon PowerBuilder product has to pass the tests of over a dozen of mainstream antivirus software before released to the public, such as Norton, Bitdefender, Kaspersky, McAfee, AVG, and so on.

2. If the pbshr.dll on the network share has been locked up, it’s suggested that you delete the file first via Carbon Black then copy the original pbshr.dll file to the network share again and you would also need to add it to Carbon Black’s whitelist.



Regards,

Ken
  1. Helpful
There are no comments made yet.
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Thursday, 3 June 2021 06:40 AM UTC
  2. PowerBuilder
  3. # 4

Hi Thomas,

From the information you provided, something might have happened to pbshr.dll file or it might be corrupted by the security software.

I suggest that you contact IT, copy the original pbshr.dll file from the Develop machine again, and add it to the security software’s exception/whitelist list.

Also, please help provide the following information:

  1. Which security software are you using?
  2. Did everything go well during the process of installing PB 2019R3 MR 2703?
  3. Did any security software quarantine or intercept this pbshr.dll file?
  4. Please help provide the pbshr.dll file that doesn’t have the digital signature.

The correct pbshr.dll file properties should display as below:

 

 

Regards,

Ken

Comment
Thomas Rolseth
  1. Thomas Rolseth
  2. Thursday, 3 June 2021 16:06 PM UTC
Ken,

Here are answers to your questions:

1) There is no AV on the Amazon Workspace VM I am using for PB development. The client uses Carbon Black (cbDefense) for their users/employess. I suspect it is also in use on the network share

2) Yes

3) See the CbDefense_warning attachment that I have included to this thread

4) I tried to zip the pbshr.dll file that I copied to their network share from where it was located after installing PB 2019 R3 (i.e. Common\PowerBuilder\Runtime 19.2.0.2703). This is the one that has lost it's digital signature. Trying to zip it caused an error -- see attached. Copying this dll to any location on their network seems to alter it somehow
  1. Helpful
There are no comments made yet.
Thomas Rolseth
Thomas Rolseth Accepted Answer Pending Moderation
  1. Wednesday, 2 June 2021 21:14 PM UTC
  2. PowerBuilder
  3. # 5

Here is an image showing how the digital signature is there for pbrth.dll but not pbshr.dll

Attachments (1)
pbshr2.JPG pbshr2.JPG
Comment
There are no comments made yet.
Thomas Rolseth
Thomas Rolseth Accepted Answer Pending Moderation
  1. Wednesday, 2 June 2021 21:04 PM UTC
  2. PowerBuilder
  3. # 6

screen shot of file copy for pbshr.dll

Attachments (1)
pbshr.JPG pbshr.JPG
Comment
There are no comments made yet.
Thomas Rolseth
Thomas Rolseth Accepted Answer Pending Moderation
  1. Friday, 28 May 2021 13:52 PM UTC
  2. PowerBuilder
  3. # 7

Ken, 

Thanks for you suggestions.  I performed steps 1 through 4 (regarding #1, the exe and runtime is 32bit) and am still getting the same error.  Attached is the error message which shows the mapped drive from the network where I am running the application from.

Tom

Attachments (1)
pbvm.JPG pbvm.JPG
Comment
Ken Guo @Appeon
  1. Ken Guo @Appeon
  2. Monday, 31 May 2021 02:33 AM UTC
Hi Thomas,



If you copy the folder Z:\TTBBUAT to C:\ to run, does it work well? If it works then the issue exists in the network path only.

If it doesn’t work in C:\ either, then please check if your Runtime files are correct.



Also, I notice that you mentioned the exception with pbshr.dll previously, I suggest that you check if any security software quarantines or intercepts the use of this pbshr.dll file.



If the issue is still not solved, I suggest that you submit a ticket to the Appeon Support system and then we can schedule a remote debug meeting there.



Regards,

Ken
  1. Helpful
Thomas Rolseth
  1. Thomas Rolseth
  2. Wednesday, 2 June 2021 21:04 PM UTC
Ken,

When I try to copy the files (exe, pbd's, runtime, etc) from the network to a local folder it stops when it hits pbshr.dll. All other dll's are fine. We also noticed that when you look at the file properties of pbshr.dll where it is installed (C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.2703) there is a digital signature tab present. When you do the same thing for that file on the network share, that tab is not there. Attached to this thread is screenshot of the file copy I attempted from the network to a local drive (D:\Deploy)
  1. Helpful
There are no comments made yet.
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Friday, 28 May 2021 03:00 AM UTC
  2. PowerBuilder
  3. # 8

Hi Thomas,

 

I have verified locally and when I used the UNC path, it runs fine.

 

If the issue persists even after you copied all PB Runtime files to the directory where EXE resides, I think the issue is probably with the Runtime files.

 

I suggest that you:

1.  Re-deploy your application using PB 2019 R3 and it will generate PBD, EXE, and XML files. Please also help confirm whether you deploy the application in 32-bit or 64-bit.

2. Delete the XML file and then copy the PBD and EXE files to this server directory: \\server\vol1\INST.

3. Copy all the PB Runtime files (.\Appeon\Common\PowerBuilder\Runtime 19.2.0.2703\*.*) from the development machine to the server directory as well, that is copy all Runtime DLLs to the directory where EXE resides.

(Note: if your application is 64-bit, the PB Runtime DLLs you need to copy are in this directory: .\Appeon\Common\PowerBuilder\Runtime 19.2.0.2703\x64\*.*)

4. Run the EXE in \\server\vol1\INST directory and see if it works fine.

 

 

Regards,

 

Ken

Comment
There are no comments made yet.
Thomas Rolseth
Thomas Rolseth Accepted Answer Pending Moderation
  1. Tuesday, 25 May 2021 20:35 PM UTC
  2. PowerBuilder
  3. # 9

Below are the contents of the batch file.  The first line sets the path for ghostscript, the second is for Oracle and the third starts the app

SET PATH=%GS%\bin;%PATH%
SET PATH=C:\Oracle\product\12.1.0\client32\BIN;%PATH%
start \\server\inst\appname.exe

 

Comment
Load more comments
Thomas Rolseth
  1. Thomas Rolseth
  2. Wednesday, 26 May 2021 13:27 PM UTC
That's partly the problem/mystery -- I removed the xml file once I put the runtime the exe in the same folder.
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Wednesday, 26 May 2021 13:31 PM UTC
The xml file is only needed if the runtime dll files are not in the exe folder, 'App Paths', or system Path.
  1. Helpful
Thomas Rolseth
  1. Thomas Rolseth
  2. Thursday, 27 May 2021 20:45 PM UTC
Yeah, I'm not using the xml file. The exe, pbd's and runtime files are all mixed together in the same network folder. We just the client tell us that PBSHR.dll won't work with an application being run from a network share. Any truth to that? I haven't seen this so thought I would mention it to the appeon community. Thanks
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 25 May 2021 18:35 PM UTC
  2. PowerBuilder
  3. # 10

Hi Tom;

  Does the .BAT file add the actual PB runtime folder to the batch job's System Path before starting the PB App EXE?

Regards ... Chris

Comment
There are no comments made yet.
Thomas Rolseth
Thomas Rolseth Accepted Answer Pending Moderation
  1. Tuesday, 25 May 2021 14:46 PM UTC
  2. PowerBuilder
  3. # 11

Also I put all of the PB runtime folders into the same folder as the exe and removed the application xml file but still got the same error.

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.