<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sharepoint Trace Service on Matt Thornton</title>
    <link>https://matt-thornton.net/tags/sharepoint-trace-service/</link>
    <description>Recent content in Sharepoint Trace Service on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Fri, 23 Feb 2018 12:17:04 +0000</lastBuildDate><atom:link href="https://matt-thornton.net/tags/sharepoint-trace-service/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SharePoint trace service keeps getting disabled</title>
      <link>https://matt-thornton.net/tech/sharepoint/sharepoint-trace-service-keeps-getting-disabled/</link>
      <pubDate>Fri, 23 Feb 2018 12:17:04 +0000</pubDate>
      
      <guid>https://matt-thornton.net/tech/sharepoint/sharepoint-trace-service-keeps-getting-disabled/</guid>
      
        <description>&lt;p&gt;Continuing the theme of obscure SharePoint gotchas you&amp;rsquo;re unlikely to encounter (unless, I assume, you&amp;rsquo;re reading this) here&amp;rsquo;s another. One environment was experiencing an issue whereby the SharePoint Tracing Service was constantly getting set to disabled. No amount of editing it in services.msc to set it to Automatic would ‘take&amp;rsquo; - that is, you could enable it and start it and it would work - but then at some miscellaneous point later it would mysteriously revert to being disabled.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>