Good morning - we have an application running on a Windows 2000 Advanced Server. The application is running on a Scheduler and probably crashed sometime during the night although I don't see anything saying that it bombed. Right now I can not open any of the tables that are used in the application either shared or exclusive so it appears that the application still has those files open. Yet if I go to MY Computer, Manage, Shared Folder, Open Files none of the files show as being open. The only solution is to reboot the server which would cause a lot of other issuse. Thanks so much, Pete
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Running 2.6 in a WIN 2K Advanced Server
- Thread starter pmbroh
- Start date
More likely the files got corrupted rather than being in use. You will probably have to repair them or at least recreate the indexes for them.
Do a search in this forum and you will find plenty of posts on how to do that.
-Dave Summers-
![[cheers]](/data/assets/smilies/cheers.gif "[cheers] [cheers]")
Even more Fox stuff at:
Do a search in this forum and you will find plenty of posts on how to do that.
-Dave Summers-
Even more Fox stuff at:
- Thread starter
- #3
Thanks Dave,
It is definately not an index issue when you get file access denied on all 50 tables in the database. The scheduler kicks off an application at night that opens all tables in an exclusive mode prior to doing data updating.
Thanks Pete
It is definately not an index issue when you get file access denied on all 50 tables in the database. The scheduler kicks off an application at night that opens all tables in an exclusive mode prior to doing data updating.
Thanks Pete
As I recall, the shared files only show as being opened by connections to the server, not the server itself. I could be mistaken, but that's the way it seems to me.
It sounds like you need to check into the logs a little or something to see if you can determine the cause of the crash. Maybe add more error reporting in the app which would write to an error log for the app.
You may also need to kill the tasks NTVDM/wowexec etc. associated with fox to get it to close the files.
Also, you could always use a 3rd party utility to close open files such as this one:
I wrote a utility and put it on my web site that does the same thing, but it requires VFP 7 or higher.
Rebooting the server shouldn't be an option.
-Dave Summers-
Even more Fox stuff at:
It sounds like you need to check into the logs a little or something to see if you can determine the cause of the crash. Maybe add more error reporting in the app which would write to an error log for the app.
You may also need to kill the tasks NTVDM/wowexec etc. associated with fox to get it to close the files.
Also, you could always use a 3rd party utility to close open files such as this one:
I wrote a utility and put it on my web site that does the same thing, but it requires VFP 7 or higher.
Rebooting the server shouldn't be an option.
-Dave Summers-
Even more Fox stuff at:
- Status
Similar threads
