Hi,

I'm having a client that is experiencing this error with DBISam 4.25b5
(compiled with Delphi 7). What is confusing is that we are not using data
compression.

Can you please advise on what I might be doing wrong?

Thanks & Regards

Adam.

Adam,

<< I'm having a client that is experiencing this error with DBISam 4.25b5
(compiled with Delphi 7). What is confusing is that we are not using data
compression.

Can you please advise on what I might be doing wrong? >>

Is your application using a remote session that accesses the DBISAM database
server ?  If so, then this type of error could occur due to an error with a
request/receipt transaction with the server.

--
Tim Young
Elevate Software
www.elevatesoft.com

Good Morning Tim,

> << I'm having a client that is experiencing this error with DBISam 4.25b5
> (compiled with Delphi 7). What is confusing is that we are not using data
> compression.
>
> Can you please advise on what I might be doing wrong? >>
>
> Is your application using a remote session that accesses the DBISAM
> database server ?  If so, then this type of error could occur due to an
> error with a request/receipt transaction with the server.

Yes - it is using a remote session to connect to a database server. When you
say an error with the request/receipt, are you saying that the server (or
client) could be erroring out, or are we talking data corruption along the
network, or is it a property I've set incorrectly, etc?

Have you got any advise on where I should start looking?

Thanks & Regards

Adam.

Adam,

<< Yes - it is using a remote session to connect to a database server. When
you say an error with the request/receipt, are you saying that the server
(or client) could be erroring out, or are we talking data corruption along
the network, or is it a property I've set incorrectly, etc? >>

This type of error is normally caused by an error in the client or database
server but could also, in rare cases, be caused by a faulty network
connection/hardware.

How many other sites are using the same setup ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> This type of error is normally caused by an error in the client or
> database server but could also, in rare cases, be caused by a faulty
> network connection/hardware.
>
> How many other sites are using the same setup ?

In this particular case, none. The current setup is unique to this
particular site.

Best Regards

Adam.

Adam,

<< In this particular case, none. The current setup is unique to this
particular site. >>

Sorry for not being more clear in my question.  What I meant was - in terms
of your software/DBISAM ?  Or just in terms of the hardware/network ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> << In this particular case, none. The current setup is unique to this
> particular site. >>
>
> Sorry for not being more clear in my question.  What I meant was - in
> terms of your software/DBISAM ?  Or just in terms of the hardware/network
> ?

Sorry - maybe it was me (didn't get enough sleep ...

The software in question is used by others, but as a stLocal application.
This client is unique in the fact they're using stRemote for this
application (mainly because of the amount of data, and the number of users).

As far as hardware is concerned they are on a Domain with a 1GB switch (and
server) and clients running 100mb NIC's.

The server is a Windows 2003 RC2 Standard Edition (The only client I have
running on this particular version of Windows Server).

Workstations are all Windows XP.

Not everyone has received this error, only those that do more processing
than others.

Best Regards

Adam.

Adam,

<< Sorry - maybe it was me (didn't get enough sleep ... >>

Nah, I asked a vague question.

<< The software in question is used by others, but as a stLocal application.
This client is unique in the fact they're using stRemote for this
application (mainly because of the amount of data, and the number of users).

As far as hardware is concerned they are on a Domain with a 1GB switch (and
server) and clients running 100mb NIC's.

The server is a Windows 2003 RC2 Standard Edition (The only client I have
running on this particular version of Windows Server).

Workstations are all Windows XP.

Not everyone has received this error, only those that do more processing
than others. >>

Is more than one workstation seeing the error ?  It could (obviously) be a
bug in DBISAM, but it must be pretty rare since all hell would break loose
around here if basic functionality like the send/receive compression was
failing.

Do you have any idea what operation is triggering the error ?  One way to
find out would be to enable the remote tracing in the client application's
TDBISAMSession component.  Then you can find out exactly which request is
causing the error.  If you need further help with this, just let me know.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> Is more than one workstation seeing the error ?  It could (obviously) be a
> bug in DBISAM, but it must be pretty rare since all hell would break loose
> around here if basic functionality like the send/receive compression was
> failing.

LOL - yeah, I know what you mean. Yes - more than one workstation has
received the error, however as previously mentioned the error is rare. There
may be 3 or 4 weeks go by without a problem, and then their will be a spate
of errors. Then everything seems to behave itself relatively well again.

> Do you have any idea what operation is triggering the error ?  One way to
> find out would be to enable the remote tracing in the client application's
> TDBISAMSession component.  Then you can find out exactly which request is
> causing the error.  If you need further help with this, just let me know.

Just a TDataset.Open command is where the error appears to be triggered.
(Through db.pas's Setconnected procedure/method). At this stage, I have no
more information, but I'll see if I can track it deeper when it happens
again.

Cheers

Adam.

Adam,

<< LOL - yeah, I know what you mean. Yes - more than one workstation has
received the error, however as previously mentioned the error is rare. There
may be 3 or 4 weeks go by without a problem, and then their will be a spate
of errors. Then everything seems to behave itself relatively well again. >>

If that is the case, then most likely the cause is external.  Are they
having any other issues with the network at all ?

--
Tim Young
Elevate Software
www.elevatesoft.com