Walter Meester
HoogkarspelNetherlands
>>>>It has been reported to me that the tables appear still open on the file server after a user has closed the application (in .EXE form). Does anyone know why this happens and how it can be prevented?
>>>>
>>>
>>>Apply NT SP5 or later to the server - this is a known issue corrected in NT SP5.
>>
>>Ed, I'm at SP6 here, and I still see quite a delay before the files are released after exiting an app. Is their a registry setting or ? that controls when these files are released? I just walked over to a client machine, verified the application was shut down, yet Server Manager still should the client holding several tables open. Any ideas?
>
>Jim,
>
>This a known mechanism in NT. The server holds the tables open for performance reasons in case the files is opened again shortly after it is closed. IOW this is NOT a bug. In general this will not lead to any problems. But if it is, you can disable it by adding/modifying some registry settings. See Article ID: Q134637 of the MS knowledgebase for more explanation of controlling the way the Server caches files. Thought this document is written for NT 3.5 it also applies to NT 4.0
>
>Walter,
Ahhh, the OpLocks thing. I suspected as much. Thanks for the pointer, Walter. I have directed a query to MS Direct Access to see why different workstations seem to keep files open longer than others.
Jim.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only