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:

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.

Your Answer


By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

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