1. Kelly Amott
  2. PowerBuilder
  3. Thursday, 30 January 2020 18:08 PM UTC

I have an app that I recently migrated to PB 19. It tested fine after the build. I needed to create a new project file in order to run the deployment. Following deployment and with a new executable the app launches but fails at the login step. I'm just getting started with the app so I'm not familiar with the debugging.

Ideas? Guidance? What would deployment have broken or what needs to be activated?

Thanks.

Kelly Amott Accepted Answer Pending Moderation
  1. Monday, 10 February 2020 21:34 PM UTC
  2. PowerBuilder
  3. # 1

Adding a new development. I now have three apps that I have migrated. I was able to get a good deployment out of one of them but for the other two the new wrinkle I am running into when I try to deploy is that it creates an executable but when I attempt to execute I get this error - 

I close the window, refresh, and my executable is gone. When I attempt to redeploy using the same executable name I get this error - 

I checked in the registry and there were entries for the .exe which I deleted but it's caching the name somewhere where I can't reuse it. I've checked and I don't see anything running as that.

Comment
  1. Kelly Amott
  2. Monday, 10 February 2020 22:56 PM UTC
I figured I'd close the IDE and run it. Prior to running I thought I'd take a look at the properties. While I was looking at the properties the file disappeared. ??

1. P-Code

2. 32-bit

3. Classic is enabled

4. Never got the chance.



I redeployed and then attempted to run the project from the IDE. I got the pop-up error "Error launching...Check if the application executable file exists and it is a valid executable file." BUT....I did then look in the folder and the executable is there. I didn't try anything funny but just clicked and ran as admin and it launched. Tried to modify permissions and was able.

One of the previous executables reappeared. I had also made a copy of one of them before doing anything and before it disappeared. I tried renaming it to the original executable name and it says that file already exists. So...even though I'm not hiding files they are hiding from me. Super bizarre.

Time to start fresh. What are the recommendations for items 1 and 3?



  1. Helpful
  1. Chris Pollach @Appeon
  2. Tuesday, 11 February 2020 19:04 PM UTC
Hi Kelly;

For #3, unless you really, really need 3D objects. I would turn that off.

The next suggestion ... make sure that the main App's work folder and all sub-folders and files are NOT write protected.

Regards ... Chris

  1. Helpful
  1. Kelly Amott
  2. Wednesday, 12 February 2020 16:05 PM UTC
Turns out it's corporate security. As quickly as the exe was created it was quarantined. Half an hour later it's released to the general population. Closing this question. Thanks for all the guidance. Next step - creating an install package.
  1. Helpful
There are no comments made yet.
Kelly Amott Accepted Answer Pending Moderation
  1. Thursday, 30 January 2020 18:32 PM UTC
  2. PowerBuilder
  3. # 2

Hi Michael. Thanks for the reply.

I'm testing from the same machine where I did the migration and deployment. Same folder as well.

I'm connecting to an Oracle 8 instance. I had no issues connecting until the deployment. I created a copy of the folder before I ran the deployment. I'm going to step through the whole process again to see if I missed something.

Found the Run-time Packager. Will try it.

Comment
  1. Kelly Amott
  2. Monday, 3 February 2020 17:43 PM UTC
Update: I dug around and found a version of the code with an existing .pbt and I was able to run a migration. Post-migration I'm getting the login failure. No errors in the migration but plenty of warnings. My last application I migrated connects to an Oracle 9.2 DB and it is working fine. Trying to figure out the debugger so I can find why the new app is failing at login.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 3 February 2020 19:38 PM UTC
Hi Kelly ...

1) Migration would be automatic when you attached the WorkSpace & Target from PB 8 to the PB 2019 IDE. It would have prompted you for a migration and then proceeded if you replied "OK".

2) The PB2019 debugger is basically the same as PB8. While the icons are updated, they are still basically the same - just modernized

Regards ... Chris.
  1. Helpful
  1. Kelly Amott
  2. Tuesday, 4 February 2020 20:17 PM UTC
Figured out the debugger. Found that the app had been hard-coded to Oracle 8 in more than a dozen places. When I changed it to Oracle 9 I was able to get logged on to the app. Somewhere down the line that has to be rectified but for now I have a working migrated app. Once I've done UAT with Oracle 9 I'll need to repeat the exercise for 12c. Hopefully they sunset the app before we upgrade databases again. (I was looking at the comments and this app was written pre-1995. It was testing for machine names in Windows for Workgroups.)
  1. Helpful
There are no comments made yet.
Michael Kramer Accepted Answer Pending Moderation
  1. Thursday, 30 January 2020 18:21 PM UTC
  2. PowerBuilder
  3. # 3

I wonder if you have deployed the full set of required runtime files. When you run from PowerBuilder IDE you run with full PB runtime (and dev-time) in the system path. PowerBuilder has a PB Runtime Packager tool to generate runtime install package. That package needs to be installed either:

  • In same folder as run app's .EXE + .PBD files - or -
  • In folder within system path

QUESTION: What DBMS is your app connecting to?

Each DBMS requires certain driver files. You mention login fails. To me that's a hint you may have missing files or configuration needed for your app's DB connection.

HTH /Michael

Comment
  1. Michael Kramer
  2. Thursday, 30 January 2020 18:24 PM UTC
Forgot important question - -Are you testing deployment on your development machine (where PB runtime is installed as part of PB dev toolset - or - are you testing deployment on separate machine?
  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.