Powerbuilder 12.6 error with PBSHR126.DLL

[Former Member]

When I include PBSHR126.dll with my application to deploy, I get an error when I try and run the application.

PBSHR126.DLL is either not designed to run on Windows or it contains an error.

How do I remedy this?  There is very little documentation on 12.6 as it is, so any info would be appreciated.

[Former Member]

Hi Chris;

  FYI: You can get this problem if you ...

a) Package the wrong version of the PBSHR126.DLL

b) There are two or more versions of PBSHR126.DLL on the target PC.

c) Other supporting run time DLL's are not present for PBSHR126.DLL to run.

    => See PB Help & search on the keyword "Deployment".

BTW:

1) Is this for PB Classic or PB.Net?

2) What type of EXE are you building?

    .Net, P-Code, M-Code, etc

HTH

Regards ... Chris

[Former Member]

The packager really has nothing to do with the problem with PBSHR126.DLL.

The original poster needs to give more information other than 'I get an error'.

[CobyKako]

Hello,

I recommend using the PowerBuilder Runtime Packager tool to bundle your runtime files in a .msi file.

Then you only install the msi file in each target computer.

pbpack126.exe is the name of the tool.

HTH,

Jacob

[Former Member]

Hi Jacob;

  The run-time PB v12.6 packager is always disabled when I launch it  - whether it is installed on W7 or W10 machine.  

Have you seen this before?

Regards ... Chris

[CobyKako]

Hi Chris,

I just successfully tested it on Windows Server 2008

[Former Member]

Any testing on W7 or W10 64 bit recently using the latest EBF's (which is what I am using currently)?

The entire dialog is always completely disabled.  

[CobyKako]

Tested with build 4088 on Win7 64bit: Runtime Packager tool works.

[Former Member]

FYI ... this is all I get!!!  

Any thoughts on why its disabled?

( I have never seen this before and its happening on three different unrelated PC's as well! )

[Former Member]

There is something very wrong with the latest packager as well. Even if you press the CREATE button, the packager errors, as follows:

Why is it looking for LIBJCC.dll in the MS-Windows System32 path when a) it is never installed there and b) the Libjcc.dll is in the "Shared" PB folder which is in my System Path (triple checked that)?

[former_member202249]

Chris,

I see what you're seeing too on my Windows 8.1 machine with the latest EBF build 4088. 

If I click around to the other options, I see a few options enabled but when I try to actually create the msi I get errors   For me, it's looking in c:\windows\system32 for either libjcc.dll or apache_license.txt.   If you click the 64 bit and .NET radio buttons and then try to create the msi, is that what you see? 

I'm looking into it.

Pat

[former_member202249]

Looks like you are seeing what I'm seeing!

Looking into it.

Pat

[Former Member]

Exactly the behaviour that I see as well Pat.  

Thanks for looking into that issue!  

[former_member202249]

Chris,

I uninstalled PB 12.6 and then reinstalled, runtime packager was correct and enabled.  I then just applied the latest EBF, build 4088 and it looks correct also.  So not sure if it was something caused by upgrading to another EBF or not but see if that works for you.  I also made sure on both autorun.exe to initially install and then setup.exe with the EBF, that I right clicked and ran as administrator.  It looks OK to me now and does build the msi . I was seeing exactly what you were seeing earlier.

Pat 

[Former Member]

Hi Pat;

FYI: I uninstalled PB v12.6, rebooted and then installed GA again. The packager is still completely disabled here on my W7 PC.  

Note1: I did not reinstall the .Net prerequisites again .. did you?

Note2: My PC has both PB v12.1 and 12.5.1 installed on it as well.

Regards ... Chris

[former_member202249]

Chris,

I did not reinstall the .Net prerequisites as I knew they were already on my laptop.   Did you right click and run both installs as administrator? 

I have many versions of PB on this machine.  Are the runtime packagers for your other versions enabled?

Let me see if I can find a Windows 7 machine. 

Pat

[Former Member]

=>  Are the runtime packagers for your other versions enabled?

A: No, they are now all disabled after PB v12.6 is loaded!   

[former_member202249]

Chris,

Are you running from explorer, clicking on pbpack126.exe or from the Start menu?  

Pat

[Former Member]

OMG ... it works from the Start Menu link!

Thanks $1M ... <more coffee>!  

[Former Member]

FYI: Reapplied the v12.6 EBF and the Packager is still OK. 

Looks like you need a short-cut to run the Packager as it needs to know the proper starting directory.  Otherwise it assumes its working out of the System32 folder and cannot run properly. 

[Former Member]

The problem ended up being Visual Studio was corrupting the DLL's.  Thx for all the input

[Former Member]

Interesting, but that makes no sense to me as PB Classic has no dependance on VS.

[Former Member]

We were keeping our source in VS.  Keyword expansion setting in VS was stripping out part of the header of the DLL and was rendering them invalid.

[Former Member]

Ahh ... so not really VS ... TFS related then?

[Former Member]

Visual Sourcesafe was causing the issue, so it was not anything related to Powerbuilder

[Former Member]

Wow ... you guys still using that EOL'ed & deprecated product ...  OMG!   

FWIW: I have used VSS in many of my Canadian Government clients with PB and never had any such issues. In fact, it was probably the best & most consistently stable SCM in use in the late 1990's thru 2000's!