Hi there,

We have a CS app running DBISAM v4.27.1  It's installed at 4 sites and has
run just fine for years, the DBISAM version have been upgraded along the
way.  all sites are running the same version of DBISAM service and apps.

About 6 months ago one site had the DBISAM server stop responding.  Nothing
in the Windows Event logs, and nothing I could see in the DBISAM server log.
The actual service says it's running, but if you try to look at the server
with the admin utility it says there is no server to be found.  The solution
was to stop the service and restart it.  In fact you have to do it a couple
of times.  The service stops and starts OK, but the admin utility or our app
can't see the server until you've flipped the service on and off a couple of
times.

This happens regularly every 2-3 weeks.

Only one site has this trouble and they were all running W2K3.  We recently
upgraded the troublesome site to a new W2K8 server and it has exactly the
same symptom.  This site has about 20 users in our app most of the day, the
others only 4-5

Any suggestions?

Bruce,

<< Only one site has this trouble and they were all running W2K3.  We
recently upgraded the troublesome site to a new W2K8 server and it has
exactly the same symptom.  This site has about 20 users in our app most of
the day, the
others only 4-5 >>

I can send you a debug version of the server that will log a stack trace and
memory dump for any AVs or other unknown errors, but the debug servers are
all 4.29 (latest build).   Is the DBISAM Database Server the only process
accessing the database tables ?  If so, then you will be okay switching to
4.29.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Yes please, I'd love a debug version of 4.29
I'm not sure what else could be accessing the database tables, our
application runs in CS mode and if the DBISAM server is down the app is
broken.

So I can just swap out the 4.27.1 server for the 4.29 debug version without
updating my application?

Thanks and regards,
Bruce.

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:F4B1A681-F8CF-4B41-AEE8-52CE0A16609A@news.elevatesoft.com...
> Bruce,
>
> << Only one site has this trouble and they were all running W2K3.  We
> recently upgraded the troublesome site to a new W2K8 server and it has
> exactly the same symptom.  This site has about 20 users in our app most of
> the day, the
> others only 4-5 >>
>
> I can send you a debug version of the server that will log a stack trace
> and memory dump for any AVs or other unknown errors, but the debug servers
> are all 4.29 (latest build).   Is the DBISAM Database Server the only
> process accessing the database tables ?  If so, then you will be okay
> switching to 4.29.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Bruce,

<< Yes please, I'd love a debug version of 4.29 >>

Please send me an email, and I'll reply with a copy of the 4.29 debug
server.

<< So I can just swap out the 4.27.1 server for the 4.29 debug version
without updating my application? >>

Correct.  However, you cannot go back to 4.27 or earlier after using 4.29
with the database tables.  You'll have to stay with 4.28 or higher,
preferably 4.29.   This is due to the BLOB re-design in 4.28.

--
Tim Young
Elevate Software
www.elevatesoft.com