Category Archives: sharepoint2010

parse error processing item failed sharepoint

parse error processing this item failed because of an unknown error when trying to parse its contents

There is parse error found in the Crawl log of a SharePoint 2013 environment. Processing this item failed because of an unknown error when trying to parsing its contents. (Error parsing document,Sandbox worker pool is closed,SearchID)

  1. In order to fix this you can try to perform the following action plan:
  2. Open "Local Policies”
  3. Click on “User rights assignment”
    adjust memory quotes-1276x416

    adjust memory quotes

  4. Make sure that the search service account has the following rights:"Replace a process level token”.
    replace process level token-1060x766

    replace process level token

  5. "Adjust memory quotas for a process"
    adjust memory quota-1054x762

    adjust memory quota

  6. "Impersonate a client after authentication"
    impersonate client-1052x758

    impersonate client

  7. Please make sure that the policies don't get changed afterwards.
  8. Run a clear configuration cache
  9. Start a full crawl and the errors should be gone.
Advertisements
Retrive account password powershell

Start SharePoint Service Application Proxy using Powershell

If your Usage and Health Data Collection Proxy is in a stopped state here is a quick bit of PowerShell to to get it started:

$sap = Get-SPServiceApplicationProxy | where-object {$_.TypeName -eq “Usage and Health Data Collection Proxy”}
$sap.Provision()

The above can easily be adapted to allow you to start any Service Application Proxy

Advertisements
Advertisements

Slow SharePoint improve performance without upgrading hardware

what you can do if your SharePoint is sometimes very slow.

E.g.: on the first start of a Site
Sometimes during the day a search query will take about a minute until you get results.....

Just look on that article: http://support.microsoft.com/kb/2625048

it will improve "feeled" performance (site response times) massive, if you're going to implement both solutions.

Disabling CRL Check is just necessary if the SP Server does not have internet connectivity, that means proxy settings must be configured for the server itself

http://technet.microsoft.com/de-de/library/bb430772(v=exchg.141).aspx, and your proxy must allow traffic from the server of course.

Advertisements
Advertisements