7 replies
From Novell:
Occasionally, a file will be held open by the os or an application. In most cases there are only two choices to resolve this: Unload the nlm that has the file open, or down the file server. This often NOT an acceptable solution.
The server, in all cases, is up and running... only one user is inoperable because of the open file, and yet the solution impacts the whole population of users connected to this server.
Basicly the process/application that they were using didn't unlock the file yet. I had experience this last year but I don't remember the exact steps. I know we reinstalled the drivers of the network card, and updated the novell client. I don't remember if we what we did at the novellserver side. I would suggest to get a the lastest patch for netware 5.
Leopold
by thorpe322
We've got the server all patched up to the latest and greatest. Our server admin is tops about that. I'll look into NIC driver updates. We're also running the 4.9 Novell client. Which I do believe is the latest release.
by techkid
by thorpe322
Poster rated this answer.
are the applications also updated , for example office 2000 sp3, and other applications that you might be using.
If they get the message file is in use, you should be able to take look at the files on the server to check if indeed the file is in use yet and by whom.
and last item that I can think of if it is the workstation to is to check the eventviewer of the pc's if they don't have error or warning messages.
Leopold
by thorpe322
Poster rated this answer.
by thorpe322
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending