Nam-Quang Tran

The Log On tab showing "Local System" means the account change was never saved: DocFetcherServerw.exe unfortunately fails silently when Windows rejects the account. Most likely the user name needs to be written as .\guenther rather than just guenther. The more reliable way is to use Windows' own Services console instead of DocFetcherServerw.exe: Press Win+R, type services.msc, and open the properties of "DocFetcher Server". On the "Log On" tab, select "This account", click "Browse…" → "Advanced…"...

DocFetcher Server doesn't connect to network shares itself. It reads files through Windows, so it doesn't accept 'smb://' addresses and has no fields for a username or password. Instead, Windows needs to know the NAS credentials, and then you add the folder by its network path. The access is denied because the DocFetcher Server service runs under the Windows "Local System" account by default, and your NAS doesn't accept that account. To fix this: 1) Run the service under your own Windows account:...

DocFetcher Server doesn't connect to network shares itself. It reads files through Windows, so it doesn't accept 'smb://' addresses and has no fields for a username or password. Instead, Windows needs to know the NAS credentials, and then you add the folder by its network path. The access is denied because the DocFetcher Server service runs under the Windows "Local System" account by default, and your NAS doesn't accept that account. To fix this: 1) Run the service under your own Windows account:...

DocFetcher Server doesn't connect to network shares itself. It reads files through Windows, so it doesn't accept 'smb://' addresses and has no fields for a username or password. Instead, Windows needs to know the NAS credentials, and then you add the folder by its network path. The access is denied because the DocFetcher Server service runs under the Windows "Local System" account by default, and your NAS doesn't accept that account. To fix this: 1) Run the service under your own Windows account:...

DocFetcher Server doesn't connect to network shares itself. It reads files through Windows, so it doesn't accept 'smb://' addresses and has no fields for a username or password. Instead, Windows needs to know the NAS credentials, and then you add the folder by its network path. The access is denied because the DocFetcher Server service runs under the Windows "Local System" account by default, and your NAS doesn't accept that account. To fix this: 1) Run the service under your own Windows account:...

Hi there, The path you see in DocFetcherServerw.exe is where the DocFetcher Server Windows service was registered when server-install.exe was run. It points to your Documents folder, so at some point server-install.exe must have been run from a copy of DocFetcher Server in that folder. The service still points there and not to your new folder in C:\Programs. That is why it doesn't start. The field is always grayed out and can't be changed there; the only way to change it is to uninstall the service...

Hi there, Specifically for the portable version, you probably need to update the index of folder A after subfolder B is deleted. The "probably" is because the index update runs automatically under some conditions: The index must have been created with the option "Watch folders for file changes" ticked. DocFetcher was running while subfolder B was deleted, or you set up the DocFetcher daemon and it was running while subfolder B was deleted. In the non-portable version, the daemon is set up automatically,...

Program Crashed whilst Indexing Files