Cannot delete files from Win 2000/XP

[cthreepo]

Does anyone know why I cannot delete files (such as Word, EXCEL etc), from the server using using either Win 2000 or Win XP?

I am running Netware 5.1 SP5.

I have no problem deleteing files from a Win 98 client PC.

Any ideas?

Thanks.

let's help one another, not hinder.

 

[TheLad]

What version of the NetWare Client are you running? Have you got File Caching switched off on the server: SET FILE CACHING ENABLED = OFF

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[cthreepo]

I am using Client 4.83 SP1.
I tried to enter what you said (SET FILE CACHING ENABLED = OFF ), and it returns UNKNOWN SET PARAMETER NAME.

Any ideas?

Thanks

let's help one another, not hinder.

 

[TheLad]

Sorry....

SET CLIENT FILE CACHING ENABLED = OFF

Apologies.

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[cthreepo]

No probs.

Have set it to OFF, but still the problem is there.

Cannot delete a simple MS Word document due to: "Access denied. The file is read only or is use by someone else etc..."

This does not happen from a Win 95/98 operating systems.

Any more ideas?


let's help one another, not hinder.

 

[rjs]

Have you tried to delete from a CMD prompt on a 2000 or XP machine?

I assume from the above this problem is from ANY 2000 or XP machine, not just a select few.

 

[terry712]

have you browsed to the file through monitor and see who has it open

i've never seen it - what client?

is it 4.83 sp2

 

[marvhuffaker]

I see this same thing on XP all the time and it is really annoying. XP does something to the files that causes the files to be open when they're not really open. I haven't been able to figure out how to turn it off..

For example, if you click on a network file in explorer... even though you haven't actually opened it, XP thinks you want to preview it, so it opens it for reading to get a preview or details about it. So then by the time it figures out you've clicked delete, it won't delete it because it (XP) has the file open. The only thing I can figure out to do to get around it, is to select another file (to clear the previous file lock), then reselect the original file, press delete really fast before it opens it for preview. Sometimes it works, and sometimes i have to do it a few times before I get it.

I found a reg hack that turned some of the File preview features off, but apparently it doesn't shut it off completely. Furthermore, It doesn't ever want to be consistent, but I've seen it on several different companies systems, not just isolated to one server or one workstation.

If anyone finds the answer, I would love to hear about it.

marv



Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[dnw99]

From what I can ascertain this is an XP problem not a Novell one. We get the same problem here on a Win2000 server with XP clients.

I haven't found a fix yet, but have found that you can delete the Word file from within the Open File Dialog box while Word is open.

To clarify, Open Word (with no doc open); Hit the File->Open menu (or open folder icon); find the word file you can't delete and hit the X button.

David

 

[marvhuffaker]

It's great that you can buy an add on program like Word to handle the basic Windows file management functions.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[dsimpaired]

If Client file caching is turned off at the server would the client properties have any effect? Under the client properties I sometimes have to go to advanced properties and make sure that file caching is switched off when I have strange file errors on some database apps that we run. Not sure if this is the same but I would just double check the client setting????

 

[miggyal]

I have been having the same problem, checked the open files on the remote server etc.... and nobody had the file open.

I then turned off the file caching on the advanced tab of properties of the local client and that did solve the problem.