Lock Error, When Rebuilding fileblock

[Rob Roberts [TPX]]

Todd,

I don't know of any differences between Windows 2000 and Windows NT4 that
would affect locking. There is the infamous Windows caching problem that
can lead to lock errors, data corruption, and other problems on networked
databases. But that is the same on Windows 2000 as it is on NT4 and
Win9x/ME.

For more information about the caching problem, take a look at corrupt.txt,
located at ftp.turbopower.com/pub/btree/corrupt.txt. Also take a look at an
article in the February, 1999 issue of The Delphi Magazine entitled "Paradox
File Corruption." You can read the article at
http://www.thedelphimagazine.com/samples/Paradox/paradox.htm. To avoid
these kinds of problems, you need to make sure that EVERY machine on your
network that will access your B-Tree Filer fileblocks is set up correctly. I
have a program called NetSafe that lets you easily check your workstations.
You can download it from here: http://www.pcisys.net/~robr/download.htm.

I'm not sure whether this has anything to do with your problem, but it's the
only thing I can think of that might be affecting it.

By the way, when you say that you're getting access denied errors and lock
errors, what IsamError error codes are you referring to?

--Rob [TPX]

"Todd Flora" <tfl...@caiso.com> wrote in message
news:RZvxa7W...@tpsmail01.turbopower.net...
> Hi,
>
> When rebuilding on windows 2000 I have a customer that occassionally gets
an
> access denied error on the datafiles. Also sometimes the system cannot
lock
> the file after 100 tries and complains with a lock error.
>
> This routine has been working for some 10 years now on all previous OS's
> including Novell and NT4. We have verified that all other computers are
off
> and not accessing the files. We also have restarted the server to make
sure
> there were no extraneous locks on the file.
>
> The file is being regenerated but the index file creation portion of the
> rebuild seems to have this problem. The SAV file is gone and the DAT file
is
> the appropriate size but the IX file is not.
>
> Are there any known issues with Windows 2000's file locking mechanism that
> could be causing this problem.
>
> Thanks
>
> Todd
>
>
>

[Todd Flora]

[Rob Roberts [TPX]]

Todd,

> One more question. The corrupt.txt article mentions not needing the
> update to Btree Filer 5.54 if I run netsafe and update the Vredir.vxd.
> Did I read this correctly. I have a dos product that is still using 5.23
> and a windows product using 5.55 that access the data files
> simultaneously. (MSNet network)

If you've ensured that all of your workstations are configured correctly and
your Windows v5.55 app seems to work OK along with your DOS v5.23 app, then
I guess there's no reason that you need to upgrade the DOS app to v5.55.

That's interesting that your two apps using different versions of B-Tree
Filer seem to work fine together. That question comes up here occasionally,
and I always just have to say that I don't know.

--Rob [TPX]

[Todd Flora]

Thanks so much for the help.

I will run netsafe on Monday at the customer site to see if this might be
the problem.

One more question. The corrupt.txt article mentions not needing the update
to Btree Filer 5.54 if I run netsafe and update the Vredir.vxd. Did I read
this correctly. I have a dos product that is still using 5.23 and a windows
product using 5.55 that access the data files simultaneously. (MSNet
network)

I have tried to update the dos product to TP7 and Btree Filer 5.55 without
success. I can't remember what the problem was but if necessary I will try
it again.

Thanks again.

Todd Flora

"Rob Roberts [TPX]" <do...@email.me> wrote in message
news:SRuE7jXn...@tpsmail01.turbopower.net...