(solved) ET Server not scanning at schedule

[Garfield]

Greetings,

I'm using ET Server since 11.2024, therefor I would say I'm a noob (also I'm using ET for >10 years) and therefor maybe I'm misunderstanding anything or all ??

ET Version in action: 1.5.1390a
on Synology win11 vm as single application, installed as described here: viewtopic.php?f=12&t=9794
The volumes are on Synology, mapped to the win11 vm and are accessible.

I can log into win11 vm and use ET as client and scan the volumes - no problems.

Switching to ET Server Mode as described ...
Logging out from win11 vm or rebooting - as I understood, ET server is running as service, a logged in user is not necessary.
The ET server is up and running, as I can access it as Network Index on any ET Client.

BUT

the ET server is not re-scanning the volumes as scheduled in the settings, also it is not trying to monitor volume changes.
Live Monitoring is a complicated thing... so my main problem is the not scanning at schedule.

This can easily be proven with the Debug statistics log on any client (today 08.02.2025):

Code: Select all

Last build date:	30.12.2024 22:47
Last rebuild reason:	Out of date network index 192.168.178.12 is available

The index could be updated in this ways:

• Manual re-scanning the ET server index is updating the index

• logged in user to win11 vm, then the ET server is re-scanning at schedule

So, what I'm missing or miss-understanding?
IMHO, for Service continuity the ET Server should run after reboot and update at schedule.

Thanks in advance for any hint or answer!

Regards,
Garfield

[NotNull]

It sounds like your Everything Server Service is (also) indexing non-local content.
Default Server Service runs under SYSTEM credentials. This local account does not have access to external filesystems. like network folders.

Solution: Run Server Service with an account that that also has access to these external files:

- Start Services.msc as administrator
- Double click Server Service ( it is probably called Everything Client Service)
- Activate the Log On tab
- Enter the credentials for an account that also has access to the networkshares.
- OK
- Restart the service

[Garfield]

Hi,

your assumption is correct
I'm using the win vm just for building an ET Index of all of my files on my NAS - my ds918+ has not enough CPU to use the win vm for more ... (hm, reason to upgrade - honey, we've to talk ... )

Will try credentials for the ET service, wait for schedule and will report here.

[Garfield]

Greetings,

sorry for the delay - I'm heavy on workload ...

It sounds like your Everything Server Service is (also) indexing non-local content.
Default Server Service runs under SYSTEM credentials. This local account does not have access to external filesystems. like network folders.

Solution: Run Server Service with an account that that also has access to these external files:

- Start Services.msc as administrator
- Double click Server Service ( it is probably called Everything Client Service)
- Activate the Log On tab
- Enter the credentials for an account that also has access to the networkshares.
- OK
- Restart the service

The proposed solution is working like charme
Just be sure to use an account which has access to the NAS.

I had forgotten that my network share mappings use a different account to access the NAS than the Win login user is called


THX NotNull!