<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">SharePoint Strategery</title><subtitle type="html">Best used when *strategy* breaks down... (blog by Brian Pendergrass, Microsoft SharePoint - Senior Support Escalation Engineer)</subtitle><id>http://blogs.msdn.com/b/sharepoint_strategery/atom.aspx</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/sharepoint_strategery/" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/b/sharepoint_strategery/atom.aspx" /><generator uri="http://telligent.com" version="5.6.50428.7875">Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><updated>2012-08-24T15:31:00Z</updated><entry><title>Alternate Access Mappings (AAMs) *Explained</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/05/27/alternate-access-mappings-explained.aspx" /><id>http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/05/27/alternate-access-mappings-explained.aspx</id><published>2013-05-27T19:55:00Z</published><updated>2013-05-27T19:55:00Z</updated><content type="html">Based on many of the support cases that I've seen, Alternate Access Mappings (AAM) may be one of the least understood aspects of SharePoint and can have substantial impact on Search (both Crawl and Query). In this post, I'll document some of my experiences and insights on AAMs. 
 Note: " Plan alternate access mappings (Office SharePoint Server) " is the best resource I've found for documenting AAMs, which covers both several configuration scenarios and troubleshooting common mistakes. Although listed...(&lt;a href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/05/27/alternate-access-mappings-explained.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10421348" width="1" height="1"&gt;</content><author><name>bspender</name><uri>http://blogs.msdn.com/bspender_4000_gmail.com/ProfileUrlRedirect.ashx</uri></author><category term="Troubleshooting" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Troubleshooting/" /><category term="Workarounds" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Workarounds/" /><category term="Concepts" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Concepts/" /><category term="Crawling" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Crawling/" /><category term="Explained" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Explained/" /><category term="Query" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Query/" /><category term="SharePoint 2013" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/SharePoint+2013/" /><category term="AAMs" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/AAMs/" /></entry><entry><title>SP2010: Troubleshooting ServerID Mismatch (Deleting Components)</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/05/19/sp2010-troubleshooting-serverid-mismatch-deleting-components.aspx" /><id>http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/05/19/sp2010-troubleshooting-serverid-mismatch-deleting-components.aspx</id><published>2013-05-20T03:15:00Z</published><updated>2013-05-20T03:15:00Z</updated><content type="html">In a previous post , I described a scenario where removing/re-joining a SharePoint Server that hosts a Search component will lead to an inconsistency in the ServerID being referenced by the applicable Search component(s) and the SharePoint farm Configuration object for the applicable server. If you identify a ServerID mismatch, the recommendation is to remove (or move to another server) any component with a mismatched ServerID, then (optionally) re-add the component(s) to the original server(s)....(&lt;a href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/05/19/sp2010-troubleshooting-serverid-mismatch-deleting-components.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10419978" width="1" height="1"&gt;</content><author><name>bspender</name><uri>http://blogs.msdn.com/bspender_4000_gmail.com/ProfileUrlRedirect.ashx</uri></author><category term="Troubleshooting" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Troubleshooting/" /><category term="Workarounds" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Workarounds/" /><category term="Topology" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Topology/" /><category term="SSA" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/SSA/" /></entry><entry><title>SP2010: Broken Topology and Hung Crawls Can Be Caused by ServerID Mismatch</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/03/28/sp2010-broken-topology-and-hung-crawls-can-be-caused-by-serverid-mismatch.aspx" /><id>http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/03/28/sp2010-broken-topology-and-hung-crawls-can-be-caused-by-serverid-mismatch.aspx</id><published>2013-03-28T19:29:00Z</published><updated>2013-03-28T19:29:00Z</updated><content type="html">Removing or re-joining a SharePoint Server that hosts a Search component will lead to an inconsistency in the ServerID being referenced by the applicable Search component(s) and the SharePoint farm Configuration object for the applicable server. 
 Translation you ask? Each Search component object has a reference to the SharePoint on which it runs. The component references its Server by both the name as well as the GUID assigned at the Farm level to identify each Server (e.g. the ServerID). 
 For...(&lt;a href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/03/28/sp2010-broken-topology-and-hung-crawls-can-be-caused-by-serverid-mismatch.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10406147" width="1" height="1"&gt;</content><author><name>bspender</name><uri>http://blogs.msdn.com/bspender_4000_gmail.com/ProfileUrlRedirect.ashx</uri></author><category term="Troubleshooting" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Troubleshooting/" /><category term="Explained" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Explained/" /><category term="Topology" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Topology/" /><category term="PowerShell" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/PowerShell/" /><category term="SSA" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/SSA/" /></entry><entry><title>Beware crawling the non-Default zone for a SharePoint 2013 Web Application</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/02/20/beware-crawling-the-non-default-zone-for-a-sharepoint-2013-web-application.aspx" /><id>http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/02/20/beware-crawling-the-non-default-zone-for-a-sharepoint-2013-web-application.aspx</id><published>2013-02-20T19:09:00Z</published><updated>2013-02-20T19:09:00Z</updated><content type="html">After playing for a while with SharePoint 2013 Search, I thought we were out of the woods regarding crawls of the non-Default Alternate Access Mapping (AAM) zone for a SharePoint Web Application. This caused all sorts of problems in earlier versions of SharePoint (primarily busted contextual scopes, broken social tagging, and workflow emails linking to the incorrect zone) because there is a built in assumption by other components throughout SharePoint that the Default zone is being crawled. I'm still...(&lt;a href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/02/20/beware-crawling-the-non-default-zone-for-a-sharepoint-2013-web-application.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10395668" width="1" height="1"&gt;</content><author><name>bspender</name><uri>http://blogs.msdn.com/bspender_4000_gmail.com/ProfileUrlRedirect.ashx</uri></author><category term="Troubleshooting" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Troubleshooting/" /><category term="Crawling" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Crawling/" /><category term="Query" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Query/" /><category term="SharePoint 2013" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/SharePoint+2013/" /><category term="AAMs" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/AAMs/" /></entry><entry><title>Troubleshooting App Management WCF Endpoint Failures</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/01/29/troubleshooting-app-management-wcf-end-point-failures.aspx" /><id>http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/01/29/troubleshooting-app-management-wcf-end-point-failures.aspx</id><published>2013-01-30T04:29:00Z</published><updated>2013-01-30T04:29:00Z</updated><content type="html">I was recently setting up federated search for SharePoint 2013 using Result Sources to a Remote SharePoint farm. That has already been extremely well documented by Steve Peschka , but did want to dive into the following error with the App Management service that I encountered along the way because it helps illustrate tactics for troubleshooting endpoint failures. 
 
 Personally, the message " Get-SPAppPrincipal : There are no addresses available for this application " gives me little indication...(&lt;a href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/01/29/troubleshooting-app-management-wcf-end-point-failures.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10389371" width="1" height="1"&gt;</content><author><name>bspender</name><uri>http://blogs.msdn.com/bspender_4000_gmail.com/ProfileUrlRedirect.ashx</uri></author><category term="Troubleshooting" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Troubleshooting/" /><category term="Explained" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Explained/" /><category term="SharePoint 2013" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/SharePoint+2013/" /><category term="Topology" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Topology/" /><category term="PowerShell" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/PowerShell/" /><category term="SSA" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/SSA/" /></entry><entry><title>PowerShell to Rebalance Crawl Store DBs in SP2013</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/01/28/powershell-to-rebalance-crawl-store-dbs-in-sp2013.aspx" /><id>http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/01/28/powershell-to-rebalance-crawl-store-dbs-in-sp2013.aspx</id><published>2013-01-29T02:58:00Z</published><updated>2013-01-29T02:58:00Z</updated><content type="html">In SharePoint 2013, simply adding a new Crawl Store DB doesn't cause the SSA to rebalance links among stores, and admins are unable to manually trigger a rebalancing process until the standard deviation of links in all existing Crawl Stores exceeds the threshold defined by the SSA property CrawlStoreImbalanceThreshold . 
 Once this threshold is reached eventually, the Search Admin UI displays a control that allows the administrator to initiate the rebalancing process. Specifically, the CrawlStoresAreUnbalanced...(&lt;a href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/01/28/powershell-to-rebalance-crawl-store-dbs-in-sp2013.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10389018" width="1" height="1"&gt;</content><author><name>bspender</name><uri>http://blogs.msdn.com/bspender_4000_gmail.com/ProfileUrlRedirect.ashx</uri></author><category term="Crawling" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Crawling/" /><category term="Explained" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Explained/" /><category term="SharePoint 2013" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/SharePoint+2013/" /><category term="Topology" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Topology/" /><category term="PowerShell" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/PowerShell/" /></entry><entry><title>SharePoint 2010: Crawl process is stuck after SQL Server runs out of disk space</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2012/11/02/sharepoint-2010-sql-server-runs-out-of-disk-space.aspx" /><id>http://blogs.msdn.com/b/sharepoint_strategery/archive/2012/11/02/sharepoint-2010-sql-server-runs-out-of-disk-space.aspx</id><published>2012-11-02T19:48:00Z</published><updated>2012-11-02T19:48:00Z</updated><content type="html">Maybe this is cheating in terms of a blog post, but I wrote the bulk of this Support KB and wanted to share in as many ways as I could... 
 SharePoint 2010: Crawl process is stuck after SQL Server runs out of disk space http://support.microsoft.com/kb/2691203 
 Consider the following scenario: You initiate a full/incremental crawl of the content source(s) in your SharePoint 2010 environment. Once the crawl begins, you find that the Crawl Store database (e.g. something such as 'SSA_CrawlStoreDB...(&lt;a href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2012/11/02/sharepoint-2010-sql-server-runs-out-of-disk-space.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10365361" width="1" height="1"&gt;</content><author><name>bspender</name><uri>http://blogs.msdn.com/bspender_4000_gmail.com/ProfileUrlRedirect.ashx</uri></author><category term="Troubleshooting" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Troubleshooting/" /><category term="Workarounds" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Workarounds/" /><category term="Crawling" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Crawling/" /></entry><entry><title>SP2010 Search *Explained: Crawling</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2012/10/30/sp2010-search-explained-crawling.aspx" /><id>http://blogs.msdn.com/b/sharepoint_strategery/archive/2012/10/30/sp2010-search-explained-crawling.aspx</id><published>2012-10-30T16:43:00Z</published><updated>2012-10-30T16:43:00Z</updated><content type="html">In broad terms, SharePoint Search is comprised of three main functional process components: 
 
 Crawling (Gathering) : Collecting content to be processed 
 Indexing : Organizing the processed content into a structured/searchable index 
 Query Processing : Retrieving a relevant result set relative to a given user query 
 
 In a previous post, I discussed SharePoint Search Concepts and Terminology and now plan to continue by further exploring aspects of the Crawling process ( Note: although this...(&lt;a href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2012/10/30/sp2010-search-explained-crawling.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10364097" width="1" height="1"&gt;</content><author><name>bspender</name><uri>http://blogs.msdn.com/bspender_4000_gmail.com/ProfileUrlRedirect.ashx</uri></author><category term="FS4SP" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/FS4SP/" /><category term="FAST Search" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/FAST+Search/" /><category term="Search" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Search/" /><category term="Concepts" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Concepts/" /><category term="Crawling" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Crawling/" /><category term="Explained" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Explained/" /><category term="SharePoint 2013" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/SharePoint+2013/" /></entry><entry><title>Troubleshooting the SSP Search Indexer for MOSS 2007</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2012/09/10/troubleshooting-the-ssp-search-indexer-for-moss-2007.aspx" /><id>http://blogs.msdn.com/b/sharepoint_strategery/archive/2012/09/10/troubleshooting-the-ssp-search-indexer-for-moss-2007.aspx</id><published>2012-09-10T14:34:00Z</published><updated>2012-09-10T14:34:00Z</updated><content type="html">It's time to set aside my SharePoint 2013 farm and get into the way-back machine to troubleshoot the Indexer for MOSS SharePoint 2007 Shared Services Provider (SSP)... 
 (As I mentioned in a previous post on Search Terminology, I try avoiding the term "Indexer" because it has a muddied connotation in SharePoint 2010 &amp;amp; 2013. However, given this relates to SP2007, consider this post one of those exceptions) 
 Isolate failures that occur during a crawl (e.g. problems with the content being crawled...(&lt;a href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2012/09/10/troubleshooting-the-ssp-search-indexer-for-moss-2007.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10347834" width="1" height="1"&gt;</content><author><name>bspender</name><uri>http://blogs.msdn.com/bspender_4000_gmail.com/ProfileUrlRedirect.ashx</uri></author><category term="Troubleshooting" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Troubleshooting/" /><category term="Workarounds" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Workarounds/" /><category term="SSP" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/SSP/" /></entry><entry><title>Deploying SharePoint 2013 SSA Across Multiple Servers Using PowerShell </title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2012/08/24/deploy-sharepoint-2013-ssa-across-multiple-servers-using-powershell.aspx" /><link rel="enclosure" type="application/octet-stream" length="7229" href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-components-postattachments/00-10-34-33-93/sp2013_2D00_buildSSA.ps1" /><id>http://blogs.msdn.com/b/sharepoint_strategery/archive/2012/08/24/deploy-sharepoint-2013-ssa-across-multiple-servers-using-powershell.aspx</id><published>2012-08-24T20:31:00Z</published><updated>2012-08-24T20:31:00Z</updated><content type="html">Update: Since the release of SharePoint 2013 RTM, I've made some modifications in an effort to simplify things (e.g. removing the unnecessary command line parameters) as well as improving the functionality (e.g. ability to provision multiple index partitions, register a Managed Account, clean up the inactive topology at the end). The core functionality has remained largely the same as the previous script, so it should still work, too. 
 As always, I'm interested to hear your feedback, suggestions...(&lt;a href="http://blogs.msdn.com/b/sharepoint_strategery/archive/2012/08/24/deploy-sharepoint-2013-ssa-across-multiple-servers-using-powershell.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10343393" width="1" height="1"&gt;</content><author><name>bspender</name><uri>http://blogs.msdn.com/bspender_4000_gmail.com/ProfileUrlRedirect.ashx</uri></author><category term="Search" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Search/" /><category term="SharePoint 2013" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/SharePoint+2013/" /><category term="Topology" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/Topology/" /><category term="PowerShell" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/PowerShell/" /><category term="SSA" scheme="http://blogs.msdn.com/b/sharepoint_strategery/archive/tags/SSA/" /></entry></feed>