Sharepoint Foundation 2013: single cpu

wsstracing.exe is the service responsible for SharePoint logging. Such a high CPU-Usage for logging-service is not normal.

Some things to check:

• Go to SharePoint Central Administration -> Monitoring -> Configure diagnostic logging -> Check if any Categories are set to Verbose logging. Reset them to their defaults with the option Least critical event to report to the trace log
• Restart the SharePoint Tracing Service (SPTracev4) in Windows Services Console (services.msc)

• You might see the following errors in your ULS-Log: Trace Service encountered an unexpected exception when processing usage event. Detail exception message: Create store file error.. Win32 error code=5. This happens if the service account does not have proper permissions to logging-directory.

  • First get the correct user in services.msc:

  • This account should be a member in the following local groups: WSS_ADMIN_WPG and WSS_WPG
    

  • Get the ULS-Logging path in Central Administration -> Monitoring -> Configure diagnostic logging:

  • Check if permissions are correctly set on the logging folder. Both groups should have read, write and some special permissions: