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

Resolved built application will not start

  1. How-to
0
Votes
Undo
  1. Doyle Hagler
    Doyle Hagler
  2. PowerBuilder
  3. Monday, 27 April 2020 14:27 PM UTC

I am migrating from PB12 to PB19.  My application runs in development on PB19.  I built it and the built version runs on the development machine.  However if I move it (and all the runtime DLLs to another machine) I get the error "The application was unable to start correctly (0xc000007b)."

Any suggestions?

doyle

  1. Build
  2. PowerBuilder
Problems with Orcascript PB2019
Issues with Migration to PB 2019 R2
Responses (2)
Doyle Hagler
Doyle Hagler Accepted Answer Pending Moderation
  1. Monday, 27 April 2020 15:17 PM UTC
  2. PowerBuilder
  3. # 1

John,

Thanks for the suggestion.  I have been trying to avoid that, but it may be the only way.  These are government systems and their network people are very picky about what they install.

Could it have anything to do with the type of Appeon license  they purchased?  When I build the app on my development machine at the office and copy it to another machine it works fine.

doyle

 

Comment
Load more comments
Doyle Hagler
  1. Doyle Hagler
  2. Monday, 27 April 2020 17:54 PM UTC
I have built the app at both sites. The built EXE runs on the development machine at both sites so I don't think there is a problem with the build.

On my local network, I can copy the built app and the basic PowerBuilder DLLs from the Shared folder to a different machine and it runs fine.

In looking at it closer, it may be the Microsoft DLLS. I have them all based on the documentation, but the sizes are different. Maybe 32bit vs 64bit?
  1. Helpful
John Fauss
  1. John Fauss
  2. Monday, 27 April 2020 18:12 PM UTC
"One thing I notice when I start the developer at the clients office it appears to login to Appeon where at my office it doesn't do that."

Does "start the developer" mean when you start the PowerBuilder IDE? If the development machine at the client's site is using an Offline License, then this is normal as PB has to verify the license every time the IDE starts. It does this by checking in with the Appeon license server via the web. I suspect your version of the PB IDE at your local office is NOT using the Offline license model.

Mike's suggestions are good ones. I agree it is likely the client's machine where you are attempting to run the compiled PB 2019 application is missing one or more Microsoft DLL's.
  1. Helpful
Doyle Hagler
  1. Doyle Hagler
  2. Monday, 27 April 2020 18:18 PM UTC
Thanks to both of you. I am checking all the DLLs and will try it again.
  1. Helpful
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Monday, 27 April 2020 14:51 PM UTC
  2. PowerBuilder
  3. # 2

Greetings, Doyle -

Probably one or more missing DLL's and/or support files. Quite a few things have changed since PB12. Did you use the PB Runtime Packager utility to assemble all of the runtime DLL's? If not, I suggest you try that. In the packager wizard, un-check any features not utilized by your application, build the install package, then test the deployment. If it works, you'll have all of the files needed to deploy.

Regards, John

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.