Databases
StackOverflow2013
Postsdbo
PODirectoy.Delete(path, true) -> IOException : the directory is not empty -> Different owners on Win7
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODirectoy.Delete(path, true) -> IOException : the directory is not empty -> Different owners on Win7
    primarykey
    data
    text
    <p>On uninstalling, I get a IOException when trying to delete a directory. 'The directory is not empty'. I tried different methods, listed below, but nothing works. The files that are left behind (and cannot be deleted) have a different owner. Files that can be deleted have owner 'SYSTEM'. Files that throw an exception have owner 'Administrators(PC_Name\Administrators)' 'System' files have been written by the installshield installer (MSI), while the other files are written by my app, launched by installshield and elevated to administrator ...</p> <p>How can I force a delete of this folder / files?</p> <pre><code> //http://stackoverflow.com/questions/329355/cannot-delete-directory-with-directory-deletepath-true public static bool DeleteDirectory(string target_dir) { bool result = false; string[] files = Directory.GetFiles(target_dir); string[] dirs = Directory.GetDirectories(target_dir); foreach (string file in files) { File.SetAttributes(file, FileAttributes.Normal); File.Delete(file); } foreach (string dir in dirs) { DeleteDirectory(dir); } Directory.Delete(target_dir, false); return result; } //http://stackoverflow.com/questions/611921/how-do-i-delete-a-directory-with-read-only-files-in-c private static void DeleteFileSystemInfo(FileSystemInfo fsi) { fsi.Attributes = FileAttributes.Normal; var di = fsi as DirectoryInfo; if (di != null) { foreach (var dirInfo in di.GetFileSystemInfos()) DeleteFileSystemInfo(dirInfo); } fsi.Delete(); } //http://stackoverflow.com/questions/611921/how-do-i-delete-a-directory-with-read-only-files-in-c public static void ForceDeleteDirectory(string path) { DirectoryInfo root; Stack&lt;DirectoryInfo&gt; fols; DirectoryInfo fol; fols = new Stack&lt;DirectoryInfo&gt;(); root = new DirectoryInfo(path); fols.Push(root); while (fols.Count &gt; 0) { fol = fols.Pop(); fol.Attributes = fol.Attributes &amp; ~(FileAttributes.Archive | FileAttributes.ReadOnly | FileAttributes.Hidden); foreach (DirectoryInfo d in fol.GetDirectories()) { fols.Push(d); } foreach (FileInfo f in fol.GetFiles()) { f.Attributes = f.Attributes &amp; ~(FileAttributes.Archive | FileAttributes.ReadOnly | FileAttributes.Hidden); f.Delete(); } } root.Delete(true); } </code></pre> <p>EDIT: Sorry, forgot this :</p> <p>On the folder that is giving problems, on installation, I'm giving the 'Users' account full control :</p> <pre><code> System.Security.Principal.SecurityIdentifier sid = new System.Security.Principal.SecurityIdentifier( System.Security.Principal.WellKnownSidType.BuiltinUsersSid, null); System.Security.Principal.NTAccount acct = sid.Translate(typeof(System.Security.Principal.NTAccount)) as System.Security.Principal.NTAccount; string usr = acct.ToString(); DirectoryInfo info = new DirectoryInfo(dir); DirectorySecurity ds = info.GetAccessControl(); ds.AddAccessRule(new FileSystemAccessRule(usr, FileSystemRights.FullControl, AccessControlType.Allow)); ds.AddAccessRule(new FileSystemAccessRule(usr, FileSystemRights.FullControl, InheritanceFlags.ObjectInherit | InheritanceFlags.ContainerInherit, PropagationFlags.InheritOnly, AccessControlType.Allow)); info.SetAccessControl(ds); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTshepang
    1. USRun CMD
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODirectoy.Delete(path, true) -> IOException : the directory is not empty -> Different owners on Win7
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODirectoy.Delete(path, true) -> IOException : the directory is not empty -> Different owners on Win7
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODirectoy.Delete(path, true) -> IOException : the directory is not empty -> Different owners on Win7
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you doing something weird with the permissions when you install? Normally SYSTEM has rights to delete files, but apparently that's turned off for your install directory.
      singulars
      1. PODirectoy.Delete(path, true) -> IOException : the directory is not empty -> Different owners on Win7
      1. USJoe White
    2. CONothing special as far as I know ..? Everything that can be deleted is installed by installshield. The files that can't be deleted are those that I've written myself during installation..... Even if I right click the file and choose 'Security', both SYSTEM as ADMINISTRATORS have 'Full Control' ??
      singulars
      1. PODirectoy.Delete(path, true) -> IOException : the directory is not empty -> Different owners on Win7
      1. USRun CMD
    3. COHi Joe, sorry forgot to mention I'm giving special permissions on the folder on installation (see question)
      singulars
      1. PODirectoy.Delete(path, true) -> IOException : the directory is not empty -> Different owners on Win7
      1. USRun CMD
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload