(Solved) Everything client fails to communicate with service named pipe

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
phanta
Posts: 2
Joined: Wed Nov 25, 2020 5:30 pm

(Solved) Everything client fails to communicate with service named pipe

Post by phanta »

I've installed everything on my shiny new Win10 laptop via scoop, and I've enabled the everything service. However, when I open the search UI, the status bar just displays "Creating database..." forever, and no files are ever displayed. If I try to open the "NTFS" tab in the options dialog, the entire application hangs indefinitely.

Enabling debug logging on both the service and the client, I see that the client tries to talk with the service, but never succeeds.
Here's the client log after just opening the client and letting it sit for a few seconds:

Code: Select all

ole initialize: 00000000
create mutex
sys img list 0000000000c2f910 0000000000c34cd0 3 0
default font MS Shell Dlg 2 -12
load everything icon
bookmarks
filters
search history
set hook
create tray
Everything
Version 1.4.1.992 (x64)
Windows NT 6.2
Processors 12
IsAdmin 0
AppData 0
Service 2
cmdline "C:\Users\(redacted)\scoop\apps\everything\current\Everything.exe" -debug
db_load
config volume: \\?\Volume{} | C: |  | 1
add volume: \\?\Volume{} | C: |
VEH 12900000
volume \\?\Volume{}: drive type 3
GetVolumePathNamesForVolumeName 234
GetVolumePathNamesForVolumeName C:
add found ntfs volume: \\?\Volume{} | C: |  | 0000000000c249e0
volume \\?\Volume{}: drive type 3
GetVolumePathNamesForVolumeName 234
volume \\?\Volume{}: drive type 3
GetVolumePathNamesForVolumeName 234
QueryDosDevice C: \Device\HarddiskVolume3
volume: \\?\Volume{} | C: |  found 1
ntfs volume create list 0.002680 seconds
new thread (0)
ui_create 0000000000000000 0000000000c1bc00
Loading structure 00002505: 42336 folders, 254714 files...
_db_index_add 0: 0, 0000000000c20cf0
convert all folder parent indexes into folder parent folders 0.000309 seconds
14 26
initheader
initsearch
parts
setmode
size
sw
WM_ACTIVATE 0000000000000001 0000000000000000, lastfocus 0000000000000000, current focus 0000000000000000
unable to set focus 0
redraw
cached oneclickactivate 0
enter setfocus
leave setfocus
ui_create leave 0000000000c1bc00
enter main loop
new results 0
fs out of date 0
fs NTFS C: 1
loaded 0 of 0 changes in 0.000546 seconds
recent changes array memory usage: 0 bytes
loaded run history in 0.000063 seconds
run history data count: 0, data: 0 bytes
run history ptr count: 0
total run history memory usage: 0 bytes
update index C:
open volume \\?\Volume{}
CreateFileW(): GetLastError(): 5: Failed to open volume \\?\Volume{}
opened -1 0.000526
new thread (1)
Here's the service log; it seems to show that the connection is seen by the service, but gets rejected:

Code: Select all

Everything
Version 1.4.1.992 (x64)
Windows NT 6.2
Processors 12
IsAdmin 1
AppData 0
Service 2
cmdline "C:\Users\(redacted)\scoop\apps\everything\current\Everything.exe" -isrunas -svc -debug -verbose
StartServiceCtrlDispatcher Everything
_service_server_main
createnamedpipe \\.\PIPE\Everything Service
awake
connect...
sleep 2 0
awake
connected
connection not allowed.
connect...
sleep 2 0
I've tried writing to and reading from the pipe via the command line, but both fail, logging "connection not allowed" in the same way, even when the terminal window is elevated. I've also tried messing around with setting permissive security descriptors and using different pipe names, but nothing changes the outcome in any way. I have no idea what's going on...
Last edited by void on Fri Nov 27, 2020 5:49 am, edited 2 times in total.
Reason: removed volume guids
void
Developer
Posts: 16678
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything client fails to communicate with service named pipe

Post by void »

connected
connection not allowed.
This can occur if the client executable path and filename does not match the service executable path and filename.
Even though they appear to match in your case, Everything is detecting the client executable path and filename as something different.

Please try the latest nightly build for a fix.
phanta
Posts: 2
Joined: Wed Nov 25, 2020 5:30 pm

Re: Everything client fails to communicate with service named pipe

Post by phanta »

I've uninstalled the scoop-managed version and manually installed the nightly, and the problem seems to have vanished. Nice!
Post Reply