Dilip Krishnan wrote:
> Hello SQLAgentman,
> * Input/Output trace is just a trace of the messages going in and
out of
> the WSE pipeline. You should see that the Output trace of the client
should
> match the input trace of the server, because all its doing is logging
the
> envelope that is being sent or received. On the outbound its after it
has
> passed through all the filters.. and in the inboud its before it
passes through
> any of the filters.
> * The Send and recieve policy is just a trace of all the policies
that the
> server went through. Usually you need this only when you want to find
out
> why you're getting a WSE402?!? policy verification error or WSE405,
the policy
> enforcement error (provided you havent written any custom policy, in
that
> case you have the code to figure what the problem is :))
>
> A very good tool that I think is real useful is the WSE trace tool
>
http://weblogs.asp.net/smguest/archive/2004/08/19/217394.aspx > Its really good to correlate messages and also shows you the
certificates
> that were used to sign/encrypt a message..
>
> HTH
> Regards,
> Dilip Krishnan
> MCAD, MCSD.net
> dkrishnan at geniant dot com
>
http://www.geniant.com >
> > Hi everyone,
> >
> > Is there a list of things to look for in the OutputTrace.webinfo or
> > the Message Trace and Policy Trace Output and input files.
> >
> > I just need to put my head around this.
> > I need some paper or article that explains what to look for and how
to
> > campare the files on the client side and the server side.
> > Any comments, links, chapters, books, articles etc.. are
> > appreciated....
> > Usually a summary from some experts helps alot..
> > Thank you,
> >
> > Sql
> >
