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

Resolved Tips to troubleshoot browser crash

  1. Issue
0
Votes
Undo
  1. Konstantin Goldobin
    Konstantin Goldobin
  2. PowerBuilder
  3. Wednesday, 14 February 2018 20:49 PM UTC

Hello,

I'm currently looking into deploying PB applications to Web using the trial version of PowerServer Web. I took a simple existing application and deployed it to web. The first thing that immediately caught my eye was that the INI file was not deployed to the application folder (or its config subfolder) despite the fact that it was listed in the project configuration. Does anybody know what factors may prevent INI files deployment?

The second thing is that the app crashes IE most of the time, but not always. Once in a while it starts and works, but most of the time I go to the URL of the application, IE crashes. Knowing that Appeon has been webifying PB apps for quite some time, it is somewhat discouraging to see that even a simple application crashes right away, but what is more worrying is that there is no obvious way to troubleshoot the crashing. In case of a regular PB app one can at least run it with a pbdebug option and see where it crashes, but what can be done with an app deployed to web? Any ideas would be highly appreciated, because the trial period is only 30 days and to waste them troubleshooting IE crashing is not something anybody would want to do.

Best regards,
Konstantin

  1. PowerServer
Suggestion PB APU
PB2017 dot net Web Service Help
Responses (4)
Konstantin Goldobin
Konstantin Goldobin Accepted Answer Pending Moderation
  1. Thursday, 15 February 2018 06:47 AM UTC
  2. PowerBuilder
  3. # 1

Hello Govinda,

Thank you, I'm aware of the debugger. But that would mean stepping in through the code from the first line till it crashes, and since the debugger is highly unstable itself and crashes a lot, it's quite a challenge. Plus, you never know what happened: whether you reached the spot where your app dies or is it just the debugger died for some other reason...

Best regards,
Konstantin

Comment
There are no comments made yet.
Konstantin Goldobin
Konstantin Goldobin Accepted Answer Pending Moderation
  1. Thursday, 15 February 2018 06:44 AM UTC
  2. PowerBuilder
  3. # 2

Hello Chris,

  • PS Web version & build: Appeon PowerServer 2017 Build 1689.00 64-bit Edition 
  • MS-Windows version: Windows Server 2012 R2 Standard
  • IE version: 11.0.9600.18893

Sorry, Chris, I'm not I understand: if the INI file is not deployed to the IIS folder, how can it be deployed to a client? And BTW, INI files don't seem to get deployed to an IIS folder of PowerServer Mobile, which comes with PB17, either. In both cases I needed to place INI files in the config subfolder on IIS. That wa one of the reason of a "sudden death" of the webified app: when it tried to read an INI file that was not there, it crashed IE. In an Android emulator, it reported an error just like the regular original app does.

I tried it with Chrome, but it keeps downloading the plugin over and over again despite the fact that it was installed after the first download and restarting the browser.

Best regards,
Konstantin

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 15 February 2018 14:52 PM UTC
Hi Konstantin;



  If it was deployed to PowerServer OK .. then you should see and even edit your INI in the AEM console, as follows (for example):







Regards ... Chris

  1. Helpful
There are no comments made yet.
Govinda Lopez @Appeon
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 14 February 2018 23:16 PM UTC
  2. PowerBuilder
  3. # 3

Hi Konstantin,

 

You actually can debug web deployments. Here's a document that details how to do that: https://www.appeon.com/support/documents/appeon_online_help/2015/appeon_developer_user_guide/ch06.html

 

I hope this helps.

 

Regards,

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 14 February 2018 21:54 PM UTC
  2. PowerBuilder
  3. # 4

Hi Konstantin;

     First of all, please do not worry about the trial. You can always send an email to sales@appeon.com and request an extension.

    As for the INI file, it should be deployed to the App's working folder on the client PC. Normally, that would be for example "C:\Users\\AppData\Roaming\appeon\\plugin". The INI file will be XML format - something like INI.xml. However, you should not need to specify the INI file's path in the ProfileXxxx() commands unless you deploy the INI to another location other than its default. The PS Web run-time should point to that App's location by default. It will also change the ProfileXxx handling at execution to XML parsing.

  BTW: Can you tell us ...

  • PS Web version & build
  • MS-Windows version
  • IE version

  Have you tried any other browsers with your Web App?

Regards ... Chris

    

 

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.