9 replies
by lizzy
Hi Leonard,
This seems to be a recurring problem when there are Windows 9x workstations connected to Windows NT technology servers (whether 4.0 or 2K). Please see the following page at an earlier Q&A for more insight:
https://www.techrepublic.com/forumqa/thread_detail.jhtml?thread_id=94147
(remove any spaces from the pasted URL)
I took part in that Q&A, but look at Dave's answer as well. Also, search MS Knowledge Base for these Q articles:
Q278558
Q293793
Q278456
Q272594
Unfortunately, these will probably point you to MS support for a downloadable fix that they may try to charge you for. We have had the same problem here once we went to NT servers and got rid of the Novell. We have applied two fixes (278558 and 293793) aswell as the 3 step shut down patches and still there is sometimes a problem when users access files on the server. I wish I had better help for you than this, but it should get you pointed in the right direction.
by lizzy
by lizzy
by leonardd
Well here is a twist for you all.
Since I could not reproduce the problem at will, Microsoft wanted me to wait until the problem resurfaced. However in the mean time I updated to a new version of CA "InoculateIt" Etrust. This seems to have resolvedall file locking problems as well as the duplicate *.in2 files taht were being created when the file does get locked.
So was it a Virus that was hiding? Did some corrupted files get replaced? Or did it fix a bug in the previous version of InculateIt that CA didn't report (or know about)?
Either way this problem is... for now at least resolved.
Thanks to everyone!
by amrsag
You did not post what version of office you are
using. If some of your users are using Office XP
you need to download Office Service Pack One and
Two and apply them to the XP machines. Office
2000 does not have this problem. Another thing that you might try to do before getting a hold
of Microsoft, is to stop the indexing server
on your NT machine, then have the user try to
save the files. You need to access it through
the console. I think its Start/Programs/Option Pack.
by leonardd
by skottke
When the user is trying to save the file to the network drive and getting the error can the network be accessed in any other way? In other words has the users access to the network been lost and hence the resource is no longer available for the filewrite? I would check for these type of connectivity issues.
Another thought just came to mind - when the user is opening the file is it opening in "read only" mode? This is usually indicated during the open of the file, but not always necessarily. Check the title bar to see if there are any indications of this.
by leonardd
by leonardd
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending