SharePoint Logs - Tracing Service lost trace events

So in the farm I'm trying to deploy to, the tracing service starting logging some "failed to write template" messages. Thousands of them. Nobody was on the machine at the time. It wasn't available to anyone so it was internal to SharePoint, whatever it was. Then it suddenly turned into the "Tracing Service lost trace events" log entries. Finally, it stopped logging altogether.

I found in a forum post on MSDN that when this happens, you need to restart the Windows SharePoint Service Tracing service.

SharePoint immediately started logging the events appropriately.

 I love SharePoint and I also hate it.

10 Comments

  • Thanks! That fixed the problem I was seeing!

  • Awesome thanks for taking the time

  • That piece of info saved lot of time...thanks...

  • Hi, thanks for this post. Although it didn't help me, I think it is a very useful post. The problem I am having is similar where the service stops tracking events however, when I try to restart the service, the service gets stuck in the stopping status and never starts up again. I then have to reboot the system, which is not something I like due to the fact that this is a production server. Once I do to restart the system, the service works for just a couple of hours and then stops tracing again

    Have you heard of this or do you know how to forcefully restart the service?

    Thanks for any help you provide.

    MAV

  • Does anyone have a problem where the Windows SharePoint Service Tracing service gets stuck in a 'stopping' state when you try to restart it?

    I've tried to kill the process by using tools like pskill.exe, taskkill.exe, process explorer etc but nothing actually kills it. I'm desperately trying not to reboot our prod box.

  • You can try the net stop wsstracing.exe -force sometimes that helps.

  • Thanks! That solved my problem :)

  • And what if the logging DOESN'T start after restarting the service? I can't reboot this production server as often as my logging dies.

    Thanks for any help

  • Thanks! That fixed the problem.

  • Thanks, saved me lots of time and hair tearing. :-)

Comments have been disabled for this content.