Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 8 of 8 total
Thread Advice required on how to handle Error 11276 (DBISAM V3)
Mon, Apr 7 2008 6:54 AMPermanent Link

"Trevor Keegan"
Hi,

I have an old application that I wanted to convert to C/S.  I have simply
installed the DBSRVR onto the server and configured the Session and Database
components.....and everything seems to work well.

My problem is that occassionally I appear to get a 11276 Error...as this was
originally a non-C/S application I have not got anything special to handle
these type of problems.....with my application being on a LAN I have assumed
that there should not be any occassion when the connection should drop out
(I have KeepConnection set the True for both the Database and Session).

Can any one tell me:
1. Why this problem may occur
2. Any guide on what I should do to handle this type of thing.

Regards
Trevor Keegan

Mon, Apr 7 2008 12:52 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Trevor,

<<  1. Why this problem may occur
2. Any guide on what I should do to handle this type of thing. >>

The easiest way to handle this is to simply set the
TDBISAMSession.RemotePing property to True.  As long as you haven't modified
the session timeout setting on the database server, the default
TDBISAMSession.RemotePingInterval property setting will be sufficient (60
seconds).

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Apr 7 2008 1:39 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim

>TDBISAMSession.RemotePing property to True.

I thought that didn't make an appearance until V4?

Roy Lambert
Mon, Apr 7 2008 10:22 PMPermanent Link

"Trevor Keegan"
Hello Tim,

I cannot find these properties on the TDBISAMSession at all.....any other
advice?

Regards
Trevor Keegan

Tue, Apr 8 2008 3:34 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Trevor


See my post above - Tim's advice relates to the next version of DBISAM.  You need to set something up yourself to keep the connection open. I've never used c/s myself so I don't know how personally but here's a post from 2004


Jacob,

> I have read over the discussion group and it seems like the solution is to
use
> GetRemoteDateTime() function periodically. This seems to prevent the
server app
> to consider a session "Dead" whenever the client stops accesing server for
a long
> period of time.

Correct, that workaround is as close as you will get with V3.x. The 'ping'
facility in V4.x was added to enhance functionality in this area.

Eryk


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.580 / Virus Database: 367 - Release Date: 06/02/2004


Roy Lambert [Team Elevate]
Tue, Apr 8 2008 8:17 AMPermanent Link

Trevor Keegan
Hello Roy

> I have read over the discussion group and it seems like the solution is to
use
> GetRemoteDateTime() function periodically. This seems to prevent the
server app
> to consider a session "Dead" whenever the client stops accesing server for
a long
> period of time.

Thanks a bunch....I guess that the easiest thing then is to call this from within a Timer
event...would that be right?

Regards
Trevor keegan
Tue, Apr 8 2008 8:31 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Trevor


Sounds good to me.

Roy Lambert [Team Elevate]
Tue, Apr 8 2008 1:48 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Trevor,

<< I cannot find these properties on the TDBISAMSession at all.....any other
advice? >>

My apologies, I missed the V3 part in the subject header.  Roy's advice is
correct - just use a timer along with a call to the GetRemoteDateTime and
that will be equivalent to a ping in 4.x.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image