Thankyou for your assistance.
When I do change http://localhost/virtualdirectoryname/webpage.aspx
to http://localhost:8888/virtualdirectoryname/webpage.aspx and set a trace 
up to listen on port 8888, I DO see some data captured for trace.  However, 
after I've selected the web service on IE browser - and it still has 
localhost:8888 , when I actually click INVOKE, nothing is captured.  This is 
what I need.

So the actual address in my browser bar at this point is 
http://localhost:8888/appl01/webservices.asmx?op=GetAllWorkStation

When I click INVOKE from this page - nothing is captured.  When the results 
of this invoke come back to my browswer, they have location URL 
http://localhost/appl01/webservices.asmx/GetAllWorkStation.  Not sure if it 
matters that the 8888 port is not there.  

So, in summary I see traces of when pulling up main aspx page and when 
selecting a particular web method.  However, when invoking the web method, I 
cannot see the trace.  Can you please provide some more tips?  

Thank you,
Tim
"Steven Cheng[MSFT]" wrote:

> Hello Tim,
> 
> As for the Trace Utility tool, it functions similarly as some other 
> tcp/http trace tools (such as TcpTrace ). When we start a trace session, we 
> just need to specify the following things:
> 
> 1. The certain local port we want to listen on 
> 
> 2. The destination machine we will forward/redirect the data to
> 
> 3. The destination port (on the destination machine we specify in #2) we 
> will forward/redirect the data to
> 
> And for your scenario, you want to trace the SOAP messages of a certain 
> webservice method calls, you can follow the below steps:
> 
> #suppose the webservice is hosted in IIS on serverA and can be  accessed by 
> the address like:
> 
> http://serverA/serviceapp/service1.asmx
> 
> 
> 1) if you use trace utility on the client machine:
> 
> **start trace utility and choose to create a formatted trace
> 
> ** in the popup setting dialog, set the local port, destination port, 
> destination host as below:
> 
> local port:  any unoccupied port on client machine(such as 8888)
> 
> destination host:  network name or ip address of serverA
> 
> destination port:  80  (because the webservice is hosted in IIS on serverA 
> which listen on 80 port)
> 
> **After start the trace session, you need to do the following change in 
> your webservice client proxy code or in IE when try accessing the 
> webservice:
> 
> change  the address from 
> 
> http://serverA/serviceapp/service1.asmx
> 
> to 
> 
> http://localhost:8888/serviceapp/service1.asmx
> 
> Because the trace utility tool will help forward your request mesage from 
> "localhost:8888" to   "serverA(:80)". Thus, the utility can capture all the 
> messages transfered through this trace session/channel.
> 
> 
> 
> 2) if you use the trace utility on the server machine:
> 
> **start trace utility and choose to create a formatted trace
> 
> ** in the popup setting dialog, set the local port, destination port, 
> destination host as below:
> 
> local port:  any unoccupied port on client machine(such as 8888)
> 
> destination host:  localhost (because you are perform the trace on server 
> machine locally)
> 
> destination port:  80  (because the webservice is hosted in IIS on serverA 
> which listen on 80 port)
> 
> **After start the trace session, you need to do the following change in 
> your webservice client proxy code or in IE(on client machine) when try 
> accessing the webservice:
> 
> change  the address from 
> 
> http://serverA/serviceapp/service1.asmx
> 
> to  
> 
> http://serverA:8888/serviceapp/service1.asmx
> 
> Because the trace utility tool is listening on the server machine and will 
> forward any messge from client to the 8888 port to 80 port. Thus, the 
> utility can capture all the messages transfered through this trace 
> session/channel.
> 
> Hope this help clarify the utility usage some. If you have anything unclear 
> on the above description or anything I missed, please feel free to post 
> here.
> 
> Sincerely,
> 
> Steven Cheng
> 
> Microsoft MSDN Online Support Lead
> 
>  
> 
> ==================================================
> 
> Get notification to my posts through email? Please refer to 
> 
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
> 
>  
> 
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues 
> where an initial 
> 
> response from the community or a Microsoft Support Engineer within 1 
> business day is 
> 
> acceptable. Please note that each follow up response may take approximately 
> 2 business days 
> 
> as the support professional working with you may need further investigation 
> to reach the 
> 
> most efficient resolution. The offering is not appropriate for situations 
> that require 
> 
> urgent, real-time or phone-based interactions or complex project analysis 
> and dump analysis 
> 
> issues. Issues of this nature are best handled working with a dedicated 
> Microsoft Support 
> 
> Engineer by contacting Microsoft Customer Support Services (CSS) at 
> 
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> 
> ==================================================
> 
>  
> 
> This posting is provided "AS IS" with no warranties, and confers no rights.
> 
> 
> 
>