Error In The Site Data Web Service Crawl
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Crawl Error - Error in the Site Data Web Service. (Exception of type 'System.OutOfMemoryException' was thrown.) SharePoint > SharePoint Legacy Versions - Search Question 0 Sign in to vote I have a Sharepoint site that includes a WIki library. Recently searches have stopped returning any hits from the Wiki pages. (Search hits from documents and discussions are correctly returned.) When I check the crawl log from Shared Services Admin site, I see the following error every time a crawl is performed: http://cao.tfn.com/caopedia/wiki%20pages/forms/allpages.aspx Error in the Site Data Web Service. (Exception of type 'System.OutOfMemoryException' was thrown.) The URL above is part of the Wiki library. When I look at the raw Sharepoint logs, I see the following entries every time a crawl is performed: 11/26/2007 05:01:50.93 mssdmn.exe (0x1F98) 0x1368 Search Server Common MS Search Indexing 7hp2 Monitorable EnumerateListFolder fail. error 2147755542, strWebUrl http://cao.tfn.com/Caopedia, strListName {e9acf8e9-f23f-4afd-b8e9-6eaf6b0101db}, strFolder 11/26/2007 05:01:50.93 mssdmn.exe (0x1F98) 0x1368 Search Server Common PHSts 0 Monitorable CSTS3RowFilter::EnumLinks: Return error to caller, hr=80042616 - File:\office\source\search\search\gather\protocols\sts3\sts3filt.cxx Line:1431 11/26/2007 05:01:50.93 mssdmn.exe (0x1F98) 0x1368 Search Server Common PHSts 0 Monitorable CSTS3RowFilter::HrOnFilterGetChunk: Return error to caller, hr=80042616
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can https://social.technet.microsoft.com/Forums/office/en-US/d7362fb1-8136-4e28-beb0-c2dd7f356b90/crawl-error-error-in-the-site-data-web-service-exception-of-type-systemoutofmemoryexception?forum=sharepointsearchlegacy ask a question Anybody can answer The best answers are voted up and rise to the top “Error in the Site Data Web Service.” when performing crawl up vote 1 down vote favorite Installed SharePoint Services v3 (SP2, october 2009 cumulative updates, Language Pack), attached to a content database I had previously (all works). Installed Search server 2008 Express (with language pack) http://serverfault.com/questions/122543/error-in-the-site-data-web-service-when-performing-crawl on top of WSS and crawl does not work. However it works for newly created web application + database. Was playing around with accounts, permissions to try get it working. Currently I have WSS_Crawler account with such permissions: Office Search Server runs with WSS_Crawler account Config database has read permissions for WSS_Crawler Content database has read permissions for WSS_Crawler WSS_Crawler is owner of search database. Added WSS_Crawler to SQL server browser user group and administrator Yes, i'v given more permissions than needed, but it doesn't even work with that and i don't know if its permission problem or what. Crawl log says there is Error in the Site Data Web Service., nothing more. There were known issues with a similar error: Error in the Site Data Web Service. (Value does not fall within the expected range.), but this is not the case as thats an old issue and i hope it has been included in SP2... Logs are from olders to newest (descending order). They don't appear to be very helpful. Crawl log http://serveris Crawled Local Office SharePoint Server sites 3/15/2010 9:39 AM sts3://serveris Craw
does not fall within the expectedrange.) Di seguito possibili cause per l’errore: “Error in the Site Data Web Service. (Value does not fall within the expected range.)” 1) You use the Stsadm.exe command-line tool to migrate users. When the Windows SharePoint Services 3.0 https://marcellotonarelli.wordpress.com/2008/09/14/error-in-the-site-data-web-service-value-does-not-fall-within-the-expected-range/ Web sites are crawled and are indexed, the following error message is logged in the crawl log: Error in the Site Data Web Service. (Value does not fall within the expected range.) It is noted, however, that http://dsen-25.blogspot.com/2010/07/error-in-site-data-web-service-value.html a few site collections, after a new full clean crawl, that the above error persists The following stsadm commands should be used to finalize the solution against any remaining site collections that still display the error in Error in the Site Data Web Service error: 1. stsadm -o export -url
within the expected range.) After setting up a new web application for a new portal I faced a crawling problem of the new site collection.Description:Right after starting the crawler it stops, giving 2-3 error messages, all with the same syntax:Error in the Site Data Web Service. (Value does not fall within the expected range.) The crawl log was the only place the error was logged, with no additional information regarding the cause of the problem. Searching the web came up with very little solutions, while only one of them seemed to apply to our case: 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(See here) While option 1 and 3 are reasonable, deleting the site collection didn't apply since the portal was already in production stage. (along with the fact faze 1 didn't pass either due to some technical issues… so I had to look for a better way to solve the issue)After opening a support ticket, Microsoft's support team came up with a nicer solution:First of all, the cause behind this problem:Corrupted SIDs in the UserInfo tableSolution:1. Run the following sql query using your moss content database:Select tp_login, tp_systemid, tp_deleted from userinfo where len(ltrim(rtrim(tp_systemid))) 2. Give some kind of permissions to the root site of the site collection to all the users returned by the query, except system users:NT AUTHORITY\authenticated users NT AUTHORITY\local service NT AUTHORITY\system SHAREPOINT\system4. After the query returns no results (accept the system accounts) start a full crawl. Notes:1. As for stage 2, you better test 2-3 users just to make sure that after you give them permissions to the root site they are infect removed from the query search results.2. By give permission I mean any type of permission, "read" is enough. While giving permissions to a user in the root level the SID is updated and fixed (somehow…).3. I had a local problem with some of the users which appeared in the returned result - I couldn't add them