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

Resolved Deployed app closes on startup

  1. Issue
0
Votes
Undo
  1. Luc Railhac
    Luc Railhac
  2. PowerBuilder
  3. Wednesday, 24 January 2024 11:18 AM UTC

Hi,

Our app is being developed on PB2022 R3 (Build 3289) and works flawlessly in our development environment (Windows 10), in the IDE and when we deploy it locally as a 32 bits exe.

When trying to deploy it on a Windows 2012 R2 server as a 64 bits exe, the following happens:

  • The startup scripts run flawlessly, required application files are checked, .ini is read, the app connects to our Oracle database and we even call a REST security webservice successfully.
  • As soon as the app tries to open the MDI frame, the app closes without any custom or Windows error message.

 

PB2022 R3 runtime files are present on the server and the path is specified in appname.xml.

If the problem comes from the runtime files (or maybe prerequisites), is there a .log somewhere allowing us to have an idea of what is happening?

 

Thanks for your help,

Luc

  1. Deployment
  2. PowerBuilder Runtime
Image in Resource File(.pbr) not showing when DW i...
Powerbuilder 2022 Runtime
Accepted Answer
Luc Railhac
Luc Railhac Accepted Answer Pending Moderation
  1. Thursday, 1 February 2024 09:25 AM UTC
  2. PowerBuilder
  3. # Permalink

Our app has been successfully deployed to a Windows 2016 server.


FYI the initial issue was actually not related to PowerBuilder, this was an Oracle client issue which returned an invalid datetime causing an infinite loop: the datetime object signals the error to the error object, which calls the datetime object to get the datetime of the error…
We were able to see this using the /pbdebug command line switch, I stumbled upon this option in the help file and it’s really useful to diagnose application startup issues.

Thanks everyone for your help and sorry for the “false PB error report”, the fact this was happening right at the opening of the MDI frame was misleading.

Thanks again,
Luc

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 1 February 2024 17:01 PM UTC
Hi Luc .. thank you for letting us know your solution to the problem!
  1. Helpful
Luc Railhac
  1. Luc Railhac
  2. Friday, 2 February 2024 19:30 PM UTC
You're welcome, the net result of our discussion is that we now have Windows 2016 servers instead of 2012 R2, which is great.



Windows 2016 support was also a major concern for us, as it is the latest Windows version compatible with our Citrix platforms, otherwise we would have been obliged to go back to PB12.6 for one more year (or to an earlier version of PB Appeon).



The roadmap is still to upgrade Windows servers to 2019/22 and Citrix by the end of this year.
  1. Helpful
There are no comments made yet.
Responses (5)
Luc Railhac
Luc Railhac Accepted Answer Pending Moderation
  1. Wednesday, 24 January 2024 14:30 PM UTC
  2. PowerBuilder
  3. # 1

Hi Chris,

Does this mean it can't run at all on Windows Server 2012 R2 or just that it is no longer "officially" supported?
We have a project to migrate our production servers to Windows 2019 but this won't happen before the end of the year, and our app must be in production around june.

What is the last PB version supporting Windows 2012 R2?

Thanks again,
Luc

 

Comment
Andreas Mykonios
  1. Andreas Mykonios
  2. Wednesday, 24 January 2024 14:45 PM UTC
Last PB release with support for 2012 R2 was PB 2021 (of course support only for runtime).

Andreas.
  1. Helpful 1
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 24 January 2024 19:59 PM UTC
Correct Andreas!

@Luc ... basically - "use at own risk".
  1. Helpful
Luc Railhac
  1. Luc Railhac
  2. Thursday, 25 January 2024 13:38 PM UTC
We should be able to get 3 Windows 2016 servers in a few days (basically in exchange for the Citrix server where PB12.6 is installed) and I'll come back to tell you if the deployment worked.



Have a nice day,

Luc

  1. Helpful 1
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 24 January 2024 13:19 PM UTC
  2. PowerBuilder
  3. # 2

Hi Luc;

   FYI: note that the MS-Windows 2012 O/S is no longer supported in PB 2022 R3 ... https://docs.appeon.com/pb2022r3/installation_guide_for_pb/System_Requirements.html

Regards ... Chris 

Comment
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Wednesday, 24 January 2024 12:43 PM UTC
  2. PowerBuilder
  3. # 3

is your application exe signed?

 

this sound like anti-virus.  if you get a cert and sign it, this will most likely not occur.

Comment
There are no comments made yet.
Andreas Mykonios
Andreas Mykonios Accepted Answer Pending Moderation
  1. Wednesday, 24 January 2024 12:18 PM UTC
  2. PowerBuilder
  3. # 4

Hi.

Are the required Visual C++ files deployed to the server (vcruntime140.dll, vcruntime140_1.dll, concrt140.dll, and msvcp140.dll)?

Check the following link: Third-party components and deployment - - Application Techniques (appeon.com)

Read carefully the last part about Universal C Runtime (CRT) as this is related to Win Server 2012 R2.

Andreas.

Comment
Dennis Little
  1. Dennis Little
  2. Wednesday, 24 January 2024 19:36 PM UTC
We had almost the exact same issue when going to PB 2022 R2 on a Windows 10 box. As a last resort we copied ALL of the PB 2022 R2 shared folder and added to our start-in folder and that seemed to do the trick.
  1. Helpful 1
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.