1. Sim Joo Pee
  2. PowerServer 2020 or older (Obsolete)
  3. Monday, 14 October 2019 02:03 AM UTC

Hi Sir or Madam,

  I had setup the PowerServer web, with proper AEM configuration. HOwever, it failed/didnt  save to the table/database after i click save. There is no error return. I believe the connection to server/database is succeeded, because i am  able to login (it is our application logon screen) and data display correctly. Please advice. Thank you.

 

Sim Joo Pee Accepted Answer Pending Moderation
  1. Friday, 18 October 2019 08:27 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi All,

  Thanks so much for the reply. I need to debug my programs. Look like something wrong in the pfc files, pfc_n_cst_luw, it return 0 on the updatepending call. I dnt know why. I need to run Appeon Debugger on this. However, i got below error when launching it.... Please help. Thanks in advance.

Comment
  1. Chris Pollach @Appeon
  2. Friday, 18 October 2019 16:36 PM UTC
Hi Sim .... Are you using PS2019?
  1. Helpful
  1. Sim Joo Pee
  2. Monday, 21 October 2019 00:30 AM UTC
Hi Chris,

I think so because i am usinng PB2019 trial version.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 21 October 2019 13:23 PM UTC
Yes, you would be using PB2019. The GA release though has an issue in the DLL routine that supports the debugging operations. Support ticket # 3154 is currently tracking this bug. It also includes a new the DLL that fixes this issue. https://www.appeon.com/standardsupport

If you search for this ticket number in the support system, please download the " EonDbgEng.dll" attached to this ticket. Please follow steps below to temporary solve the issue .....

1 Backup the the file EonDbgEng.dll under %Toolkit%, for example:

C:\Program Files (x86)\Appeon\PowerServer 2019\Toolkit

2 Replace above file with attached one.

HTH ... Chris
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 14 October 2019 02:28 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Sim;

   Make sure that ...

1) The DWO that your App is using has proper update properties set.

2) Your App checks the Update() command's return code for a good status.

3) Other DW events code are not preventing the AcceptText() from working to transfer data from the keyboard to the DWO's primary buffer.

4) Your App is issuing a proper Commit command after the update.

5) Your App is not inadvertently issuing a Rollback after a successful update ().

6) Code in other DC events are blocking the update SQL from running.

Tip: Turn on Debug Logging in AEM & check to make sure in the PS logs that you see the Update & Commit statements coming through PowerServer.

Regards ... Chris

 

Comment
  1. Sim Joo Pee
  2. Monday, 14 October 2019 02:50 AM UTC
Hi Chris



Thanks for your quick reply. I check the error log from AEM, They are:.. WHY?



2019-10-14 09:55:05.088 : Connection to Sybase server has been lost. Connection died while writing to socket. Socket returned error code 10054. All active transactions have been rolled back.

at Sybase.Data.AseClient1.AseCommand.CheckResult(Int32 res)

at Sybase.Data.AseClient1.AseCommand.ExecuteNonQuery()

at Appeon.Server.Services.DataService.ASE.EonASENETConnection..ctor(AseConnection _dbConnection, PBTransactionProperties _pbTrans, Int32 commandTime)

2019-10-14 10:45:41.185 : Connection to Sybase server has been lost. Connection died while writing to socket. Socket returned error code 10054. All active transactions have been rolled back.

at Sybase.Data.AseClient1.AseCommand.CheckResult(Int32 res)

at Sybase.Data.AseClient1.AseCommand.ExecuteNonQuery()

at Appeon.Server.Services.DataService.ASE.EonASENETConnection..ctor(AseConnection _dbConnection, PBTransactionProperties _pbTrans, Int32 commandTime)

  1. Helpful
  1. Sim Joo Pee
  2. Monday, 14 October 2019 02:52 AM UTC
Hi Chris,



I also setup the debug mode at AEM. What i can do with that? I run it and i see no different?
  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 14 October 2019 02:54 AM UTC
Hmmm ... Looks like a possible ASE connection issue. Are you using the native ASE or ODBC connectivity from PS to ASE in your "Data Source" declaration?

Debug Tracing requires two settings ...

1) Global

2) application

When those are both on, Debug Tracing will activate.
  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.