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

Resolved Powerserver Debug not functioning correctly

  1. How-to
0
Votes
Undo
  1. Louis Arena
    Louis Arena
  2. PowerServer
  3. Friday, 30 December 2022 17:18 PM UTC

Has anyone noticed that the Debug in Powerserver is a little wonky?  I just upgraded to the latest release build 1892 and I am still having the same issue.  I am trying to debug a weird problem I am having so I setup a quick test event for me to debug.  See the code below.  

 

integer i

Transaction SQLCC


SQLCC = Create Transaction
f_copy_tran(sqlcc)   /* copies all transaction parameters */
SQLCC.logid = 'sa'
SQLCC.autocommit=TRUE
SQLCC.logpass = [sa password]
DISCONNECT USING SQLCC;
CONNECT USING SQLCC;
// must grant the user access to login functions so they can change their password on SQL 2008 and above 2014-12-30
// this procedure must exist in the MASTER database because server permissions can only be set there
i = pos(SQLCC.DBParm, "Database")
SQLCC.DBParm = left(SQLCC.DBParm, i - 1)
SQLCC.DBParm = SQLCC.DBParm + "Database='master'"
SQLCC.database='master'

DISCONNECT USING SQLCC;
CONNECT USING SQLCC;

In debug I want to see if SQLCC connects properly.  However in debug for Powerserver I do not see the SQLCC transaction!  Before you ask, yes SQLCC is defined in advance section of the Database tab for the my cloud project.  Additionally, the original code does work for SQLCC, it is just when I try and change databases that I am having a problem and therefore wanted to debut it.

Thanks

请问下powerserver 怎样写个接口供别人调用
SESSION CREATION FAILED POWERSERVER
Responses (2)
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Saturday, 18 February 2023 21:13 PM UTC
  2. PowerServer
  3. # 1

Hi,

I've been playing around with Powerbuilder 2022 (not powerserver). I'm setting my debug stops, run the application which blows up without any visible error messages, except for this in the event viewer of windows:

"Error":

Faulting application name: PB220DebugService_x64.exe, version: 22.0.0.1892, time stamp: 0x63765251
Faulting module name: ntdll.dll, version: 10.0.19041.2130, time stamp: 0xb5ced1c6
Exception code: 0xc0000005
Fault offset: 0x00000000000a3f52
Faulting process ID: 0x4aa4
Faulting application start time: 0x01d943dc6c86ff78
Faulting application path: D:\Appeon2022\PowerBuilder 22.0\IDE\x64\PB220DebugService_x64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: ec53e735-c5b3-486d-8869-c5b4566d8c82
Faulting package full name: 
Faulting package-relative application ID:

right after that, "Information":

Fault bucket 1797497323345878776, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: PB220DebugService_x64.exe
P2: 22.0.0.1892
P3: 63765251
P4: ntdll.dll
P5: 10.0.19041.2130
P6: b5ced1c6
P7: c0000005
P8: 00000000000a3f52
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB19.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD0E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD3E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD3E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD6E.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_PB220DebugServic_a81e807a9083fe84a776c39ae579ce1679821e_1d2d54f9_744f92bc-3f54-4519-9fff-d87cbbcba354

My suggested "trick" of entering the application and immediately exiting (and even closing powerbuilder), does NOT work for PB2022. All of my stops keep disappearing constantly. So the OP might make a very valid point here!!

regards

 

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Saturday, 18 February 2023 23:53 PM UTC
BTW: I figured out why the app blew-up. I was running in 64 it mode and had to replace Roland's n_osversion object with his latest version. (not really the point here, but just to clear up why it blew-up).

regards.
  1. Helpful 1
Logan Liu @Appeon
  1. Logan Liu @Appeon
  2. Monday, 20 February 2023 02:47 AM UTC
Hi Miguel, for the PB Debugger crash issue, kindly please report it via our support ticketing system to ensure it is being properly received by our tech support and tracked at: https://www.appeon.com/standardsupport/



BTW: The PowerServe Debugger feature talked about in this post is a new feature for PowerServer 2022. When not fully built or deployed, you may fail to watch the variables when debugging the PowerServer project.

Regards, Logan
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 20 February 2023 06:51 AM UTC
Hi Logan,

I'll make a ticket. You're right.

regards
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 30 December 2022 17:41 PM UTC
  2. PowerServer
  3. # 2

Hi Louis;

   FWIW: I have no such issues when using local transaction object's in the PS App using the IDE's PS project debugger.

  Have you tried making SQLCC. Global object?

Regards ... Chris 

Comment
Load more comments
Louis Arena
  1. Louis Arena
  2. Friday, 30 December 2022 18:45 PM UTC
It is getting even weirder. On my local cloud test, I recompiled because of the new build. In debug it sees the changes on a window I am testing with. On the production cloud version, I rebuilt and then during test it is bringing up the old version of the window! Not a library issue since both libraries are the same.
  1. Helpful
Francisco Martinez @Appeon
  1. Francisco Martinez @Appeon
  2. Friday, 30 December 2022 18:59 PM UTC
Hi Louis, I had that happen to me a couple of times. It turned out there were some PBD files in the workspace directory that were not being cleared when deploying. Deleting these files made the changes reflect correctly in the Cloud App.



Regards - Francisco
  1. Helpful 3
Logan Liu @Appeon
  1. Logan Liu @Appeon
  2. Tuesday, 3 January 2023 02:01 AM UTC
Hi Louis,

Please full-build the PowerServer project and verify it again.

Regards, Logan
  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.