Hi Larry;

   When you state "will not run" ... what are the symptoms / observations?

Regards ... Chris

Sorry. Same old "The application was unable to start correctly (0xc000007b)..."

Dis the Packager trick as well (32-bit because app is 32-bit).

What about a simple "Hello World" PB App on the PC's that will not run the main App?

"Added 32-bit runtime DLLs"

Did you add all the required run-times - specifically the microsoft ones that might already exist on more standard windows installs?  such as msvcr100.dll?  (not 100% sure of the msvcr version used by 2019)

Yup. All msvcrxxx.dlls are installed. It requires msvrc80.dll I think.

This error usually is associated with a bitness issue. It is likely trying to load a DLL that is 64 bit (as you have indicated that the PB app is 32 bit).

I would suggest running process monitor ( from MS Sysinternals) to determine what the PB application is trying to load making sure that each DLL that PB is trying to load is 32 bit.  Because that tool can be quite verbose, you will want to start with the simplest app that shows the issue. 

Chris, I built a 32-bit 'Hello World" executable. PBL built into the exe. BOOM! Same thing. Has to be a runtime or system file missing.

What anti-virus software is included in your image?

Any other / older runtimes installed at the same time on these pc's?

Download this tool, it will tell you what DLL files your app uses. If you do this on one of the computers that work, you can make sure they are all present on the ones that fail.

https://docs.microsoft.com/en-us/sysinternals/downloads/listdlls

Run your app then in a DOS command window run the command:

listdlls yourexename > listdlls.txt

Open listdlls.txt in a text editor.

Larry,

Just going to throw my two cents in here.

Not sure if you have ever used Dependency Walker, but if you install this on a machine that is working, and on the machine that isn't, and select the executable on each machine, you should see all the DLL's that it is associated with.

http://www.dependencywalker.com/

98% of the time you'll pretty quickly see what DLL is available on one machine and not available on the other.  (Or it may be available on both, but outside the defined paths on your computer)

Let me know if you have any questions on this.

Thanks!

Jeff Gibson
Intercept Solutions
Nashville, TN

What about C++ Runtime and .Net Framework?

Thanks to all who replied. By using Depends22 and ListDLLs, I was able to discover that ATL100.DLL was not installed on the company-imaged Win10 PCs. It was already on the Dell-imaged-out-of-the-box PCs. Seems our network folks deemed it not needed. In Windows/SysWOW64.

