Windows 7 network search enters "sleep mode"

Hakuna Matata 89

Reputable
Jun 17, 2014
20
0
4,510
Hello guys.

At work we have set up a local network consisting of 10 PCs (1 server + 9 clients) all with Windows 7 so we can have a shared folder where we will store all our working files (mostly Excel, Word). Currently the folder contains ~200K files and it is indexed. The users use Windows 7 search field (at the top right corner of each window) in order to search for file names or specific words inside files.

Everything is working great but with a problem:

- If the person using the server PC won't do a single search for some time (f.e no searches for 1 hour at the Server PC) then the search stops working (returning results) for the clients PC. Its like the server PC's search is entering in sort of "sleep mode" until the user do some searches (from the server PC) in order to reactivate it.

Is this some kind of Windows 7 setting? Is there a way to make the search not "freeze" after some time of inactivity?
 

Hakuna Matata 89

Reputable
Jun 17, 2014
20
0
4,510


The folder is already indexed. Also the category "How do I troubleshoot problems with search and indexing?" doesn't help.

As i said my problem is the search stops working if there are no searches executed from the server PC for ~1 hour
 
I did a bit more research on Windows 7 indexing - if there is no activity in the indexed folders as determined by the local system that is performing the indexing - it doesn't update the indexes (I couldn't find the specific time periods of inactivity).

On servers (Server 2003, 2008, 2012), indexing is performed non-stop, as the system is not designed to be utilized as a desktop computer, but to serve files.

You can try this: Create a batch job that does a simple directory command of the indexed folders that need updated - and add this to windows scheduler to be run every XX minutes.
 

Hakuna Matata 89

Reputable
Jun 17, 2014
20
0
4,510


M8 you didn't understand my problem :) . Indexing is fine. Let me give you an example of what is happening with the following timeline:


  • ■ 10:00 - John searches a phone XXX-XXXX-XXXXX from a client PC. The server returns him some results
    ■ 10:00 to 11:00 - Mike is using the server PC but he is not doing any searches from the server (f.e writing a big word) for 1 hour (from 10:00 to 11:00) so the server's search is entering in some kind of "sleep mode" (the problem)
    ■ 10:30 - John searches again for the same phone (from the same client PC) which previously returned results and he gets nothing. Now every search he does the server won't return any results. So he yells to the guy sitting at the server PC: "Mike, do some bloody dummy searches in order to wake up server's search"
    ■ 10:31 - Mike do some quick searches from the server PC and voila the search "unfroze" and is working again for the next 1 hour
    ■ Now unless Mike is doing regular searches from the server, the server's seach will stop working again after 1 hour of no searches