none
Search throws an error on first query

    General Discussion

  • I have an intermittent problem with Search. When a person enters a search query, it returns an error saying "Internal Server Exception". I can't seem to see any other information apart from that. Then when the user runs another search, it seems to be fine. I can't see any reasons for this. Any ideas on where to start?

    Monday, July 01, 2013 9:26 AM

All Replies

  • Does it take a long time for the first search to load?

    Once user A has run a search (and gotten the internal server exception message) does user B get the same error or a working search?

    It sounds like it could be a very slow to load web application timing out during the warmup process. That would be very slow the first time around then nice and snappy for any other users that hit it.

    If so the crudest approach is to use a warmup script but that would only hide the underlying issue that causes the site load to be so slow (rarely hardware, normally configuration)...

    Monday, July 01, 2013 10:08 AM
  • Hi,

    Thanks for your response. I already have a warm up script. The error is not slow to load at all, it comes up instantly. Other people could be fine or they could be the same, it's hard to pinpoint. The same thing could happen to the same user a few times throughout the day. It's difficult to troubleshoot as people don't use search too often.

    Monday, July 01, 2013 10:12 AM
  • Have you been able to find any matching entries in either the event viewer or in the ULS logs?
    Monday, July 01, 2013 10:40 AM
  • Do you have multiple search components installed in the farm (e.g. two query components), it's possible that one of these is faulty and the problem you're seeing as intermittent is because of the service load balancing?

    Paul.


    Please ensure that you mark a question as Answered once you receive a satisfactory response. This helps people in future when searching and helps prevent the same questions being asked multiple times.

    9 hours 13 minutes ago