Problem deleting folders

E

Eric

Hello, hope anybody can help with this.

We're having problems deleting folders because they
contain files with ~ (tilde) in the filename.
The place of the ~ doesn't seem to matter.

Most of the times it is possible to delete the file, but
the directory will refuse to delete/move/rename without
the server being rebooted.

The problem is occuring on Windows 2000 servers, mostly
fileservers, but when restoring data from the fileservers
to a backup server which is not a domain controller (and
also running 2000 Server) the same problem occurs.

On the backup server I've been testing with this a bit.
If you make a new folder and make a new file in it, for
example a word document and try to delete it, no problem.

If you make a new folder and make a new file and rename
the file to contain a ~ and try to delete the folder it
will say:
Error deleting file or folder
Cannot delete filename: There has been a sharing
violation. The source or destination file may be in use.

If you delete the file from the folder, the folder
remains 'locked', after rebooting the server the folder
can be deleted.

I have confirmed that there are no sessions holding the
files open and verified that the problem is not rights
related (logged on as administrator and have also taken
ownership of files/directories and set rights full to
everyone).

Servers are running on Compaq/HP hardware, running
Windows 2000 Server (US) with SP4 and up-to-date, NTFS
partitions. Most but not all are domain controllers.
The PDC emulator does not have the problem.
The domain is in mixed mode.

Couldn't find much helpful on the Microsoft KB or via
search engine.

I've tried disabling 8dot3 name creation but that didn't
solve the problem either.

Some of the filepaths tend to be pretty long (sometimes
longer than 255 characters), but it also happens when
testing with normal filepaths.

All tests done on the server were conducted via Terminal
Server connection or whilst directly on the console.

Most workstations are XP with Office 2000.

As a workaround we're configuring Word to place ~*.doc
temporary files on the local drive instead of on the
Network. But as said that is only to prevent the problem
from occuring, not resolving it.

We have tried filechecks, defragmenting and using
software to check for processes locking the
files/directories but they revealed nothing out of the
ordinary.

Also tried closing the explorer process via task manager
and trying to remove the directory via dos but that also
was without success.

If anyone has any ideas or has seen this problem before
help is appreciated.

Regards,

Eric
 
G

Guest

This is not a total solution for your problems, but if you happen to be trying to use the 16-bit version of the console (Command.com) rather than the 32-bit version (cmd.exe), then you will have to deal with 8.3 file names. best thing to do is use the windows explorer to delete the files, or the cmd.exe utility. try not to use the COmmand.com utility, is much more difficult

Brandon Dedman
MCSA
 
E

Eric

The problems occur via the Windows explorer, both on the
server console or from a workstation via a file share.

I've tried stopping the process "explorer" and tried
deleting the folders with cmd.exe but that didn't help
unfortunately. I never use command.com.

Tildes commonly occur when opening programs or documents
from a network share, the system will place a temporary
reference in the directory and if for example Word would
crash the file would be orphaned.
We have a possibility to put the temporary Office files
on a local drive (via the registry) but not all programs
support that. And it would still be a workaround.

Eric
MCP MCSA MCSE MCDBA etc
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top