Crawl fails with an error The SharePoint item being crawled returned an error when requesting data from the web service

Crawl fails with an error The SharePoint item being crawled returned an error when requesting data from the web service. ( Error from SharePoint site: Data is Null. This method or property cannot be called on Null values. )

Issue: The SharePoint item being crawled returned an error when requesting data from the web service. ( Error from SharePoint site: Length of parameter Name exceeds specified max for the column )

Solution: Please find the below solutions to resolve the issues.

1.    Check the link :http://support.microsoft.com/kb/2323206/en-us

2.    Try to disable the anonymous access on the default zone web application(in content source)

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

The item may be too large or corrupt.You may also verify that you have the latest version of this I Filter

Issue: SharePoint 2013 crawl error - The item may be too large or corrupt

Solution: Please follow the following steps to resolve the issue. Ensure to change the following registry settings.

 

Key	Default   Value	New   Value
HKLM\SOFTWARE\Microsoft\Office   Server\15\Search\Global\GatheringManager\DedicatedFilterProcessMemoryQuota	104857600	209715200
HKLM\SOFTWARE\Microsoft\Office   Server\15\Search\Global\GatheringManager\FilterProcessMemoryQuota	104857600	209715200

 

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

The file reached the maximum download limit. Check that the full text of the document can be meaningfully crawled” in the Crawling log Error

The file reached the maximum download limit. Check that the full text of the document can be meaningfully crawled” in the Crawling log Error.

Issue: The file reached the maximum download limit. Check that the full text of the document can be meaningfully crawled” in the Crawling log Error

Description: Since working with SharePoint 2013, I had lot of crawl warning saying the file was not fully indexed as it reached the maximum download limit: “The file reached the maximum download limit warnings. Check that the full text of the document can be meaningfully crawled”.

Cause: it was an ‘issue’ with the new search engine (now SharePoint 2013 is fully using Fast as search engine) as my content was properly crawled with SharePoint 2010.

Solution 1: The solution is (off course) to increase the download limit for the index process.

1)   Open the SharePoint Management Shell

2)   Run the following commands

a.   $searchapp = Get-SPEnterpriseSearchServiceApplication

b.   $searchapp.GetProperty(“MaxDownloadSize”) |this command is just to check the current value; default is 64

c.   $searchapp.SetProperty(“MaxDownloadSize”, <value>) where you replace <value> with the download limit; for example, 128

d.   $searchapp.Update()

3)   Restart the server

4)   Do a full crawl and the ‘download’ warnings will disappears

Solution 2: Please change the registry settings for search as below.

1.   Start Registry Editor (Regedit.exe).

2.   Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Global\Gathering Manager

3.   Open Edit – New – DWORD Value. Name it MaxDownloadSize. Double-click, change the value to Decimal, and type the maximum size (in MB) for files that the gatherer downloads.

4.   Restart the server.

5.   Start Full Crawl. 

Note: Increasing the file size may cause a timeout exception. How To increase timeout value check the Article below.

http://expertsharepoint.blogspot.de/2013/12/this-item-could-not-be-crawled-because.html

 

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

What are the scenarios where full crawl will required

What are the scenarios where full crawl will required

Description: Before users can perform searches in SharePoint Server 2013, we must crawl or federate the content that want to be able to search. When you crawl content, the Search service builds a search index that users can run queries (search requests) against. You can also configure the Search system to display search results from an external provider (such as Bing) alongside the results from the local search index. The process of getting search results from an external provider and displaying the results locally is called federation. 

crawl will required in below:

Reasons for a Search service application administrator to do a full crawl for one or more content sources include the following. In All the below we need to do a full crawl to get the data search.

1.     A Search service application has just been created and the preconfigured content source Local SharePoint sites has not been crawled yet.

2.     Some other content source is new and has not been crawled yet.

3.     The Search service application administrator has changed a content source.

4.     A software update or service pack was installed on servers in the farm. See the instructions for the software update or service pack for more information.

5.     A Search service application administrator or site collection administrator added or changed a managed property. A full crawl of all affected content sources is required for the new or changed managed property to take effect.

6.     You want to detect security changes that were made to local groups on a file share after the last full crawl of the file share.

7.     You want to resolve consecutive incremental crawl failures. If an incremental crawl fails a large number of consecutive times for any particular content, the system removes the affected content from the search index.

8.     Crawl rules have been added, deleted, or modified.

9.     You want to replace a corrupted search index.

10.  The permissions for the user account that is assigned to the default content access account have changed.

The system does a full crawl even when an incremental crawl or continuous crawl is scheduled under the following circumstances:

1.     A search administrator stopped the previous crawl.

2.     A content database was restored, or a farm administrator has detached and reattached a content database.

3.     A full crawl of the content source has never been done from this Search service application.

4.     The crawl database does not contain entries for the addresses that are being crawled. Without entries in the crawl database for the items being crawled, incremental crawls cannot occur.

 

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.