One of the Drive Partition Can't be Index in Alpha .1357a

Found a bug in "Everything"? report it here
Post Reply
rabbit_says
Posts: 15
Joined: Tue Mar 19, 2019 12:40 pm

One of the Drive Partition Can't be Index in Alpha .1357a

Post by rabbit_says »

Here is the scenerio,

I have installed Version 1.5.0.1357a (x64).
I have 2 SATA Drives and 1 nvme with 5 Partitions more. So far every partition can be index but one partitions is giving the error "Access denied: Install the Everything service or run as administrator to index this volume."

Only way to index is running the everything in admin. Indexing process in admin also doesn't work. Reinstalling also doesn't help.

FYR here is the drive structure, everything is installed in C drive and the highlighted drive F can't be index others are working fine.
Image

https://imgur.com/a/N0SPnzs
therube
Posts: 4668
Joined: Thu Sep 03, 2009 6:48 pm

Re: One of the Drive Partition Can't be Index in Alpha .1357a

Post by therube »

Post, Help | Troubleshooting information?
(You may want to blank out the 'ntfs_volumes=[{"path:' part - except for that dealing with F:, though you could "fiddle" with the volume id display.)
Indexing process in admin also doesn't work.
Explain?

And did you try installing the Everything Service (which essentially runs "as admin", but leaves the Everything client itself running at a user level)?
rabbit_says
Posts: 15
Joined: Tue Mar 19, 2019 12:40 pm

Re: One of the Drive Partition Can't be Index in Alpha .1357a

Post by rabbit_says »

Yes I've installed everything service, and as I said all the other drives and being indexed normally only this one partition isn't.

And yes I have changed the drive letters as well but same results.
therube wrote: Fri Oct 13, 2023 5:35 pm (You may want to blank out the 'ntfs_volumes=[{"path:' part - except for that dealing with F:,)
Pardon me, I didn't get this hint, can you explain it little more.
therube
Posts: 4668
Joined: Thu Sep 03, 2009 6:48 pm

Re: One of the Drive Partition Can't be Index in Alpha .1357a

Post by therube »

Only way to index is running the everything in admin. Indexing process in admin also doesn't work.
I'm confused on this?

So you do have the Everything Service installed.

Help | Troubleshooing
should show something like, "Service: 1 (connected / installed and running)" [in most cases]

That said, with the Service installed, the only way you can index is by running Everything.exe "as Administrator"?

And if you do that, run Everything.exe "as Administrator", that does or does not then see F:?

Is F: seen in Tools | Options | Indexes -> NTFS (& is it set as 'Include in database')?

Might F: have been excluded (some time in the past, or whatever) in Tools | Options | Indexes -> Exclude?
therube
Posts: 4668
Joined: Thu Sep 03, 2009 6:48 pm

Re: One of the Drive Partition Can't be Index in Alpha .1357a

Post by therube »

can you explain it little more
It might help to post the contents of Help | Troubleshooting Information.
Some of the information might be "personally identifiable information".
So if something in there strikes you as "identifiable", omit that.
Some might consider NTFS volume ID's as "PID".
If that bothers you, edit, remove, or "randomize" that part of the information.
void
Developer
Posts: 15623
Joined: Fri Oct 16, 2009 11:31 pm

Re: One of the Drive Partition Can't be Index in Alpha .1357a

Post by void »

Was this working in an older versions of Everything?

Sounds like the Everything Service or the admin index process is crashing.
Strange running as admin works...



Please check your drive for errors:
  • Please backup anything important on your drive before checking it for errors.
  • In Windows Explorer, right click your drive and click Properties.
  • Click the Tools tab.
  • Click Check now...
  • Click Start
  • If prompted to schedule a scan on the next restart, click Yes.
Does the issue persist?
rabbit_says
Posts: 15
Joined: Tue Mar 19, 2019 12:40 pm

Re: One of the Drive Partition Can't be Index in Alpha .1357a

Post by rabbit_says »

A little more details to add, I installed this drive from another computer just recently it is mainly my backup drive.

The issue persists even after the error rechecking the drive, here is the screenshot of the error: https://imgur.com/a/bKF4M3E

and for your query regarding version earlier I had .1337a version and found this issue, so I updated the app to .1357a but issue remains.
I installed the stable version and indexing was done on all drives as expected.




