Adam,

<< I think I've found the problem... The users are NOT logged in. A few
other users who decided to 'share credentials' WERE logged in, and keeping
there machines on over night!

That looks like it will account for the wierd 'ghost' records, although I'm
still concerned about the messages like:

[WARNING] Re-connection rejected, session not found [Client Version: 4.26]
Username: Address: 10.30.11.118 Encrypted: No Thread: 5148 Session: xxxxxxx
>>

That's a normal message.  It simply is a situation whereby the user left the
session around longer than the dead session expiration time, and the server
killed the session.  Then, when the user tries to do something with the
application again, the session is no longer present, so the server issues
that error.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Thanks for your reply...

> [WARNING] Re-connection rejected, session not found [Client Version: 4.26]
> Username: Address: 10.30.11.118 Encrypted: No Thread: 5148 Session:
> xxxxxxx
> >>
>
> That's a normal message.  It simply is a situation whereby the user left
> the session around longer than the dead session expiration time, and the
> server killed the session.  Then, when the user tries to do something with
> the application again, the session is no longer present, so the server
> issues that error.

So to see a few hundred of these during a day isn't a problem. The
application will just simply create a new session, and continue where it
left off? (Just trying to explore every possibility, as we're still getting
occasional decryption / AV errors).

Cheers

Adam.

Adam,

<< So to see a few hundred of these during a day isn't a problem. >>

Well, not exactly.  It means that you've got way too many people leaving
their application idle for long enough that the session is removed from the
database server due to the dead session expiration time.  You should
consider turning on the TDBISAMSession.RemotePing property in your
application in order to keep the application's session "alive" on the
database server.

<< The application will just simply create a new session, and continue where
it left off? >>

No, it won't.   The user will have to shut down the application and restart
it to get a new session.

<< (Just trying to explore every possibility, as we're still getting
occasional decryption / AV errors). >>

Decryption, or decompression ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Thanks for your reply...

> Well, not exactly.  It means that you've got way too many people leaving
> their application idle for long enough that the session is removed from
> the database server due to the dead session expiration time.  You should
> consider turning on the TDBISAMSession.RemotePing property in your
> application in order to keep the application's session "alive" on the
> database server.

Ahh - right. It is a problem then, as I though all users had remote pinging
turned on. Will have to double check

> << (Just trying to explore every possibility, as we're still getting
> occasional decryption / AV errors). >>
>
> Decryption, or decompression ?

Decompression - sorry.

Have a great weekend!

Adam.