Deleting/Renaming Network Folders : On fail release locks and retry

[meteorquake]

It's actually quite difficult deleting/renaming network folders when open on Everything, a lot of them fail.
I suspect Everything has locks on some of the files, particularly due to thumbnail generation. For example it might report it can't delete/move due to thumbs.db being in use by Everything.

* Can I suggest than when a folder deletion/rename fails, Everything does a scan to see if it is holding any resources within that folder, particularly thumbs and presumably also previews, and to kill them where appropriate and retry the action. Actually it could even report all locks (including external ones) and ask if OK to kill.

David

[void]

It's an issue with the Microsoft IShellItemImageFactory API.

IShellItemImageFactory keeps a handle open to your thumbs.db.

The same issue is present in Windows Explorer.



To disable IShellItemImageFactory in Everything:

• In Everything 1.5, from the Tools menu, click Options.
• Click the Advanced tab on the left.
• To the right of Show settings containing, search for:
  shell image
• Select: shell_item_image_factory
• Set the value to: false
• Click OK.

When disabled, Everything will load thumbnails directly instead of from cache.

[tkabat]

We are experiencing the same issue, both within Explorer and Everything. It's impacted across multiple versions of Everything.

We've tested multiple ways:

>Set shell_item_image_factory to false. When creating a new file in a network share, all computers with Everything including the test computer show that the file is open with a state of Read.

>We unchecked the Attempt to monitor changes option on one mapped drive "folder." This seem to work with our test user, however the new file was not searchable until the next rescan ran.

>Closing Everything on the computer also fixed the issue but is not the permanent fix.

Any thoughts would be helpful.

[therube]

both within Explorer and Everything

Just noting if that is the case, that W/E also causes the same issue, then it most likely is not an Everything issue, per se.
(That said, maybe there is something Everything that can be done ?)


Anything particular with your network, its' setup?
And what type of Indexing are you dealing with; NTFS, Network Drives, Network Indexes... ?

[tkabat]

In Everything we set up the network drives under the Folders index.

On our file servers, we can watch what users are opening folders/files. When we create a new folder/file we can see that all computers running Everything are opening the folder in read mode. This prevents users from deleting/renaming/moving/etc in either Explorer or Everything. I have tested closing Everything on multiple computers, when we create a new folder those users are no longer showing up in the open files list.

From what I can tell, Everything checks out new folders/files immediatley which "locks" the folder/file for about 15 - 20 minutes, then we can see all the open files on the server release.