>regarding the categories for OS, Network - it's really 2008 server r2 for both, VFP on terminal server.
>
>We have two separate errors in two separate terminal server environments:
>
>1) On an app that hasn't changed in a really long time, nor the OS or terminal server. Upon opening a form we got
>'Error reading file'. If we went into any terminal server session from any desktop or thin client, and tried to open the same form in the app, we got the error. But if we went into the app from a regular desktop non/TS environment, the form opened fine.
>
>I kicked everyone off the TS and restarted it, and the problem went away. Any ideas? Any MS updates affecting TS environment?
>
>
>2) On another Terminal Server environment, we just setup a new vmware virtual machine as a TS - windows 2008 server r2
>file server for the vfp app is also win2008 r2. There is a weekly batch routine that one user needs to run - close orders - requires that everyone be off the system - and needs to gain exclusive access to a table. All users exit - for all intents and purposes it looks like there are no open files anywhere on the system. When the user tries to close from within a TS session, it tell him the file is in use by another (I think that's the message - that's what I was told - in any event the lock can't be obtained) However, the same as #1 above, if the user starts the VFP app from a regular desktop non/TS environment, he is able to get the lock and proceed.
>
>This environment (item #2) was just migrated to a new VMWare environment and new TS. However, this problem with the exclusive lock is longstanding - had it in the previous environment - not vmware, but still 2008 server r2.
>
>A year and a half ago, in this non vm environment, wary of 'SMB2' issues, I had disabled SMB2 and did a bunch of other stuff supposedly related to potential issues - but the exclusive lock issue still remained. In the new TS environment, I haven't disabled SMB2.

I don't have any answers, but if you can't obtain a lock, that implies the OS thinks someone else has the file open, with or without a lock. Have you checked to see who has the file(s) open when the problem occurs? http://www.techrepublic.com/blog/datacenter/server-2008-manage-open-files-with-share-and-storage-management/315