• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • System.InvalidOperationException: This SqlTransaction has completed; it is no longer usable.

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

Resolved System.InvalidOperationException: This SqlTransaction has completed; it is no longer usable.

  1. Issue
0
Votes
Undo
  1. backya arun
    backya arun
  2. PowerBuilder
  3. Friday, 20 March 2020 13:49 PM UTC

Hi,

 We have migrated PB 8 to 11.5 then PB 11.5 to PB 19.. No issues in PB 8.. but in PB 19, Randomly i'm getting the below error while closing the windows in Powerbuilder 19 build(2170).DBMS is SQL server 2008 R2.

System.InvalidOperationException: This SqlTransaction has completed; it is no longer usable.

at Sybase.PowerBuilder.Db.Block.SqlBlock.ProcessError(Exception ee)

at Sybase.PowerBuilder.Db.Data.DbBlock.DoTransaction(PbTrans oper)

at Sybase.PowerBuilder.Db.DbRoutine.DoTransaction(PbTrans oper)

 

Any guess???

 

Regards,

Backya

How to have a console application wait for termina...
Wich column/row in Tile Menu Style using Datawindo...
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 20 March 2020 14:38 PM UTC
  2. PowerBuilder
  3. # 1

Hi Backya;

   Is this related to the ADO.Net driver question / issues that you posted in another community thread?

Regards ...Chris

Comment
backya arun
  1. backya arun
  2. Friday, 20 March 2020 15:00 PM UTC
Hi Chris

Not related to that query.. this is another issue I am facing..



Regards

Backya

  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 20 March 2020 15:44 PM UTC
But, using ADO.Net ... correct?
  1. Helpful
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Sunday, 22 March 2020 00:04 AM UTC
  2. PowerBuilder
  3. # 2

Have you walked through the code in DEBUG mode to determine exactly where the failures are occurring?

It appears as if there are  database activities being attempted during the CLOSE process. It is possible that the old code has built-in safeguards that prevented this for occurring, but that those safeguards are no longer in place.

IF there is a database activity being attempted, wrap an sqlca.of_isconnected() test check around the activity.


FYI, if you are not using the PFC's transaction object SQLCA, here's the of_isconnected code:

if this.DBHandle() = 0 then
    return false
else
    return true
end if



Later -

Olan



Comment
Load more comments
Olan Knight
  1. Olan Knight
  2. Monday, 23 March 2020 23:19 PM UTC
And the "hearbeat" feature is.....
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 24 March 2020 01:57 AM UTC
A new feature I added to my framework in 2018 but, had been using for years in various PB Apps ....

http://chrispollach.blogspot.com/2018/02/ifc2018r1.html

Basically, a DB "Ping" operation to keep the DBMS from timing out the connection. A technique used by almost every Web & App Server - including PB's old EAServer.
  1. Helpful
Olan Knight
  1. Olan Knight
  2. Tuesday, 24 March 2020 13:41 PM UTC
I see. Thank you for sharing!



Later -

Olan
  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.