[…] shows the power of SPTraceView. So if you haven’t got it yet, you should get it NOW from here. Possibly related posts: (automatically generated)Standby Database Out of SyncError messages with […]
[…] registry key. You can monitor the ULS trace messages in real time using the very light-weight SPTraceView utility. For detailed information and best practices on disposing SharePoint objects see the […]
[…] SPTraceView « SharePoint Internals – Hristo Pavlov’s Blog SPTraceView is a utility targeted mainly for people that develop and/or test custom SharePoint applications. It could be also useful to administrators to diagnose and troubleshoot their MOSS farm. It analyses in real time the ULS trace messages coming from all MOSS components and can notify you using a balloon-style tray bar messages when something happens. […]
[…] To fill the gap and facilitate troubleshooting, free third-party tools exist like LogViewer, SPTraceView and WSS/MOSS Log File Reader .Some utilities including SPTraceView will aggregate log data from […]
[…] To fill the gap and facilitate troubleshooting, free third-party tools exist like LogViewer, SPTraceView and WSS/MOSS Log File Reader .Some utilities including SPTraceView will aggregate log data from […]
SharePoint Internals - Hristo Pavlov's Blog 
[…] More information about how to use SPTraceView and how it works is available on its own page. […]
Pingback by SPTraceView - Lightweight Tool for Monitoring the SharePoint Diagnostic Logging in Real-Time « SharePoint Internals - Hristo Pavlov’s Blog — 19 June, 2008 @ 11:57 pm
Awesome work Hristo!
Comment by Nick Cox — 20 June, 2008 @ 5:19 am
[…] shows the power of SPTraceView. So if you haven’t got it yet, you should get it NOW from here. Possibly related posts: (automatically generated)Standby Database Out of SyncError messages with […]
Pingback by Operation aborted (Exception from HRESULT: 0×80004004 (E_ABORT)) « SharePoint Internals - Hristo Pavlov’s Blog — 2 July, 2008 @ 4:33 am
[…] registry key. You can monitor the ULS trace messages in real time using the very light-weight SPTraceView utility. For detailed information and best practices on disposing SharePoint objects see the […]
Pingback by Understanding SharePoint: SPRequest « SharePoint Internals - Hristo Pavlov’s Blog — 19 January, 2009 @ 4:07 am
Yet another tool to add to my standard SharePoint deployment kit (Having it available but not enabled, of course).
Great work Hristo.
Comment by Brad Saide — 7 March, 2009 @ 11:39 am
[…] SPTraceView « SharePoint Internals – Hristo Pavlov’s Blog SPTraceView is a utility targeted mainly for people that develop and/or test custom SharePoint applications. It could be also useful to administrators to diagnose and troubleshoot their MOSS farm. It analyses in real time the ULS trace messages coming from all MOSS components and can notify you using a balloon-style tray bar messages when something happens. […]
Pingback by links for 2009-03-25 « Murratore’s Weblog — 26 March, 2009 @ 12:01 am
[…] SPTraceView. […]
Pingback by WSS 3.0 & MOSS: Algunas herramientas de depuración (I)! « Pasión por la tecnología… — 29 March, 2009 @ 5:28 pm
[…] SPTraceView. […]
Pingback by WSS 3.0 & MOSS: Algunas herramientas de depuración (I)! - Blog del CIIN — 29 March, 2009 @ 5:28 pm
[…] last thing I want to do is make the SPTraceView utility open source. However I don’t have the time to manage this. So I am looking for an […]
Pingback by My Last Post in ‘SharePoint Internals’ « SharePoint Internals - Hristo Pavlov’s Blog — 6 April, 2009 @ 12:23 am
[…] To fill the gap and facilitate troubleshooting, free third-party tools exist like LogViewer, SPTraceView and WSS/MOSS Log File Reader .Some utilities including SPTraceView will aggregate log data from […]
Pingback by Reduce to bare bones of SharePoint debugging by creating the snagexecution toolbox « Aswath’s Blog — 21 April, 2009 @ 8:42 am
[…] To fill the gap and facilitate troubleshooting, free third-party tools exist like LogViewer, SPTraceView and WSS/MOSS Log File Reader .Some utilities including SPTraceView will aggregate log data from […]
Pingback by Simplifying SharePoint debugging by creating the troubleshooting toolbox | SharePoint Magazine — 6 November, 2009 @ 8:46 am
Do you have any plans to support SharePoint 2010? It sure would be nice!
Comment by wesmacdonald — 7 June, 2011 @ 8:39 pm