Hi Nathan,

Since the performance is fine with W2k3 and worse with W2k, i would 
investigate what's different on the server environment.
I'm not an exchange expert so unfortunately i cannot help you diagnose what 
differences exist in the configuration of OS, Exchange, IIS that are 
affecting perf.
Try posting this on the exchange forums.

A general tool to "sniff" the network is NetMon [1], and you already have 
very useful info in the logs of IIS (assuming logging is active).

Hope this helps,

--VV [MSFT]
vascov@m...
This posting is provided "AS IS" with no warranties, and confers no rights.

[1] 
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/netmon/netmon/network_monitor.asp


"Nathan" <Nathan@d...> wrote in message 
news:71B971F4-1F98-444A-82FF-60A2455C90BC@m......
> Hello,
>
> I am running in to a performance bottleneck with a COM+ application that
> does a ServerXMLHTTP post to an exchange data store using WebDAV.
>
> I see the following works as desired performance when communicating to
> exchange 2003 on windows 2003 and slow down considerably on exchange 2003 
> on
> windows 2000.
>
> In general, here are my questions:
> 1.I believe the HTTP posts are slowing down. Is there a way I can monitor
> the time taken for a HTTP request to reach the server? Any performance
> counters/sniffing tool that can help. If you have better suggestion, 
> please
> do share.
> 2.CoCreateinstance of ServerXMLHTTP takes as high as 100 milliseconds in
> some instances. Is that ok?
> 3.The machine configuration is pretty good for app: I never see any 
> 80-100%
> CPU usage or high memory leak.It stays less than 50%
>
> Thanks for your time.
>
> Nathan
>