Hello, I am having a very strange problem. System got .Net 1.0, 1.1 and 2.0 installed. Performance counters are working for 1.0 and 1.1 but for 2.0 it is not recording anydata. I tried following things: 1) http://support.microsoft.com/kb/267831 2) net stop iisadmin /y net stop "remote registry"...

Hello, We are running IIS6, with .NET framework 1.1 on Windows 64-bit. Therefore ASP.NET is running in 32-bit mode. The ASP.NET performance counters are only available when using the 32-bit version of perfman (from WinWOW64 folder) locally. Remote connections to perfmon only show 64-bit counters. Is...

Hi Everyone, 1) Use PHP as isapi module 2) Open Internet Information Services (IIS) Manager > Right Click On "Web Sites" select properties > Click Service Tab > Open HTTP Compression > Select Compress Application Files and Compress Static Files 3) Open Internet Information Services...

Hi! I am running a web site on an Windows Server 2003, IIS6 with a 3 GHZ dual core, 3gb ram and ASP.NET 2.0. Currently, the response times are extremely slow, maybe 10-15 seconds (even on pages with very quick database queries). The cpu is usually up at 100%, averaging between 97-100%, almost all the...

hi I suggest you read this article http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/webapp/iis/iis6perf.mspx Covers more topics to your query, but I think you will be very useful

Thanks for you replies. This server is in production as of now hence it is not possible to do stress testing again and use any tool. I would like to know that is this issue related to networking problem or IIS ASP.Net problem? Uday

Dear, While doing stress testing, I am receiving HTTP error 504. Its literal meaning suggest that it is "Gateway Time out" error. I am not quite sure whether it is networking issue or am I maxing out my worker process thread limits. I am running IIS 6 with ASP.Net 2.0 and all process model...

The KB article you posted is for asp.NET, not asp.dll (classic asp) so changing those settings will not make ASP improve. You have a problem with hte way your ASP application has been coded; you should investigate where the performance bottlenecks might be. The threads running ASP are taking too long...

This is good info and actually the first time that someone EVER (between the lines) told me that you actually have to take a possible network latency in consideration when you see this problem. At the TechED,Barcelona I asked Wade Elmo who is Program manager on IIS7 and he told me that the answer to...

Indeed true about the long running pages. But at one customers site we have a phenomenon that cannot possibly be something serverside. What we see are clients issuing GET's where amongst those some of them are for a .gif. Now that .gif is only 57kb in size and nothing is actually "processed"...