Hello All,
Love the software overall. We are having an issue with one client though. He's got 4 mapped drives indexed on his "Everything" client. For some reason every morning though it's like his connection is broken and then the search results don't work right. He will see a file is there, it will be in the location it says, but it will give him the specified path does not exist error. I've attached a screenshot of what it looks like. Any assistance with this is greatly appreciated.
The Specified Path Does Not Exist Error
Re: The Specified Path Does Not Exist Error
Press Ctrl + ~ in Everything to show the debug console.
What is displayed in the debug console after this error window has appeared?
Can you right click the files, does it show a context menu?
What is displayed in the debug console after this error window has appeared?
Can you right click the files, does it show a context menu?
-
- Posts: 2
- Joined: Sun Mar 29, 2015 6:46 pm
Re: The Specified Path Does Not Exist Error
I have the same problem but only on network drives. I used to be able to launch Foxit to read a pdf file by double clicking on the file name in "everything". Now I get the "Specified Path Does Not Exist". If I open Foxit I can drag the file from "everything" to Foxit and it works. Similarly mp3 files need to be dragged from "everything" to VLC.
The problem started a couple of weeks ago so, thinking my copy of "everything" had been corrupted I downloaded the latest 64 bit version. The problem persists.
Right clicking on a network drive file produces a 7 item context menu - on a local drive file the menu has over 20 entries.
I cannot get a debug console by using ctrl + ~ but hope the above clues will help identify what has caused the change in operation. I can live with it but prefer the original version!
Thanks in advance.
The problem started a couple of weeks ago so, thinking my copy of "everything" had been corrupted I downloaded the latest 64 bit version. The problem persists.
Right clicking on a network drive file produces a 7 item context menu - on a local drive file the menu has over 20 entries.
I cannot get a debug console by using ctrl + ~ but hope the above clues will help identify what has caused the change in operation. I can live with it but prefer the original version!
Thanks in advance.
Re: The Specified Path Does Not Exist Error
@duncangray, that sounds like a combination of permissions & 32 vs 64-bit context-menu ... crapola. (To me that's a good way of putting it.)
Oh, you can run into issues permission-wise if you were running Everything "As Administrator", yet your application (say mp3 player) was running as a Limited user.
And then 32 vs 64-bit. (Mostly) a 32-bit applications context menu items will only show in another 32-bit application, like Everything x86. (Mostly) a 64-bit applications context menu items will only show in another 64-bit application like Everything x64. In some cases a particular program provides some sort of work-around so that its context menu items are seen both 32 & 64-bit versions of another program. Sometimes you would need to install both 32 & 64-bit versions of a particular program for its context menu's to show up in the respective version of Everything (or some other program).
Another issue that can crop up, is a "too long path" issue. In general, Everything (Windows ?) is good for ~xxx character pathnames, but other applications may be limited to ~260.
(And while we're here, I'll just throw this in, You cannot delete a file or a folder on an NTFS file system volume and also Naming Files, Paths, and Namespaces.)
Oh, you can run into issues permission-wise if you were running Everything "As Administrator", yet your application (say mp3 player) was running as a Limited user.
And then 32 vs 64-bit. (Mostly) a 32-bit applications context menu items will only show in another 32-bit application, like Everything x86. (Mostly) a 64-bit applications context menu items will only show in another 64-bit application like Everything x64. In some cases a particular program provides some sort of work-around so that its context menu items are seen both 32 & 64-bit versions of another program. Sometimes you would need to install both 32 & 64-bit versions of a particular program for its context menu's to show up in the respective version of Everything (or some other program).
Another issue that can crop up, is a "too long path" issue. In general, Everything (Windows ?) is good for ~xxx character pathnames, but other applications may be limited to ~260.
(And while we're here, I'll just throw this in, You cannot delete a file or a folder on an NTFS file system volume and also Naming Files, Paths, and Namespaces.)
-
- Posts: 2
- Joined: Sun Mar 29, 2015 6:46 pm
Re: The Specified Path Does Not Exist Error
@therube
Thanks for your suggestions but I suspect I may have misled or perhaps just posted insufficient information.
Everything/64 is being run as admin as is VLC. The 7 item context menu is for PIC18F87K22.pdf on any network NAS drive (W:, X:) but exactly the same file on any local disc (C:, E:) in the same Everything/64 window has a 20 item context menu.
The full path on the local drive is about 46 characters and only 17 characters on the network drives i.e. Everything launches the application with a long path on a local drive but not a short one on an external drive.
This all worked with Everything/32 until a few weeks ago when I found I could no longer launch the application by double clicking on the file name in the Everything/32 window and changing to 64 bit doesn't seem to have corrected the problem. The only thing that I am aware has changed is the dreaded Windows 7/64 Updates but I was hoping it wasn't that and was something I could tweak instead.
Thanks for your suggestions but I suspect I may have misled or perhaps just posted insufficient information.
Everything/64 is being run as admin as is VLC. The 7 item context menu is for PIC18F87K22.pdf on any network NAS drive (W:, X:) but exactly the same file on any local disc (C:, E:) in the same Everything/64 window has a 20 item context menu.
The full path on the local drive is about 46 characters and only 17 characters on the network drives i.e. Everything launches the application with a long path on a local drive but not a short one on an external drive.
This all worked with Everything/32 until a few weeks ago when I found I could no longer launch the application by double clicking on the file name in the Everything/32 window and changing to 64 bit doesn't seem to have corrected the problem. The only thing that I am aware has changed is the dreaded Windows 7/64 Updates but I was hoping it wasn't that and was something I could tweak instead.
Re: The Specified Path Does Not Exist Error
I ran the debugging with this issue happening and it is attached. Any help is appreciated.
- Attachments
-
- SearchEverything.png (38.16 KiB) Viewed 5579 times
Re: The Specified Path Does Not Exist Error
Thanks for the debug output.
Related:
https://social.msdn.microsoft.com/Forum ... wssecurity
It could be a permission issue, does running Everything with lower privileges help?
Related:
https://social.msdn.microsoft.com/Forum ... wssecurity
It could be a permission issue, does running Everything with lower privileges help?
Re: The Specified Path Does Not Exist Error
I reinstalled the software, was having different issues. I would save which network drives and upon reboot nothing was indexed. Reinstalled again and now it's working fine.