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

Resolved Application failed to start - PB2019

  1. Issue
0
Votes
Undo
  1. Tom Mangano
    Tom Mangano
  2. Beta Testing
  3. Tuesday, 9 April 2019 13:55 PM UTC

because i have PB 2019 installed on my PC, the executable runs as expected.

build is 64 bit platform.

i'm doing this for testing only.

i created PBCLTRT190.msi using the runtime packager.

got this warning

file was created

here's the file

 

installation was on Win10 Pro

instead of installing to the default path, i installed in the folder where my application runs (c:\VS7\)

when i double-clicked on the EXE file i got the following error message

suggestions?

 

 

Native Functions Return Zero
PB2019R2 - how to initialise ribbonbar control
Responses (4)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 9 April 2019 15:48 PM UTC
  2. Beta Testing
  3. # 1

Hi Tom;

   The PB "Packager" utility "assumes" that a) the .Net 4.0 (or later) run-time framework is installed and b) the VS2010 C++ redistributable run-time is already installed on your target deployment PC. If not for "B", you will need to either manually install this from MSDN or copy the following DLL's from the "PB2019" Shared folder ...

msvcp100.dll
msvcr100.dll
atl100.dll

  You may also need to manually copy the "nlwnsck.dll" file as well as the LIBxxx190 DLL's have a dependency on this Microsoft DLL.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Tom Mangano
Tom Mangano Accepted Answer Pending Moderation
  1. Tuesday, 9 April 2019 20:46 PM UTC
  2. Beta Testing
  3. # 2

hello Chris,

Thanks for the quick response.  i have one problem.  i searched my entire C drive and cannot fine any LIB*190 dlls

there are 24 lib* dlls under Appeon which i moved to the test pc.  no help

Tom M

Comment
There are no comments made yet.
Tom Mangano
Tom Mangano Accepted Answer Pending Moderation
  1. Wednesday, 10 April 2019 12:32 PM UTC
  2. Beta Testing
  3. # 3

good morning Chris,

Problem solved.

as stated in my original post, i compiled the app as 64 bit. 

if you look at the run time packager screen shots, you'll see it created the MSI as a 32 bit.

i compiled the app as 32 bit and installed both on a virgin Win10 Pro pc.

works fine.

thanks for the help,

Tom

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 10 April 2019 14:27 PM UTC
Hi Tom;

Excellent news!

Yes, your initial post said a "64 bit platform" not a "64 bit App" - so I ass-u-me'd that you meant a 64bit O/S. That is why I did not challenge the packager screen shots. ;-)

Regards ... Chris
  1. Helpful
There are no comments made yet.
Gordon Weil
Gordon Weil Accepted Answer Pending Moderation
  1. Tuesday, 22 October 2019 15:46 PM UTC
  2. Beta Testing
  3. # 4

I've learned a lot about .msm files and PB 2019 installation files, but mostly I learned that I am a bonehead. I accidentally included some PB 2017 .PBD files in my installation. When I replaced them with the PB 2019 .PBD files it worked fine.

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.