1. Minogue Susan
  2. PowerBuilder
  3. Monday, 7 January 2019 14:02 PM UTC

Hi All,

we have application which is developed in PB 11.5 and recently we have migrated it to PB2017 to make this work in windows 10 machine. But we are facing issues with it. 

We could open the login form but later it will closed automatically, sometimes we receive an error as "system error". 

Could you please provide your advises to over come this issues.

Thank you in advance.

ivan sinarahua Accepted Answer Pending Moderation
  1. Wednesday, 20 January 2021 04:29 AM UTC
  2. PowerBuilder
  3. # 1

Hi, 

I have the exact same problem.  It was working fine but Windows 10 released a new update and after that the app crashes when a dw is involved.  

Do you have any news about the subject? I would appreciate any comments

 

thank you

 

Amelia

Comment
There are no comments made yet.
Minogue Susan Accepted Answer Pending Moderation
  1. Thursday, 14 February 2019 07:13 AM UTC
  2. PowerBuilder
  3. # 2

Hi All,

we have done some more test cases on application and found that application works fine if we run as administrator. But all users have normal access and doesn't have administrator access to application. Please advise, how we can resolve it without run as administrator.

Thank you in advance. 

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 14 February 2019 14:33 PM UTC
Hi Sadananda,

In your Project Object that builds the App's EXE .. do you include / embed a "Manifest" in the EXE?

Regards ... Chris
  1. Helpful
There are no comments made yet.
Minogue Susan Accepted Answer Pending Moderation
  1. Wednesday, 30 January 2019 14:13 PM UTC
  2. PowerBuilder
  3. # 3

In the app we have developed , the data windows are not painting on Windows 10. We are using 2017 R3. We have tried having an empty datawindow without a data object and the application simply crashes with system error. 

We get the error below in the event log 

Faulting application name: sample_application.exe, version: 1.0.0.1, time stamp: 0x5b6318c2
Faulting module name: PBVM170.dll, version: 17.2.0.1858, time stamp: 0x5b6319d3
Exception code: 0xc000041d
Fault offset: 0x000ef3c3
Faulting process id: 0x6db4
Faulting application start time: 0x01d4b89c83ca95de
Faulting application path: C:\Test_Application\sample_application.exe
Faulting module path: C:\pb2018_dll\PBVM170.dll
Report Id: 834b97a5-b9d8-4dbc-9c02-45f1bfbca8f0
Faulting package full name:
Faulting package-relative application ID:

 

Any help and insights into resolving it is much appreciated. 

 

Thanks

Sadananda

Comment
There are no comments made yet.
Andres Slachevsky Accepted Answer Pending Moderation
  1. Tuesday, 8 January 2019 12:52 PM UTC
  2. PowerBuilder
  3. # 4

Are you running from the PB IDE?
if yes why are you not run in debug mode to find the line that cause the crash 

do you have any external DLL calls from the app?

Comment
There are no comments made yet.
René Ullrich Accepted Answer Pending Moderation
  1. Tuesday, 8 January 2019 09:22 AM UTC
  2. PowerBuilder
  3. # 5

Hi Sadananda,

 

you could try to run the application with /pbdebug parameter (or from IDE using the "Enable PBDebug Tracing" from System Options). It writes a log file about every line it executes. So you can find out what statement produces the crash.

Regards,

René

Comment
  1. Chris Pollach @Appeon
  2. Wednesday, 9 January 2019 19:56 PM UTC
Hi Sadananda;

For the DWO that causes the crash in the DS ... can you open the DWO's source and see if the 1st line in the source code states "release 17;",

If not, change the release number to 17, save the DWO and then retest.

HTH

Regards ... Chris
  1. Helpful
  1. Minogue Susan
  2. Friday, 25 January 2019 10:51 AM UTC
Hi

Now, SQLCA connected without any errors. I have added driver details in connection string and able connect transaction successfully.



But, still application crashes at datastore retrieval. I tried run one single query and able to retrieve information but couldn't retrieve from data store. Please advise do we have any dll's or drivers for datastore also.



Driver details added to existing connection string: Driver={ODBC Driver 13 for SQL Server}

Application crashes at :

li_rowcount = lds_access_level.Retrieve(s_uid)



Application works good in server and crashes in windows 10 local machine.



Thank you.
  1. Helpful
  1. Minogue Susan
  2. Friday, 25 January 2019 13:55 PM UTC
Hi All,



I created one test application to test each object. Below are my findings

1. Application could connect to transaction object

2. Able to retrieve information on window. (Data retrieved and displayed on message box)

3. Couldn't able to open data window

4. when we trying to open data window in windows 10, total application crashes.



Please provide your advises to resolve it.
  1. Helpful
There are no comments made yet.
Minogue Susan Accepted Answer Pending Moderation
  1. Tuesday, 8 January 2019 08:57 AM UTC
  2. PowerBuilder
  3. # 6

Thank you Chris.

1. It is not PFC based app. it is windows application.
2. yes, we have code to capture some of error codes. But here we didn't receive any error it just closes the application without any warnings/ errors.
3. yes, we ran the code through Migration assistant and then built pbd's
4. we didn't receive any Warnings/ errors on Full Build.

we have run migration assistant in our server and built PBD's. we are able to use application in server i.e. WIndows 12 R2 server but facing issues in windows 10 local machine.

we also have copied required DLL's from powerbuilder Shred folder and copy in our local machine. Do we need to copy any other DLL's. we are using windows 10.0.17134.472 version. Please advise.

Thank you again for your help,

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 7 January 2019 18:50 PM UTC
  2. PowerBuilder
  3. # 7

Hi Sadananda;

  Can you tell us ...

  1. Is this a PFC based App?
  2. Does your App have code in the System Error event to capture / log the exact error code & error text?
  3. Did you run the PB 11.x App code through the PB2017's "Migration Assistant" before migration?
  4. Does your APP call external O/S API's or 3rd party DLL's?
  5. Is your App receiving any Warning or Error messages when performing a Full Build?

Regards ... Chris

Comment
  1. Chris Pollach @Appeon
  2. Tuesday, 8 January 2019 17:35 PM UTC
Hi Sadananda;



1) Does the App work (run) OK from the PB IDE?

2) In your project object where you build the EXE ... did you include a "Mainfest"?



Regards... Chris



  1. Helpful
There are no comments made yet.
Marco Meoni Accepted Answer Pending Moderation
  1. Monday, 7 January 2019 15:38 PM UTC
  2. PowerBuilder
  3. # 8

Hello Sadananda,

I would run the application from the PB debugger and pinpoint the exact line that causes the crash.

It might be DB issue (i.e. need for an up-to-date driver), or ANSI/Unicode chars, or many more things related to the new platform.

Best,

Marco

Comment
  1. Miguel Leeuwe
  2. Wednesday, 9 January 2019 05:55 AM UTC
It sounds to me like a missing runtime library or maybe wrong runtime build installed.

- Do you have a runtime installed or are the dll's simply copied to some place?



Maybe a way to figure out is to run process monitor and see where it crashes: https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
  1. Helpful
  1. Minogue Susan
  2. Wednesday, 9 January 2019 13:00 PM UTC
we have copied all required DLL's from C:\Program Files (x86)\Appeon\Shared\PowerBuilder to our local machine.

Do we need copy any other DLL's



Thank you.
  1. Helpful
  1. Miller Rhodes
  2. Monday, 15 June 2020 20:17 PM UTC
I had this exact same problem. I could run my application EXE with no issues and then something changes and I have to now 'Run As Administrator" . Otherwise, the application crashes.
  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.