Any recommendation on  POWERGEN (https://www.ecrane.com/index.php/features) to generate PBL? 

If you type "runtime files" into the PB2019R2, b2358 HELP file, this is the page that comes up. It shows every DLL required, including the MS DLLs.

Naturally, the HELP file is formatted, but the formatting is lost here.


Olan

========================================


PowerBuilder runtime files
Prev  Deploying Applications and Components  Next

--------------------------------------------------------------------------------

PowerBuilder runtime files
Database connectivity
Files required for database connectivity are listed separately in Database connections.

Download PowerBuilder runtime files
To help developer conveniently get all of the required runtime files, Appeon provides the different versions of runtime files as zip packages on the site: https://www.appeon.com/developers/get-help/knowledgebase-for-pb. You can download the runtime files starting from version 2017 R2. For example, the download link for version 2019 is https://www.appeon.com/developers/get-help/knowledgebase/powerbuilder-runtime-files-2019-2082.html.

Core runtime files

The following table lists the core PowerBuilder runtime files.


Name
 Required for
 
pbvm190.dll
 All.
 
pbshr190.dll
 All. pbvm190.dll has dependencies on this file.
 
libjcc.dll
 All. pbvm190.dll has dependencies on this file.
 
libsybunic.dll
 All. pbvm190.dll has dependencies on this file.
 
libjutils.dll
 All. libjcc.dll has dependencies on this file.
 
libjtml.dll
 All. libjcc.dll has dependencies on this file.
 
nlwnsck.dll
 All. libjcc.dll has dependencies on this file.
 
pbuis190.dll
 All. pbvm190.dll has dependencies on this file.
 
pbdwe190.dll
 DataWindows and DataStores.
 
pbsysfunc190.dll
 System functions.
 
pbresource190.dll
 PowerBuilder resource file.
 



Microsoft files

When you deploy the core PowerBuilder runtime files, you must also deploy the msvcr100.dll and msvcp100.dll Microsoft Visual C++ runtime libraries and the Microsoft .NET Active Template Library (ATL) module atl100.dll, if they are not present on the user's computer. The PowerBuilder runtime files have a runtime dependency on these files. See Third-party components and deployment for more information.

Additional runtime files

The following table lists additional runtime files that your application might not require. For example, pbvm190.dll is required for all deployed applications, but pbrtc190.dll and its associated runtime files are required only if your application uses Rich Text controls or RichText DataWindow objects.

For more information about deploying applications that use the pbjvm190.dll for Java support, see Java support.


Name
 Required for
 
pbacc190.dll
 Accessibility support (Section 508)
 
pbdpl190.dll
 Data pipeline support
 
PBDWExcel12Interop190.dll, Sybase.PowerBuilder.DataWindow.Excel12.dll
 Excel 2007 support
 
PBXerces190.dll, xerces-c_2_8.dll, xerces-depdom_2_8.dll
 XML Web DataWindow support and XML support for DataWindows and DataStores
 
Sybase.PowerBuilder.WebService.Runtime.dll, Sybase.PowerBuilder.WebService.RuntimeRemoteLoader.dll, Sybase.PowerBuilder.WebService.WSDL.dll, Sybase.PowerBuilder.WebService.WSDLRemoteLoader.dll,
 Web service DataWindows (Obsolete)
 
pbjvm190.dll
 Java support
 
pbrth190.dll
 ADO.NET
 
For 32-bit:

pbrtc190.dll, PBTCTEXT190.dll, TER25.dll, WRS9.dll, spell32.dll, PDC32.dll, WRW9.dll, HTS20.DLL, ssts.dll, SSGP.dll, TXML2.dll

For 64-bit:

pbrtc190.dll
 Rich text support with TE Edit Control
 
For 32-bit:

pbrtc190.dll, PBTXTEXT190.dll, podofo.dll, tp4ole15.ocx, tp15.dll, tp15_bmp.flt, tp15_css.dll, tp15_doc.dll, tp15_dox.dll, tp15_gif.flt, tp15_htm.dll, tp15_ic.dll, tp15_ic.ini, tp15_jpg.flt, tp15_obj.dll, tp15_pdf.dll, tp15_png.flt, tp15_rtf.dll, tp15_tif.flt, tp15_tls.dll, tp15_wmf.flt, tp15_wnd.dll

For 64-bit:

pbrtc190.dll
 Rich text support with the OEM version of TX Text Control
 
pblab190.ini
 Label DataWindow presentation-style predefined formats
 
pbtra190.dll, pbtrs190.dll
 Database connection tracing
 
pbpdf190.dll
 Saving DataWindows as PDF files using the NativePDF! method
 
pbCSI190.dll
 Encryption and decryption
 
pbodw190.dll, pbodt190.dll, Sybase.PowerBuilder.DataSource.OData.dll, Sybase.PowerBuilder.ODataClient.dll, Sybase.PowerBuilder.ODataWrapper.dll
 OData database interface
 
pbjson190.dll, pbhttpclient190.dll, pbrestclient190.dll
 JSON data exchange and RESTful Web APIs
 
For 32-bit:

pbcrypt190.dll, libcrypto-1_1.dll

For 64-bit:

pbcrypt190.dll, libcrypto-1_1-x64.dll
 Data encoding and encryption
 
pboauth190.dll
 OAuth 2.0 support
 
pbcompression190.dll
 Compression capability
 
pbtheme190.dll, pbjson190.dll (and "theme190" folder)
 UI theme support

("theme190" folder must be manually copied from the "%Appeon%\Shared\PowerBuilder" directory )
 
pbjwt190.dll
 JSON Web Token support
 
PBRibbonBar190.dll
 RibbonBar control support
 
PBDotNet190.dll, PBDotNetFrameworkInvoker190.dll, PBDotNetCoreInvoker190.dll
 .NET class support
 
pbwebbrowser190.dll (and its dependent DLLs: chrome_elf.dll, d3dcompiler_43.dll, d3dcompiler_47.dll, libEGL.dll, libGLESv2.dll, libcef.dll, swiftshader/libEGL.dll, swiftshader/libGLESv2.dll) (and "pbcef190" folder)
 WebBrowser control support

("pbcef190" folder will be automatically copied)
 



Installed path

\%Appeon%\Shared\PowerBuilder.

The Sybase DLLs are installed to \%Appeon%\PowerBuilder 19.0\DotNET\bin.

Deployment path

Same directory as the application, in a directory on the system path, or in the App Path registry key.

Registry entries

See App Path registry key.

Localized runtime files

Localized runtime files are provided for French, German, Italian, Spanish, Dutch, Danish, Norwegian, and Swedish. These files are usually available shortly after the general release of a new version of PowerBuilder. The localized runtime files let you deploy PowerBuilder applications with standard runtime dialog boxes in the local language. They handle language-specific data when the application runs.

For more information, see Localizing the product.


--------------------------------------------------------------------------------
Prev  Up  Next
Software used for SOAP clients for Web services (Obsolete)  Home  Database connections