none
Windows Search Service

    Question

  • So the text reads:

    Windows Search Service permits fast file searches on this server from clients that are compatible with Windows Search Service. Windows Search Service is intended for desktop search or small file server scenarios, and not for enterprise scenarios.

    So whats considered an "enterprise scenario"? My business is small to medium, but one of our file servers is performing badly with Windows Search related errors. Such as:

    The entry <D:\FILESHARES\filename.docx> in the hash map cannot be updated.

    Context:  Application, SystemIndex Catalog

    Details:
    A device attached to the system is not functioning.   (0x8007001f)

    The dedicated fileshare disk (RAID5) has about 4TB of files and well over a million files, but only about 60 users accessing these files.

    So...should I remove the Windows Search Service?

    Thursday, February 27, 2014 9:39 AM

Answers

  • Hiya,

    It could sound like a lock is preventing the other indexing application in working with the item. However my experience with Windows Search is limited.

    Your transferring 4TB over the WAN link everytime your crawling. So depending on your line speeds, the 8 days might be what is expected. The following articles gives a bit more on the subject.

    http://technet.microsoft.com/en-us/library/gg441255.aspx

    On a general level of performance, the following article gives you some numbers on what to expect for a LAN crawl. http://technet.microsoft.com/en-us/library/dn342836.aspx#BKMK_Step1

    In general I would advise only to use one indexing technology. I also know that it quickly becomes political about who does what. Depending on how SharePoint is implemented in your company, I would properly recommend using that for the indexing and presenting the contents of your file shares.

    • Marked as answer by Trana010 Sunday, March 02, 2014 9:47 PM
    Friday, February 28, 2014 7:45 AM

All replies

  • Hiya,

    Yes. I'm guessing your not really using it anyway. And if you want to use search on your files, SharePoint 2013 Foundation, would be a way better option anyway.


    Thursday, February 27, 2014 1:03 PM
  • Funny you should bring that up, I wasn't going to ask this. But the fact is that these issues seem to be occurring while the SharePoint 2013 search crawler runs.

    We were basically running both since some end users prefer to search on the file shares and some on SharePoint. But, we are crawling these files over the WAN for SharePoint, not on the LAN. A full crawl takes like 8 days...this setup is done by another department and don't really want any part of it.

    But since you brought it up, whats your thoughts on doing a SP search crawl over a WAN on a file server with 4TB of files. Thanks

    Thursday, February 27, 2014 9:26 PM
  • Hiya,

    It could sound like a lock is preventing the other indexing application in working with the item. However my experience with Windows Search is limited.

    Your transferring 4TB over the WAN link everytime your crawling. So depending on your line speeds, the 8 days might be what is expected. The following articles gives a bit more on the subject.

    http://technet.microsoft.com/en-us/library/gg441255.aspx

    On a general level of performance, the following article gives you some numbers on what to expect for a LAN crawl. http://technet.microsoft.com/en-us/library/dn342836.aspx#BKMK_Step1

    In general I would advise only to use one indexing technology. I also know that it quickly becomes political about who does what. Depending on how SharePoint is implemented in your company, I would properly recommend using that for the indexing and presenting the contents of your file shares.

    • Marked as answer by Trana010 Sunday, March 02, 2014 9:47 PM
    Friday, February 28, 2014 7:45 AM