1. Krishna Mohan Gullap
  2. PowerBuilder
  3. Thursday, 7 March 2019 15:55 PM UTC

Hello PB Guru's

I have one burning issue right now. Our PowerBuilder application is on version 12.6 and build # 4091

Some of our terminal users have reported that the application suddenly crashes and throws an 'InPageError'. This doesn't happen for all users, but specific people. I have attached a snapshot of this error

What could be the possible reasons this error might occur? Appreciate any suggestions to fix this

Thanks,

Krishna

Attachments (1)
Accepted Answer
Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 7 March 2019 18:57 PM UTC
  2. PowerBuilder
  3. # Permalink

To show that it's not the code failing, create a classic installation.

1.  Find one of the users to whom this error is occurring

2.  Install the application on their personal platform, complete with ALL required files and DLLs.

3.  Run the app. Keep it running.

4.  When the app refuses to fail with that error, you'l have a pretty convincing argument.

 

Later -

Olan

Comment
There are no comments made yet.
Krishna Mohan Gullap Accepted Answer Pending Moderation
  1. Monday, 25 March 2019 13:05 PM UTC
  2. PowerBuilder
  3. # 1

Thanks to you all for your help. I am going to try the following (on the same lines as suggested by Olan):

 

1. Right now, the users log into a 'terminal' server, say abc, and run a shortcut to the application

2. The shortcut actually runs an application which is hosted on an application server, say xyz, on which the application build is hosted. The 'target' property of the shortcut reads something like '\\xyz\\appname.exe

3. Instead, I am going to just move the build to the 'terminal' server and host it from there instead of trying to access the build on \\xyz\.....

 

Hope this will eliminate most of the cases in which this issue occurs

Comment
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 7 March 2019 19:00 PM UTC
  2. PowerBuilder
  3. # 2

The event log entry that you are seeing was not logged by PowerBuilder. That is your proof right there.

Comment
There are no comments made yet.
Krishna Mohan Gullap Accepted Answer Pending Moderation
  1. Thursday, 7 March 2019 18:40 PM UTC
  2. PowerBuilder
  3. # 3

Thank you Roland. Is there a way to confirm this? I see this error in the event viewer at times -> "Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program abc.exe because of this error"

I have placed a batch file which pings the network path from the terminal machine every 30 seconds in an infinite loop and log the output. Will this help identify if some pings fail, then maybe it has to be a network error?

Or is there a better way to prove it probably is a network error?

Comment
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 7 March 2019 16:36 PM UTC
  2. PowerBuilder
  3. # 4

It is likely due to network issues causing the application to not be able to access a file it needs.

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 7 March 2019 19:16 PM UTC
Hi Roland ... I always wondered why MS called it "Terminal" Server. Hmmmm? ;-)
  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.
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.