Here is the troubleshoot log, @therube

Code: Select all

Everything:	1.5.0.1357a (x64)
OS:	Windows NT 10.0 22621 (x64)
Admin:	0
Service:	1 (connected / installed and running)
Command line:	
Binary:	C:\Program Files\Everything 1.5a\Everything64.exe
Profile:	C:\Users\...\AppData\Roaming\Everything\Everything-1.5a.ini
Database:	C:\Users\...\AppData\Local\Everything\Everything-1.5a.db
Instance:	1.5a
Config:	highlight_max_or_paths=256
Config:	auto_include_fixed_refs_volumes=1
Config:	find_first_file_path_not_found_retry_timeout=30000
Config:	input_stream_buf_size=0
Config:	output_stream_buf_size=0
Config:	icon_blend_hidden=1
Config:	thumbnail_medium_text_lines=2
Config:	thumbnail_large_text_lines=2
Config:	set_foreground_window_attach_thread_input=0
Config:	auto_scroll_view=1
Config:	rename_move_caret_to_selection_end=1
Config:	focus_search_on_activate=1
Config:	keep_result_focus_in_view=0
Config:	hotkey_explorer_path_search=1
Config:	efu_folder_append_path_separator=0
Config:	txt_folder_append_path_separator=0
Config:	csv_folder_append_path_separator=0
Config:	size_number_format=4
Config:	exclude_hidden_files_and_folders=1
Config:	exclude_system_files_and_folders=1
Config:	db_update_thread_priority=-1
Config:	refs_file_id_extd_directory_info_buffer_size=0
Config:	content_buf_size=0
Config:	include_file_content=1
Config:	content_include_only_folders=D:\Assets\Deliverable List
Config:	content_max_size=1
Config:	content_exclude_recall_on_data_access=0
Config:	show_copy_path=1
Config:	show_copy_full_name=0
Config:	show_explore=1
Config:	show_explore_path=1
Config:	context_menu_parent_folder=1
Config:	filter=EVERYTHING
Config:	filter_everything_name=Everything
Config:	filter_visible_count_max=0
Config:	omit_results=1
Config:	preview_icon=1
Config:	treeview_labels=0
Config:	search_history_always_suggest=1
Config:	nav_max_selection=1024
Config:	plugins=0
Config:	ntfs_volumes=[{"path":"C:","volume_name":"\\\\?\\Volume{70...51}","include_only":"C:\\Users\\...\\Desktop;C:\\Users\\...\\Downloads;C:\\Users\\"},{"path":"D:","volume_name":"\\\\?\\Volume{50...00}"},{"path":"E:","volume_name":"\\\\?\\Volume{66...00}"},{"path":"F:","volume_name":"\\\\?\\Volume{22...00}"}]
Last edited by void on Sat Oct 14, 2023 8:19 am, edited 1 time in total.
Reason: removed volume guids
void
Developer
Posts: 15623
Joined: Fri Oct 16, 2009 11:31 pm

Re: One of the Drive Partition Can't be Index in Alpha .1357a

Post by void »

Could you please send some debug output?
  • In Everything 1.5, Hold down Shift and from the Tools menu, under the Debug submenu, click Start Service Debug Logging.
  • Copy and paste the following into your Everything search box:
    /reindex f:
  • Press ENTER in your Everything search box.
    ---please wait for the reindex to complete -progress is shown in the status bar.
  • Hold down Shift and from the Tools menu, under the Debug submenu, click Stop Service Debug Logging.
  • Please send your C:\Windows\Temp\Everything Service Debug Log-1.5a.txt to support@voidtools.com
void
Developer
Posts: 15623
Joined: Fri Oct 16, 2009 11:31 pm

Re: One of the Drive Partition Can't be Index in Alpha .1357a

Post by void »

Thank you for the debug logs rabbit_says,

The logs show Everything unable to get volume information for this volume.
Access was denied.

Everything 1.5.0.1358a will now silently fail and continue indexing the volume.
rabbit_says
Posts: 15
Joined: Tue Mar 19, 2019 12:40 pm

Re: One of the Drive Partition Can't be Index in Alpha .1357a

Post by rabbit_says »

void wrote: Thu Oct 19, 2023 5:31 am
Everything 1.5.0.1358a will now silently fail and continue indexing the volume.
Thank you, it works flawlessly now.
Post Reply