Using Everything Server (x86) plugin, in case that matters. Using 1406 build currently.
An interesting situation where I just added e:\test to this list on the server instance, and it's removed from the Server's instance of Everything, but my workstation can still see it. However, my workstation cannot see the first two listed. What's the trick? Screenshot is server settings:
Excluding folders
Re: Excluding folders
After adding e:\test to your excludes, Everything will do a quick reindex and create a new index journal.
The existing clients will be immediately disconnected from the Everything Server because the journal ID has changed.
They will pull down the fresh index without e:\test within 30 seconds.
Please make sure the clients have "Monitor changes" enabled on the network index under Tools -> Options -> Network Indexes.
Please make sure the clients are not indexing e:\test from another method, eg: Folders, File Lists or Network Drives.
If the issue persists, please upload your Tools -> Debug -> Statistics from the client and server in a bug report.
The existing clients will be immediately disconnected from the Everything Server because the journal ID has changed.
They will pull down the fresh index without e:\test within 30 seconds.
Please make sure the clients have "Monitor changes" enabled on the network index under Tools -> Options -> Network Indexes.
Please make sure the clients are not indexing e:\test from another method, eg: Folders, File Lists or Network Drives.
If the issue persists, please upload your Tools -> Debug -> Statistics from the client and server in a bug report.
Re: Excluding folders
Monitor changes is enabled and folders, file lists, network drives are blank. I just uploaded both client and server debug statistics via the Bug Report.
Re: Excluding folders
I also just noticed that for some reason the Everything (1.5a) service doesn't appear to be running on the server.
Admin: 1
Service: 2 (disconnected / installed and not running)
I don't want to start it without your blessing, but not sure whats up there.
Everything Client service IS running on the server, however.
Admin: 1
Service: 2 (disconnected / installed and not running)
I don't want to start it without your blessing, but not sure whats up there.
Everything Client service IS running on the server, however.
Re: Excluding folders
I assume you are running the Everything Server as a service and as a logged-in-user.
This will lead to conflicting settings.
Please try the following:
On the Server:
Exit Everything (File -> Exit)
Stop the Everything Server Service by running:
Launch Everything as admin and update your exclude list.
Exit Everything (File -> Exit)
Restart the Everything Server Service by running:
Your clients should detect the change immediately and reindex within 30 seconds.
This will lead to conflicting settings.
Please try the following:
On the Server:
Exit Everything (File -> Exit)
Stop the Everything Server Service by running:
Everything.exe -stop-client-serviceLaunch Everything as admin and update your exclude list.
Exit Everything (File -> Exit)
Restart the Everything Server Service by running:
Everything.exe -start-client-serviceYour clients should detect the change immediately and reindex within 30 seconds.
Re: Excluding folders
When I launched as admin and added e:\test to exclude (it wasn't there).. Everything crashed on the server. My two workstations are stuck at "indexing fileserver2" and I'm not sure it's doing anything. (CPU usage doesn't show much)
So what is the proper set up here? The installs have always been a point of confusion. Should I start the Everything 1.5a service and stop the client service on the server?
So what is the proper set up here? The installs have always been a point of confusion. Should I start the Everything 1.5a service and stop the client service on the server?
Re: Excluding folders
Currently, both Everything 1.5a and Everything Client services are running. That was the only way I could get the clients/workstations to load up the file list. e:\test has also vanished on the client side now as hoped.
Re: Excluding folders
Exiting the client service would have overwritten your Everything.iniWhen I launched as admin and added e:\test to exclude (it wasn't there)..
Thanks for the Application Error report, fault offset 0x0005fc1d is building a folder path.Everything crashed on the server. My two workstations are stuck at "indexing fileserver2" and I'm not sure it's doing anything. (CPU usage doesn't show much)
A folder is corrupt.
Please build a fresh index:
- Exit Everything (File -> Exit)
- From a command prompt, run:
Everything.exe -stop-client-service - Delete your Everything-1.5a.db in the same location as your Everything.exe
- From a command prompt, run:
Everything.exe -start-client-service
Everything Service == service for the GUI running as a standard user to read NTFS volumes.So what is the proper set up here?
Everything Server Service == service for the Everything Server.
Everything Server Setup Guide
Everything Server Service Guide
The Everything Service is not required when running the Everything Server as a service.
I recommend installing the Everything Server as a service and uninstalling the Everything Service.
Please uninstall the Everything Service: (not the Everything Server Service)
- From a command prompt, run:
Everything.exe -stop-client-service - Launch Everything.exe as an administrator
- In Everything, from the Tools menu, click Options.
- Click the General tab on the left.
- Uncheck Everything Service.
- Click OK.
- Exit Everything (File -> Exit)
- From a command prompt, run:
Everything.exe -start-client-service
Please make sure you run Everything as administrator in the future when you want to make a change.
Making a change to the Everything Server Service