Sharepoint - SPTraceV4 Being Disabled

This issue actually had nothing to do with storage space or permissions, as originally indicated. The problem was the Config database thought the SPTraceV4 service was supposed to be disabled by default. So when the Health Analyzer ran it turned the service off, disabled it as it thought it should.

The solution was found on a TechNet blog here. Not to pick on the author here, but the syntax needed to be cleaned up. Below is the correct PowerShell that worked to get GUID of the SPTraceV4 service on all servers on the farm.

((Get-SPFarm).Services | where {$_.Name -match "SPTraceV4"}).instances

or

((Get-SPFarm).Services | where {$_.Name -match "SPTraceV4"}).instances | Format-List

In addition to the GUID, the script also returns the default status of the service (Disabled or Online). The second script option above would be the preferred option for some if this is happening in a multiple server farm.

Once the service GUID was retrieved, the next PowerShell command enabled it on the respective server. So in a two server farm (ex serv1 and serv2), run the GUID for serv1 on serv1 and the GUID for serv2 on serv2.

Start-SPServiceInstance -Identity <Id>

The services were reset to start automatically and were started by the server itself. After manually running the Health Analyzer it continued working!

Big shout out to a team mate who helped push to find a solution.