Thursday, November 20, 2008

SharePoint Logs – Tracing service lost trace events

Some time, my SharePoint logging didn’t work properly for some reason, if I looked into my SharePoint Logs directory then in every generated log file, I have found below lines.

Date and time        wsstracing.exe        (0x07E4) 0x1634         ULS Logging  Unified Logging Service uls1        Monitorable              Tracing Service lost trace events.           Current value 8.


I need to restart my logging service, SharePoint uses "Windows SharePoint Services Tracing" service for writing logs into ULS logs, so I went to services and restarted my "Windows SharePoint Services Tracing" services, once I did that, a new logs was created into SharePoint logs file. I also found out that might be this errors showed due to upgrade of service pack 1.


  1. 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? 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.


  2. Hey Mav,

    Thanks for your comments.

    Actually I have also faced same problem many times, in my case also, I have to restart the system because when I restart the service, it gets stuck, we can set the forcefully restart of the service, but somehow it didn't work.

    We can forcefully restart the service from going to service tracing properties and "Recovery" tab, but many times, it didn't work.

    There are no updates or patch fix for this problem, but I'll keep looking for the same and will post you here if I find anything.

    Thanks again,

  3. Thanks Sanket. Appreciate all of you help.