File is in use by another

Since converting many of our applications to VFP8.0 from
VFP6.0, we are getting persistent "File is in use by
another" errors when USEing a file, when the file is
definitely not in use, excl is off etc etc. Usually trying
again immediately allows it to open OK!!!!!
This has happened across several unrelated applications on
various platforms. We have both Novell and Win2K servers,
with both XP and NT4 clients. Unfortunately we do not have
sufficient XP clients to determine whether an XP client
resolves this issue - but I doubt it. We also have vfp8
applications where the tables are still in Foxpro 2.6
format, some with tables in VFP6.0 format and some with
tables in VFP8.0 format. Happens across all when app is
VFP8.0. Revert back to 6.0 with everything else the same
and the problem goes away.

I believe this to be a bug in VFP8.0. I have seen similar
complaints from others on various forums, but no one has
come up with an answer as yet.

Any help appreciated.

Maybe next service pack this will be fixed....

And while I'm moaning - anyone know of any fix yet for the
dropped table handles issues with VFP apps running on
terminal server when data is not on the Terminal server
drive?

Regards,
Brian Wood

Rolf
Sun Nov 30 15:11:00 CST 2003

There is a fix for this one.
Microsoft doesn't want anyone to download it.
You will have to call them to get it.


> And while I'm moaning - anyone know of any fix yet for the
> dropped table handles issues with VFP apps running on
> terminal server when data is not on the Terminal server
> drive?
>
> Regards,
> Brian Wood

John
Sun Nov 30 15:23:08 CST 2003

I've seen this happen with Novel 5 servers, and the current 2k/XP Novell
client (4.90). The server will have "OpLock" errors after it runs out of
file locks and VFP apps running on the network will start getting error
messages, but not all workstation, just the last users to log onto the
Novell server. I've only seen it happen to VFP 7&8 applications, mostly 8
though. All apps are commercial apps on the market and I've seen it happen
with about 5 of them.

Downgrading to the previous novell client (4.83) that does not have the new
Opportunist Locking level 2 capability fixed the problem. A work around
(temp of course) is to raise the OpLock file settings on the Novell server,
but eventually it will run out and give errors again under high usage. It
seems the server will free the files after a couple of days or so.

You may also get 'Windows is currently working with a file' message when
shutting down XP once in a while.

John

John
Sun Nov 30 15:25:01 CST 2003

Oh, I should mention updating to the current 5.x service pack on the server
should fix the problem as well, but I haven't tried it.

John

"John Jacques" <auto.man@verizon.net> wrote in message
news:0dtyb.18511$lF6.15699@nwrdny01.gnilink.net...
> I've seen this happen with Novel 5 servers, and the current 2k/XP Novell
> client (4.90). The server will have "OpLock" errors after it runs out of
> file locks and VFP apps running on the network will start getting error
> messages, but not all workstation, just the last users to log onto the
> Novell server. I've only seen it happen to VFP 7&8 applications, mostly 8
> though. All apps are commercial apps on the market and I've seen it happen
> with about 5 of them.
>
> Downgrading to the previous novell client (4.83) that does not have the
new
> Opportunist Locking level 2 capability fixed the problem. A work around
> (temp of course) is to raise the OpLock file settings on the Novell
server,
> but eventually it will run out and give errors again under high usage. It
> seems the server will free the files after a couple of days or so.
>
> You may also get 'Windows is currently working with a file' message when
> shutting down XP once in a while.
>
> John
>
>

Brian
Sun Nov 30 15:41:42 CST 2003

Thanks for the response.
We are "mostly" using NT4 Workstation with Novell Client
4.81 so that would suggest we are dealing with a
different, but perhaps related issue. It is also happening
with our Win2K servers (with NT4 clients).
Regards,
Brian

>-----Original Message-----
>I've seen this happen with Novel 5 servers, and the
current 2k/XP Novell
>client (4.90). The server will have "OpLock" errors after
it runs out of
>file locks and VFP apps running on the network will start
getting error
>messages, but not all workstation, just the last users to
log onto the
>Novell server. I've only seen it happen to VFP 7&8
applications, mostly 8
>though. All apps are commercial apps on the market and
I've seen it happen
>with about 5 of them.
>
>Downgrading to the previous novell client (4.83) that
does not have the new
>Opportunist Locking level 2 capability fixed the problem.
A work around
>(temp of course) is to raise the OpLock file settings on
the Novell server,
>but eventually it will run out and give errors again
under high usage. It
>seems the server will free the files after a couple of
days or so.
>
>You may also get 'Windows is currently working with a
file' message when
>shutting down XP once in a while.
>
>John
>
>
>.
>

anonymous
Sun Nov 30 15:42:01 CST 2003

Thanks for the post. Will get onto them!
Brian
>-----Original Message-----
>There is a fix for this one.
>Microsoft doesn't want anyone to download it.
>You will have to call them to get it.
>
>
>> And while I'm moaning - anyone know of any fix yet for
the
>> dropped table handles issues with VFP apps running on
>> terminal server when data is not on the Terminal server
>> drive?
>>
>> Regards,
>> Brian Wood
>
>
>.
>

