Adding Comments to a SharePoint 2013 Approval Workflow
I needed the ability to capture comments from Approval Tasks in a workflow. This has changed greatly in 2013 workflows. Everything is more modular and as such must be built somewhat from scratch. SharePoint 2013 workflows can become corrupt. This may have been fixed by a patch, but please refer to a previous post before creating any 2013 workflows in Designer: http://www.ericjochens.com/2014/12/sharepoint-2013-workflow-observations.htmlSharePoint 2013 does not have a built-in approval workflow, nor does a built-in task item include comments. I solved this by building my own approval workflow, and using a custom content type to include a comments field.A SharePoint 2013 Workflow will not store the Task ID when a task is created, so you cannot do a lookup into that task list to grab comments or any other field. I solved this by creating a separate workflow in the task list to read the Related Items column, and update the origin…
I realize that many admins are reluctant to delete web applications. I personally know why I ma doing it and how to achieve this easily. You should always retain any customization you have added to the site, like web.config mods, etc. The Alternate Access Mappings are always available, but they leave open holes that I do not wish to keep active. I like a clean setup.
Perhaps you need to clone a development, test, or some SharePoint server and you need to change the hostname so that it can exist on the same domain without a SID conflict. Or you just have a use-case for wanting to rename the hostname of a SharePoint server. It can be done, just make sure you go through all of the steps.
The Rename-SPServer PowerShell command can also be used to change the SQL Server name, for the case where you might move the databases to a new SQL server or instance and you need to point all of the farm servers to this new hostname\instance.
SharePoint 2013 Search Crawls Stop Crawling All Content
Recently the search system stopped successfully crawling content. ASPX pages were crawled, but no content was being indexed. Opening up the crawl log showed thousands of errors with this message: The content processing pipeline failed to process the item. (Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index; SearchID = [GUID]) Note: the resolution is in the resolution section for those who cannot or refuse to read.
What does this mean? Honestly initially it made no sense. So I learned a valuable lesson: I misguidedly spent the next 2 days trying the usual fixes like resetting the index, rebuilding the 2013 search components, and lastly what EVERYONE does: they fix it with a sledgehammer (in this case rebuilding the search service application).
But what if rebuilding the search service application is a horrible pain? We have thousands of query rules, 30 result source…