SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So, after a clean install of SharePoint 2010 you sometimes get a warning that a service is using a built in account. This is found in yellow in the Monitoring panel in Central Administration.

Upon further examinination, the service at fault is SPTraceV4 (though the actual error on the console (rather than the error detail) is SPTimerServiceV4 is failing).

Sure enough, upon checking the windows services console, the account for SPTraceV4 is the built in local service account.

So, is there a proper way to update this account to something other than local service OR to prohibit its provisioning with a local service account? Is this a bug?

Another thread with similiar detail is here:

share|improve this question

If you really want to get rid of this somebody posted this complicated PowerShell script to fix it.

My personal view is that it seems like a lot of effort. I suspect it will be fixed in the next version, anyway. I am lazy and just disable the health rule. Sorry.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.