I have a user reporting:

ElevateDB Error #504 The maximum number of concurrent sessions (4096)
has been reached.

This happens when the Session is first opened.  It is a new install
and no other users have reported this error.
On Vista SP2, all on the local machine

What am I looking for?

--

Malcolm wrote:

> I have a user reporting:
>
> ElevateDB Error #504 The maximum number of concurrent sessions
> (4096) has been reached.
>
> This happens when the Session is first opened.  It is a new install
> and no other users have reported this error.
> On Vista SP2, all on the local machine
>
> What am I looking for?

Hmm .. that post was submitted after the user had uninstalled,
deleted both the app's program and data folder trees, and then
re-installed.

Latest report is that after uninstalling and wiping again, shutting
down machine, having a good night's sleep, then booting and
re-installing .. it now runs just like we've come to expect Tim's
stuff to do!    <shrug, rolls eyes>

--

Malcolm,

<< Hmm .. that post was submitted after the user had uninstalled, deleted
both the app's program and data folder trees, and then re-installed.

Latest report is that after uninstalling and wiping again, shutting down
machine, having a good night's sleep, then booting and re-installing .. it
now runs just like we've come to expect Tim's stuff to do!  >>

Hmm, that's a weird one.  Locking is used to determine session usage, so
this type of problem indicates that the locking was failing for some reason.
We've seen this error on Windows CE device emulators when trying to use the
shared folder for storing an EDB database, so I suspect that the OS was
causing the locking calls to fail for some reason.

--
Tim Young
Elevate Software
www.elevatesoft.com