Posts

Showing posts from January, 2016

SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem

if you got an error like this

The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 ) as well as these: The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD ) the solution for me was to clear configuration cache (PS) and then restart SP Search Services.

THX to my friend T…

Internet Explorer error 'Node' is undefined

if you by any chance get this only in ie its because MS is trying to make the shityest browser ever!!!

the browser probably runs in compatible mode of ie7.

the fix is so ever simple:
<meta http-equiv="x-ua-compatible" content="IE=edge">

Run Sharepoint Powershell as a different user

In the other day i want to set a Pre-Prod stage and wanted to change the Continuous Crawl Interval using the known PS commands

$ssa = Get-SPEnterpriseSearchServiceApplication  
$ssa.SetProperty("ContinuousCrawlInterval",20)
see more here

BUT!  i could not gain access to the search service, and kept getting this error:
format-default : Exception has been thrown by the target of an invocation.

Googling around i got the point that it was a permissions error, mainly from here where it was stated by BastianWebster that you need to do this with the user running the app pool.

now usually its either everything is running with the same super-user, or at least you get your super-user with permissions to rule-them-all, but not this time. i was sp_admin, and, funny as it is, the sp_search, running the pool for the SSA, was not allowed for RDP.

so i just tried to run SP Management Shell, the Sharepoint Powershell (SP PS lol) as a different user but could not!

many suggestions are around ther…