Error 35 - Error calling external object function.
Fernando Braga
SetTransObject method in a PB 7.0.3 (Build 10135) running on a
multi-threaded environment - DPB. In our code we execute the HALT CLOSE
command when it occurs to stop the thread and this leads to an Error 35 in
client application.
It is important to say that when the DPB server is restarted, these errors
disappears for a while and after 1 or 2 days they come up again. We also use
HALT CLOSE to stop the thread when a critical error occurs. We are using
MSSQL Server 2000 through native PBMSS70.DLL.
We wonder if it is possible to get rid of this situation, which we call
instability of DPB. Is there an explanation for such behavior? Is it
possible that we are facing memory leaking ?
TIA
Terry Voth
- What is the state of the transaction object when this error occurs?
Can you execute SQL against it? If the transaction object has been
disconnected, it may be either the PB DBMS driver or an issue with the
MS client software, or maybe even a network issue. In any case, if
this is the problem, you may be able to identify a work around.
- Keep in mind that for SQL Server 2000, OLEDB is the native database
driver. If your problem is with the SQL Server client software (as
mentioned above), you won't get any sympathy from MS.
Good luck,
Terry [TeamSybase] and Sequel the techno-kitten
On 2 Aug 2004 09:09:46 -0700, "Fernando Braga"
<NOSPAN...@ymf.com.br> wrote:
Sequel's Sandbox: http://www.techno-kitten.com
Home of PBL Peeper, a free PowerBuilder Developer's Toolkit.
Version 2.2.06 now available at the Sandbox
See the PB Troubleshooting Guide at the Sandbox
^ ^
o o
=*=