<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wcf on Matt Thornton</title>
    <link>http://localhost:1313/tags/wcf/</link>
    <description>Recent content in Wcf on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 17 Jan 2018 11:58:09 +0000</lastBuildDate><atom:link href="http://localhost:1313/tags/wcf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SharePoint Search Service Application recovery &#43; WCF Endpoint</title>
      <link>http://localhost:1313/tech/sharepoint-search-service-application-recovery-wcf-endpoint/</link>
      <pubDate>Wed, 17 Jan 2018 11:58:09 +0000</pubDate>
      
      <guid>http://localhost:1313/tech/sharepoint-search-service-application-recovery-wcf-endpoint/</guid>
      
        <description>&lt;p&gt;I recently had some fun and games trying to fix a broken SharePoint Search Service Application. Although I&amp;rsquo;m not entirely what caused the issue (other than, you know, SharePoint) although it may be to do with changing the &lt;a href=&#34;https://www.matt-thornton.net/tech/sharepoint/sharepoint-passphrase-recovery&#34;&gt;Farm Passphrase&lt;/a&gt; but one way or another it was, fooked.&lt;/p&gt;
&lt;p&gt;I opted to just delete it and create a new one. This didn&amp;rsquo;t go well. A new application was created, but it, also, was dead.&lt;/p&gt;
&lt;p&gt;As many people have found, Central Admin and Remove-SPServiceApplication have a habit of doing entirely nothing when it comes to remove broken Search Applications.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>