Tracing Service lost trace events
February 12, 2009 5 Comments
If you are receiving this error within the ULS logs in SharePoint 2007 (x:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS\), and the error is as follows:
Tracing Service lost trace events. Current value n.
(Where n is a numeric value) – the best course of action to take to remedy this is to restart the Windows SharePoint Services Tracing service within the services console on your Windows server.
Usually if you are seeing this error in the ULS logs, you are most likely not seeing any other log entries at all. The ULS logging service is basically just posting a message to the logs saying that it is having issues hooking up with the service that SharePoint speaks to.
This is a short post, however, it should get you back on track. As I research this issue further, I will update this blog entry with possible causes and additional solutions for resolving this issue. This is definitely not the first time I have run into the issue, but, I wanted to at least make a quick posting about it to share the “quick fix” for now.
About Geoff Varosky
Geoff Varosky's Blog 
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 againHave you heard of this or do you know how to forcefully restart the service? Also, do you know if this is fixed on any of the updates or will be fixed in SP2?Thanks for any help you provide.MAV
Marco,Thanks! I have not personally seen the issue before, and unfortunately do not know if this is fixed within any of the cumulative update packages to date, hotfixes packages, or the upcoming SP2. I will keep an eye out however, and if I do find anything, I will post back here to let you, and anyone else know.Almost sounds similar to the "Timer Job Shocker" issue that many people have experienced in the past (see: http://support.microsoft.com/?id=946517). If that fixes you up – please let me know.If anyone else visiting this post has any idea, please post a comment! I will update the post with that relevant information is well.
Thanks Geoff. Unfortunately the link didn\’t help me but I do appreciate the help. I\’m still trying to find a solution for this problem. Thanks for any help provided.
Did you check the ULS Log Level Settings? Usually this Error also is a good indicator for a to granular loglevel. In most cases when I saw this error the log (or the trace service) was kind of flodded with information logs before he suddenly "shut down"…
Their vodka battered onion rings and fried pickles are
awesome and they always have an amazing salad on the menu.