SPTraceView Analyses in real time the ULS trace messages coming from all MOSS components
Download

SPTraceView Ranking & Summary

SPTraceView Tags

SharePoint trace tracer ULS Viewer ULS Log ULS MOSS Column MOSS MOSS Indexing Server SharePoint Event ULS Trace Message Message Tracer MOSS Package Creator Create MOSS Package MOSS Feature MOSS Recovery MOSS Task Builder MOSS environment MOSS Plugin ULS class Carrie Anne Moss MOSS portal MOSS explorer analyses ratchet analyses

SPTraceView Description

The SPTraceView application was designed to be a small tool that 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 of interest happens. This functionality is 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. As soon as you run it, SPTraceView will start receiving all messages from MOSS and will start checking if any of them match filters defined by you. The default filter matches all messages which severity level is: Critical Event, Unexpected, Exception, Warning Event, Assert or Unassigned. You can configure your settings by choosing “Configure” from the context menu. The configuration form will show up and you will be able to choose the monitored levels and what you want SPTraceView to do when any of the messages match your filter. To configure an instance of SPTraceView to send the traced messages to other SPTraceView clients you should use the “Farm Trace Provider” mode. You will typically configure in this mode the instances of SPTraceView running in all servers in your farm but one. This will be the server where you will be monitoring all the traced messages from the other servers. On this machine you will need to configure SPTraceView to run as “Farm Trace Receiver”. It is important to know that the filters will be applied locally and only if a trace message matches the local filter it will be transmitted to other SPTraceView clients. So make sure you have the same filter settings in all servers. SPTraceView instances are using the UDP protocol to communicate between each other and the advanced settings form allows you to configure the communication settings. There are two modes of communicating: by using a multicast or a broadcast. If you are not sure what the difference is then use Multicast. To be able to communicate all running SPTraceView instances will have to use the same transport method: multicast or broadcast and must use the same port as well. By default SPTraceView is using port 12361. If you need to change it to a different port, then create a new DWORD registry value called Port under HKEYCURRENTUSER -> Software -> SharePointInternals -> SPTraceView and specify your custom port number. The multicast IP address cannot be changed and is always 232.153.23.255. Don’t worry it will work for your network as this is an IP address in the special multicast range.

SPTraceView Related Software