Carsten
Mon Dec 01 02:31:48 CST 2003

Brian,

we had similar problems (mostley when accessing huge tables).
The problem was the new switch "SET TABLEVALIDATE"
Default is 3 which means that VFP tries to check RecCount() upon opening
tables and appending new records. To do that, it needs to lock the
table-header.
We changed the switch to 2 (Validate record count when appending or
inserting records and writing them to disk.), and solved the problem.
Please refer to the help (and the SP1-Docs) for more info on SET
TABLEVALIDATE.

I hope it helpes.

Cheers
Carsten


"Brian Wood" <anonymous@discussions.microsoft.com> schrieb im Newsbeitrag
news:9e8601c3b780$0142ae70$a601280a@phx.gbl...
> Since converting many of our applications to VFP8.0 from
> VFP6.0, we are getting persistent "File is in use by
> another" errors when USEing a file, when the file is
> definitely not in use, excl is off etc etc. Usually trying
> again immediately allows it to open OK!!!!!
> This has happened across several unrelated applications on
> various platforms. We have both Novell and Win2K servers,
> with both XP and NT4 clients. Unfortunately we do not have
> sufficient XP clients to determine whether an XP client
> resolves this issue - but I doubt it. We also have vfp8
> applications where the tables are still in Foxpro 2.6
> format, some with tables in VFP6.0 format and some with
> tables in VFP8.0 format. Happens across all when app is
> VFP8.0. Revert back to 6.0 with everything else the same
> and the problem goes away.
>
> I believe this to be a bug in VFP8.0. I have seen similar
> complaints from others on various forums, but no one has
> come up with an answer as yet.
>
> Any help appreciated.
>
> Maybe next service pack this will be fixed....
>
> And while I'm moaning - anyone know of any fix yet for the
> dropped table handles issues with VFP apps running on
> terminal server when data is not on the Terminal server
> drive?
>
> Regards,
> Brian Wood

PAul
Mon Dec 01 11:45:17 CST 2003

> And while I'm moaning - anyone know of any fix yet for the
> dropped table handles issues with VFP apps running on
> terminal server when data is not on the Terminal server
> drive?

Yes, it's a hotfix because it's not made it into a release yet.
KB article 818528

anonymous
Tue Dec 02 16:12:49 CST 2003

You have saved my job Carsten.
Many thanks
Brian
>-----Original Message-----
>Brian,
>
>we had similar problems (mostley when accessing huge
tables).
>The problem was the new switch "SET TABLEVALIDATE"
>Default is 3 which means that VFP tries to check RecCount
() upon opening
>tables and appending new records. To do that, it needs to
lock the
>table-header.
>We changed the switch to 2 (Validate record count when
appending or
>inserting records and writing them to disk.), and solved
the problem.
>Please refer to the help (and the SP1-Docs) for more info
on SET
>TABLEVALIDATE.
>
>I hope it helpes.
>
>Cheers
>Carsten
>
>
>"Brian Wood" <anonymous@discussions.microsoft.com>
schrieb im Newsbeitrag
>news:9e8601c3b780$0142ae70$a601280a@phx.gbl...
>> Since converting many of our applications to VFP8.0 from
>> VFP6.0, we are getting persistent "File is in use by
>> another" errors when USEing a file, when the file is
>> definitely not in use, excl is off etc etc. Usually
trying
>> again immediately allows it to open OK!!!!!
>> This has happened across several unrelated applications
on
>> various platforms. We have both Novell and Win2K
servers,
>> with both XP and NT4 clients. Unfortunately we do not
have
>> sufficient XP clients to determine whether an XP client
>> resolves this issue - but I doubt it. We also have vfp8
>> applications where the tables are still in Foxpro 2.6
>> format, some with tables in VFP6.0 format and some with
>> tables in VFP8.0 format. Happens across all when app is
>> VFP8.0. Revert back to 6.0 with everything else the same
>> and the problem goes away.
>>
>> I believe this to be a bug in VFP8.0. I have seen
similar
>> complaints from others on various forums, but no one has
>> come up with an answer as yet.
>>
>> Any help appreciated.
>>
>> Maybe next service pack this will be fixed....
>>
>> And while I'm moaning - anyone know of any fix yet for
the
>> dropped table handles issues with VFP apps running on
>> terminal server when data is not on the Terminal server
>> drive?
>>
>> Regards,
>> Brian Wood
>
>
>.
>

anonymous
Tue Dec 02 16:13:38 CST 2003

Thanks, have got my grubbly little hands on the patch now
and am currently testing.
Cheers
Brian
>-----Original Message-----
>> And while I'm moaning - anyone know of any fix yet for
the
>> dropped table handles issues with VFP apps running on
>> terminal server when data is not on the Terminal server
>> drive?
>
>Yes, it's a hotfix because it's not made it into a
release yet.
>KB article 818528
>
>
>.
>