• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Crash in 2017 R3 build 1858 - debug mode and app execution

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

Resolved Crash in 2017 R3 build 1858 - debug mode and app execution

  1. Issue
0
Votes
Undo
  1. Menna Pablo Javier
    Menna Pablo Javier
  2. PowerBuilder
  3. Friday, 10 May 2019 16:13 PM UTC

Hello Chris, I have a problem with the IDE, version 2017 R3 build 1858. It happens that being in debug mode, in any part of the code, the system hangs. The error is not constant, so I deduce that it is not due to an error in the code. In addition, the same system already compiled, closes frequently without following the same pattern of execution. Any idea what may be causing it? Thank you!

PB 2017 64 Bit Deployment
Error Using SVN Native
Responses (2)
Menna Pablo Javier
Menna Pablo Javier Accepted Answer Pending Moderation
  1. Monday, 13 May 2019 12:47 PM UTC
  2. PowerBuilder
  3. # 1

Hello. Thank you for your response. However, I already do these steps in past (for another kind of problems), and didn't can solve it. Next I include some additional data:

The application was migrated from the IDE Powerbuilder 9 to Powerbuilder 2017, taking into account that the database connection driver was changed to SNC Native Client, having to modify the following parameters in order to maintain functionality. Modified connection properties:
* DBMS: SNC SQL Native Client (OLE DB)
* Provider = 'SQLNCLI11
* OptSelectBlob = 1
* BinTxtBlob = 1
* DateFormat = \ dd / mm / yyyy \
* DateTimeFormat = \ dd / mm / yyyy hh: mm: ss.fff \
* TimeFormat = hh: mm: ss.fff \
The following statements are executed before making the connection using the transaction object
* EXECUTE IMMEDIATE "SET ANSI_WARNINGS OFF;" USING SQLCA;
* EXECUTE IMMEDIATE "SET ANSI_NULLS OFF;" USING SQLCA;
In the majority of cases it happens executing the compiled application, when opening a report of a datawindow, and it occurs during the reading of information (for which I assume that it is something of the interaction with the database).

BTW: sorry for the redaction, i'm from Argentina and have a medium/low english handle.

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 13 May 2019 18:01 PM UTC
Hi Menna;

May I suggest ....

1) OptSelectBlob is not supported by SNC

2) BinTxtBlob=1 means non-Unicode data. Whereas PB2017Rx is fully Unicode

3) Make sure that all DBMS interactions check the DB return status code(s).

4) Not sure why your App is turning off ANSI_Warnings and NULLs.

Try commenting these "SET" commands out as its not common a practice.

5) Try tracing your app's EXE by adding the " /pbtrace" to the EXE start-up

6) Try adding in an SQL trace ... (SQLCA.DBMS = "TRACE SNC")

7) Review your App's code for Unicode compliance. PB9 was ANSI based

- ANSI defined external functions => Unicode

- ANSI based PowerScript commands => Unicode

8) DB Date formats should always be CCYY-MM-DD internally

9) DB DateTime formats should always be CCYY-MM-DD HH:MM:SS:FFF internally

Also... did you run the PB 2019 "Migration Assistant" on your PB 9 App source before migration to see if it logged any PB 9 features that need to be cleaned up for PB 2017?

HTH

Regards ... Chris
  1. Helpful
Olan Knight
  1. Olan Knight
  2. Thursday, 16 May 2019 23:26 PM UTC
Your English is better than my Spanish, mi amigo! :)
  1. Helpful
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Friday, 10 May 2019 17:41 PM UTC
  2. PowerBuilder
  3. # 2

I've had this issue in pre-2017 version of PowerBuilder, and in most cases it is solved by

1. Review the library list to ensure completeness
2. Do a FULL BUILD on the application
3. Now try it again.


Good Luck,

Olan

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 10 May 2019 18:17 PM UTC
I agree with Olan as a 1st step - however, I would a another step (1A) to the list and perform an optimize on all your PB's before the full build.
  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.