Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Defrag Tools: #72 - Message Analyzer - Part 2

11 minutes, 58 seconds


Right click “Save as…”

In this episode of Defrag Tools, Paul Long joins Chad Beeder in this 3 part series on Message Analyzer.

Message Analyzer Download Center
Message Analyzer Blog

[00:32] - Analyzing HTTP Traffic
[01:08] - Visualization
[03:36] - Viewing the Data
[05:39] - Request/Response time (TimeElapsed)
[07:12] - Server response time (ResponseTime)
[08:18] - Diagnostic column
[10:12] - Viewpoints - Protocol Layers
[11:26] - Email us your issues at defragtools@microsoft.com


Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation
  • Well, Paul I have now installed message analyzer and the issues that I was referring to are no longer a problem, it looks like they must have been cleared up, since the last time I looked at the documentation, it may have just been that I needed to restart the server or something, it is working fine on server 2012R2 for me now. Thank you for the tool...more things to learn for me now!

  • DarkWalkerDarkWalker

    I had to trace the source of some traffic a few months ago and used message analyser (it has Process ID column which is unavailable in other networks sniffers like WireShark), the problem was - this Process ID column was empty for packets that I had to track. Why is that? (it turned out to be that the source was Message Broker on SQL Server 2008 R2)

  • I'm not sure how you got an Process ID column that is empty.  I assume this was a Link Layer capture?  Which trace scenario did you use?  Was the traffic all of the same type (hint use grouping on Process ID)? 

    One thing about Process ID, is that it's more accurate for outgoing traffic.  In the case of incoming traffic, the Process ID could be based on the current process that happens to be busy at the time.  We do plan to expose a more high level process info at some point in the future.


Remove this comment

Remove this thread


Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.