<< Back To All Blogs
Resolving "Tracing Service lost trace events" in MOSS 2007
Saturday, May 1st, 2010
I recently came across an issue while attempted to debug some MOSS workflow. My workflow was terminating with an error, but upon doing some deeper digging into the log files I realized that the only error appearing was "Tracing Service lost trace events. Current value 1."
An incredibly useful and descriptive SharePoint error, as expected.
This occurs when the SharePoint tracing service is erroring for whatever reason. Restarting the service named "Windows SharePoint Services Tracing" fixes the problem.
A short post, but as always, SharePoint never fails to amaze me.
Tracin' Tom Out.
Configuring ASP.NET (And SharePoint) to use SQL-based Sessions
Receiving null value when using SPFarm.Local on SharePoint 2010
Adding a Custom ASP.NET Page to MOSS/WSS
Adding Custom Menu Item to MOSS/WSS List Actions Menu
Currently no comments.
Add A Comment
Email Address: (not public, used to send notifications on further comments)
Enter the text above, except for the 1st and last character: