Hi Jim,

It locks different files, there does not seem to be a pattern in it.

>Nick,
>
>As you know, others her have had problems with AV software, and it seems to me that it was usually in concert with newer, faster configurations. I'd guess that the new system has newer AV software on it.
>
>Even if policy disallows stopping it, it should allow inspecting/revising its 'configuration' to ensure that VFP-related files are exempted from processing by it.
>
>And if it is the exact same AV software, maybe it is the problem. Maybe it has compatibility issues with the new OS.
>
>Do you know which file, and is it always the same file? If it is, maybe it could be exempted specifically, at least for verification purposes.
>
>good luck
>
>
>>No, we cannot disable the antivirus there - it is against the corporate policy.
>>The existing production server works fine with the same antivirus.
>>
>>>Hi Nick,
>>>
>>>Did you try to disable Antivirus software on this computer and did it help?
>>>
>>>>Hi All,
>>>>
>>>>Our Application Support came to me to ask what could be wrong. We have a big FP 2.5 DOS app which works for about 8-9 years. They decided to test it on the new server. It is Pentium 3 dual processor 1 Ghz machine with 512 mb RAM running Windows 2000 Server, and the data are located on Compaq Storage Area Network.
>>>>
>>>>What happens is that sometimes (often enough) they get Error 1705 - File Access is Denied (all tables, naturally, are shared). Restarting the workstation does not release the file, only rebooting the server helps.
>>>>
>>>>All application settings (config.fp and .nt, etc.) are identical to those on the running production server, which is Pentium single processor 333 MHz, Windows NT 4.0 Service Pack 3. All production data are located on local drives on this server.
>>>>
>>>>Anybody have any ideas? Could it be related to dual processor configuration?