Home
%3CLINGO-SUB%20id%3D%22lingo-sub-571580%22%20slang%3D%22en-US%22%3ESharePoint%20Tidbit%20-%20SharePoint%202013%20Crawl%20is%20getting%20the%20error%20%22Sandbox%20worker%20pool%20is%20closed%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-571580%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20TECHNET%20on%20Jul%2025%2C%202016%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20Hello%20All%2C%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20As%20a%20customer%20of%20mine%20stands%20up%20there%20SharePoint%202013%20farm%2C%20they%20are%20using%20least%20privilege%20for%20the%20service%20accounts.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20During%20the%20crawl%20a%20large%20portion%20of%20the%20documents%20get%20the%20following%26nbsp%3Berror%20message%20in%20the%20%3CBR%20%2F%3E%3CBLOCKQUOTE%3EProcessing%20this%20item%20failed%20because%20of%20an%20unknown%20error%20when%20trying%20to%20parse%20its%20contents.%20(%20Error%20parsing%20document%20'http%3A%2F%2Fsharepoint%2FLists%2FHR%20Transaction%20Links%2FMSS'.%20Sandbox%20worker%20pool%20is%20closed.%3B%20%3B%20SearchID%20%3D%204D01F588-EF0F-4F13-A2AE-49EA0BEXXXXX%20)%3C%2FBLOCKQUOTE%3E%3CBR%20%2F%3E%20This%20issue%20is%20due%20to%20a%20lack%20of%20permissions%20for%20the%20crawl%20account%2C%20the%20Support%20team%20has%20provided%20the%20following%20steps%20to%20resolve%20the%20issue%20%3CBR%20%2F%3E%3CBLOCKQUOTE%3E%3CSTRONG%3E(1)%20%3C%2FSTRONG%3E%20%22Start%22%20-%26gt%3B%20%22Administrative%20Tools%22%20-%26gt%3B%20%22Local%20Security%20Policy%22%20(or%20run%3A%20%3CSTRONG%3E%20Secpol.msc%20%3C%2FSTRONG%3E%20)%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20(2)%20%3C%2FSTRONG%3E%20Expand%20%E2%80%9CLocal%20Policies%E2%80%9D%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20(3)%20%3C%2FSTRONG%3E%20Click%20on%20%E2%80%9CUser%20rights%20assignment%E2%80%9D%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20(4)%20%3C%2FSTRONG%3E%20Make%20sure%20that%20the%20search%20service%20account%20has%20the%20following%20privileges%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20-%26gt%3B%20%22Replace%20a%20process%20level%20token%22%20%3CBR%20%2F%3E%20-%26gt%3B%20%22Adjust%20memory%20quotas%20for%20a%20process%22%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20(5)%20%3C%2FSTRONG%3E%20Run%20%3CSTRONG%3E%20gpupdate%20%2Fforce%3C%2FSTRONG%3E%3C%2FBLOCKQUOTE%3E%3CBR%20%2F%3E%20After%20making%20that%20change%20you%20can%20either%20force%20a%20crawl%20or%20allow%20the%20next%20scheduled%20crawl%20to%20happen.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Pax%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-571580%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20Jul%2025%2C%202016%20Hello%20All%2CAs%20a%20customer%20of%20mine%20stands%20up%20there%20SharePoint%202013%20farm%2C%20they%20are%20using%20least%20privilege%20for%20the%20service%20accounts.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-571580%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ecrawl%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPermission%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esearch%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esharepoint%202013%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
First published on TECHNET on Jul 25, 2016
Hello All,

As a customer of mine stands up there SharePoint 2013 farm, they are using least privilege for the service accounts.

During the crawl a large portion of the documents get the following error message in the
Processing this item failed because of an unknown error when trying to parse its contents. ( Error parsing document 'http://sharepoint/Lists/HR Transaction Links/MSS'. Sandbox worker pool is closed.; ; SearchID = 4D01F588-EF0F-4F13-A2AE-49EA0BEXXXXX )

This issue is due to a lack of permissions for the crawl account, the Support team has provided the following steps to resolve the issue
(1) "Start" -> "Administrative Tools" -> "Local Security Policy" (or run: Secpol.msc )
(2) Expand “Local Policies”
(3) Click on “User rights assignment”
(4) Make sure that the search service account has the following privileges

-> "Replace a process level token"
-> "Adjust memory quotas for a process"


(5) Run gpupdate /force

After making that change you can either force a crawl or allow the next scheduled crawl to happen.

Pax