Hello:

   I am using DBISAM version 1 which is a file share version and my
customer was running perfectly for years and is now getting this error.

   Specifically what they told me is that last night they simply moved the
server PC and several workstations from one location to another location on
the network (all in the same building).

  Now, on 1 computer - once they use the software for a few minutes, it
starts producing this error - but only on this 1 PC.

   The "Server" is a windows 64 bit computer with a shared directory with
passwords turned on. The client PC is also Windows 7.

  I suspect that maybe a windows update was run on the client PC or some
other change was made to that PC - all of the other PC's seem to be
operating just fine.

  Any ideas ???

Neil Huhta

Neil,

<< I am using DBISAM version 1 which is a file share version and my customer
was running perfectly for years and is now getting this error.

Specifically what they told me is that last night they simply moved the
server PC and several workstations from one location to another location on
the network (all in the same building). >>

Now, on 1 computer - once they use the software for a few minutes, it starts
producing this error - but only on this 1 PC. >>

It sounds like they've got a bad network cable/card with this one machine
and it isn't able to acquire locks like it should.  If there's a network
issue with file-sharing access (the only type of access that DBISAM 1.x
used), then things like locking may fail.

Tim Young
Elevate Software
www.elevatesoft.com

The problem appears to be solved. Their network guy googled the error and
found a microsoft article that advised him to reinstall the client. Upon
re-installing the client - he claims the errors stopped.

I was suspicious of the Kapersky antivirus software - I exempted the files
from being scanned abot 4 hours after the trouble stopped.

I am very doubtful about a hardware failure - but - as of now the problem
has vanished as quickly as it appeared.

Thank you.


Neil Huhta



"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:8B722F1F-DF9A-4446-86BF-9377B9F18E54@news.elevatesoft.com...
> Neil,
>
> << I am using DBISAM version 1 which is a file share version and my
> customer was running perfectly for years and is now getting this error.
>
> Specifically what they told me is that last night they simply moved the
> server PC and several workstations from one location to another location
> on the network (all in the same building). >>
>
> Now, on 1 computer - once they use the software for a few minutes, it
> starts producing this error - but only on this 1 PC. >>
>
> It sounds like they've got a bad network cable/card with this one machine
> and it isn't able to acquire locks like it should.  If there's a network
> issue with file-sharing access (the only type of access that DBISAM 1.x
> used), then things like locking may fail.
>
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Neil,

<< The problem appears to be solved. Their network guy googled the error and
found a microsoft article that advised him to reinstall the client. Upon
re-installing the client - he claims the errors stopped. >>

Hmm, interesting.  It's certainly possible, of course, but I've never heard
of such a problem being solved by an OS re-install, unless the new OS image
was newer with fixes for the issue.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com