Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals > Forums Home > Microsoft Enterprise Search Forums > SharePoint - Search (pre-SharePoint 2010) > Search not indexing one site

Unanswered Search not indexing one site

    •  
      Tuesday, October 21, 2008 4:02 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi,
      Site information first:
      SPS Version: 12.0.0.6300 (wws3)
      We are using a farm, One db server, One server for search server/help search/web ap/ excel calc and the rest are hosted on another server.

      So our search function for one of our top-level site collections stopped being indexed by gatherer, ie: search still functioned on all of the other site collections, but it did not return any results for this specific site collection.  This started in the past week, can not hunt down a specific time when the search stopped working however.

      Sifting through the crawler logs i ran into these two that addressed my specific problem:

      http://intranet/sites/brokensite
      Error in the Site Data Web Service.

      http://intranet/sites/brokensite
      Error in the Site Data Web Service. (Value does not fall within the expected range.)


      Now researching this error brought me to several sites that told me that it occurs during user migration.. service pack was suppose to fix this problem ect...

      These are non-factors, we have not migrated users, the service pack was installed well in advance of any of these issues occuring.

      I have forced a full index (and the server is set up to do this every week) and it did not fix the problem.

      This is a production site so taking it down and putting it back up is not a viable option at this time.

      Does anyone have any suggestions? Or directions i can start to look in harder for possible fixes and solutions, i'm kinda running out of ideas.

      Thanks!

      • Edited by Graf3X Tuesday, October 21, 2008 7:27 PM
      •  
       

    All Replies

    • Tuesday, October 21, 2008 4:40 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Just another note i forgot to post -  I have also reset the entire index and allowed a full crawl, the same error came up in the crawl logs.
       
    • Wednesday, October 22, 2008 1:53 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hello Graf3X, 

      Errors in EventLog?

      Regards,

      Francesco
      www.sharepointinside.it
       
    • Wednesday, October 22, 2008 1:39 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi Francesco,


      That is the worst part of it all, i put the server to log all warnings and errors, perform a full crawl and i have no errors in management log, that is what made me look in the crawl log in sharepoint to start to figure it out.  Other errors in the logs are un-related (printer on network, ect) so i am really stumped.

      -Graf
       
    • Wednesday, October 22, 2008 1:48 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Update Logs:

      Now this maybe (and most likely is) completely un-related but, when looking at the SQL box's log (this does not host the search server ap, it's a strict sql box only) i bumped into these two errors the last time i did a full crawl:

      Event Type:    Error
      Event Source:    Windows Search Service
      Event Category:    Gatherer
      Event ID:    3024
      Date:        10/22/2008
      Time:        9:41:23 AM
      User:        N/A
      Computer:    SQL
      Description:
      The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

      Context:  Application, SystemIndex Catalog


      For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
      -----------------------------------------------------------------------------------------
      Event Type:    Warning
      Event Source:    Windows Search Service
      Event Category:    Gatherer
      Event ID:    3036
      Date:        10/22/2008
      Time:        9:41:23 AM
      User:        N/A
      Computer:    SQL
      Description:
      The content source <outlookexpress://{s-1-5-21-2920236363-1388513298-694212695-16241}/{60267a35-76e1-40b6-8cda-4d90627ca604}/> cannot be accessed.

      Context:  Application, SystemIndex Catalog

      Details:
           (0x81270005)


      For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
      --------------------------------------------------------------------------------------------

      Now since our corporation does not currently use outlook, i am not too concerned about the warning.. and the error seems to me to be due to the fact that i ran the update during operating hours. But i could be wrong! So i put it up here for your feed back.

      Thanks again

       
    • Monday, October 27, 2008 6:18 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi guys,

      I still haven't found a solution for this problem yet (but i will post once i find one!) -- However now i have found another interesting tid-bit that is most likely related to the problem:

      Ok so  Central Administration > Application Management > Site Collection Administrators
      Select the site Collection->

      Now i choose my site collection, it shows in the selection box the correct url, title, and primary admin..
      But when i click ok on it i get the following error message:

      User cannot be found.
      Troubleshoot issues with Windows SharePoint Services.

      So.. where does one start to fix this problem? Any ideas?


       
    • Wednesday, October 29, 2008 4:44 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      The above was an unrelated problem, and i solved it pretty easily. Still having trouble with this search problem, only new information i have is from the trace logs :

      10/29/2008 12:35:15.38     mssdmn.exe (0x0D5C)                         0x0E2C    Search Server Common              MS Search Indexing                7hos    Monitorable    GetSite fail. error 2147755542, strSiteUrl http://intranet/sites/brokensite

      Not very useful, i try looking up the specific error code and get.. well nothing.
      *pokes people around him*
      Anyone got some thoughts on this one?
       
    • Wednesday, November 19, 2008 6:34 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I am encountering the same issue, although we did do a user migration.

      Single server deployment 64-bit WSS 3.0.  I have two site collections and only one is being indexed.

      I get the error:

      GetSite fail. error 2147755542, strSiteUrl https://mysite

       
    • Thursday, November 20, 2008 3:37 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Aaron,

      There is a solution out there that i am trying to test in my set up (getting some test boxes set up to attempt to fix other problems with the site first... headache with -export).

      I don't have a link to the article at the moment, but once i do i will edit this post to link/give credit.

      The problem originates dude to the SID's and users. Since you migrated users, this solution should apply for you (turns out the person who had my job before me did migrate users a while back, and had this problem, but didn't fix it the correct way, and now it's comming back to haunt me)

      To solve this problem you need to force sharepoint to rebuild/reorder the SID's and forget about any custom sercurity that was on your site. In order to do this you export your site without the -includeusersecurity tag.

      So the whole proccess is:

      1. stsadm -o export -url http://intranet/sites/it -filename D:\it.back.11.21.08.cmp -versions 2
      2. Delete the site collection
      3. stsadm -o import -url http://intranet/sites/it -filename D:\it.back.11.21.08.cmp -updateversions 2 -nofilecompression

      I'm stuck facing an -o export problem on this solution myself at the moment, so i cant verify this is going to fix the problem for me, but it should work for you.

      Oh and if your site is anything like mine, and your running low on disk space on your c drive, you may want to log in as another account and change the environment variables for your tmp directory to go to another drive (my case d).