1. Rick Domogalik
  2. PowerBuilder
  3. Thursday, 20 February 2020 15:53 PM UTC

I am getting the following error on 2 workstations while trying the install my PowerBuilder application.

"The application was unable to start correctly (0xc000007b).  Click OK to close the application."

My assumption is this is a x64 versus x32 issue.  I have successfully deployed this application to around 40 other workstations with just 2 having this issue.  I created a runtime package for 32bit.  It works fine on the 40, but these 2 kick this error.  I have tried removing the runtime files and reinstalling, no luck.  I have fully patched both machines, same issue.  I have reinstalled the .NET framework.  I have done multiple reboots.  

So all the usual fixes for this error seem to not be working.  I have identical workstations with identical hardware and software installs to these 2 machines that took the application install with no issues.  Really scratching my head as to what the issue could be.  The two workstations are about 2 years apart in age, so no commonality between them as to why they would both have this issue.

 

Any insight from others who have seen this issue on an application deployment would be greatly appreciated.

 

Rick

Accepted Answer
Rick Domogalik Accepted Answer Pending Moderation
  1. Friday, 21 February 2020 19:27 PM UTC
  2. PowerBuilder
  3. # Permalink

OK.  So I was able to figure out what the issue was.  Turns out the 2 computers in question had the basic intel chipset driver installed.  After updating the chipset driver to the motherboard specific driver, all started working.

 

Thanks for all the suggestions.

 

 

Rick

Comment
  1. Michael Kramer
  2. Friday, 21 February 2020 19:39 PM UTC
Kudos, you solved it! Thx for sharing.
  1. Helpful
There are no comments made yet.
Rick Domogalik Accepted Answer Pending Moderation
  1. Thursday, 20 February 2020 20:01 PM UTC
  2. PowerBuilder
  3. # 1

So I have went through and reinstalled:

Visual C++ redistributables

Reinstalled .NET 4.8

updated and installed DirectX 

Tried to clean boot with minimal windows only drivers loaded using msconfig

Ran the scandisk - no errors on the drive.

 

Totally at a loss as to what the issue could be.  The windows logs just log the aforementioned error.  Nothing further.  I also watched in process monitor, nothing odd there either.  Running as administrator has no change to the outcome.  

The only install for this software is the PowerBuilder runtime package.  It installs with no error.  The error only fires when I try to launch my powerbuilder app.  Baffling that it works on over 40 similar if not identical workstations to the 2 that it wont load on.  

 

 

Comment
  1. Miguel Leeuwe
  2. Thursday, 20 February 2020 21:03 PM UTC
have you tried using a registry cleaner?
  1. Helpful
  1. Rick Domogalik
  2. Friday, 21 February 2020 14:12 PM UTC
I tried the /pbdebug. Does this put a log somewhere or will it pop up with debug info at runtime? After running it, I saw no more info displayed on the screen, just the normal oxc000007b error.
  1. Helpful
  1. Rick Domogalik
  2. Friday, 21 February 2020 14:13 PM UTC
I have also disabled antivirus on this machine, but I have also successfully installed it on other machines with the same AV running. We use Cylance. And I have always been leery of reg cleaners. They seem very intrusive from a security standpoint.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Thursday, 20 February 2020 19:15 PM UTC
  2. PowerBuilder
  3. # 2

Run the install, wait for the crash and then check the windows event log, maybe you can get some information where the crash is coming from

MS advice: run "sfc /scannow" (yes I know it's a joke, but it won't harm to try)

run "process monitor" from sysinternals and see if that sheds any light.

 Have you tried running the install "as administrator"?

my 2cts

Comment
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 20 February 2020 16:37 PM UTC
  2. PowerBuilder
  3. # 3

Google search indicates Windows error 0xc000007b might be a problem with .NET framework, and this video walks you through troubleshooting the issue: https://www.youtube.com/watch?v=JxAnWhjyNlo

There are also troubleshooting steps from Microsoft MVP here that I think you should try doing carefully: https://answers.microsoft.com/en-us/windows/forum/all/0xc000007b-error-on-windows-10-when-starting-games/7fe1efc9-ede9-4a48-9eb0-33aec12fa0a7 

I wonder if it will be less effort/time to simply wipe those hard drives clean and do fresh install of Windows and then your PowerBuilder app?

Comment
  1. mike S
  2. Thursday, 20 February 2020 19:55 PM UTC
he was suggesting to wipe/reinstall windows on a user's workstation, not a developers workstation. makes sense if it is a simple workstation install vs trying to figure out some obscure bug with something like an outdated driver installed on 2 machines.
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Thursday, 20 February 2020 20:34 PM UTC
Yes, I was talking about the user machine, and many of our customers have default images they can quickly roll out. Just keeping an open mind and throwing out options!
  1. Helpful
  1. Miguel Leeuwe
  2. Thursday, 20 February 2020 20:59 PM UTC
yes okay Mike and Armeen, but I think more options could have been mentioned. Sadly mine have not given any more information, so yes.... maybe a full reinstall might be the only solution. Upvoted again :)
  1. Helpful
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.