Ramblings & Controls from a .NET Addicted Freak!

Kevin Gearing's Blog

February 2005 - Posts

  • Slow Opening Web Project with Visual Studio .NET and w3wp.exe

    Following on from my previous post, I've also started to experience another problem. This time with Visual Studio .NET and it taking forever to open a Web Project.

    Whilst testing I noticed that opening the Web with FrontPage was as quick as I would expect, however when opening with Visual Studio, it took forever. After it had been opened with Visual Studio, trying to re-open with FrontPage was also extremely slow.

    I noticed on the server, that two w3wp.exe processes were being spawned, one running under 'System' and one running under 'Network Service'. Whilst opening with Visual Studio, if I switch to the server and kill the process running under 'System', it opens the project immediately... strange!

    Research on Microsoft's knowledgebase points to an article which has a hotfix available. However, upon contacting Microsoft, it would appear that this hotfix has been withdrawn and replaced with a new one, which I was sent. Unfortunately this didn't solve the problem, and as I'm not prepared to pay the £185+ fee to find out what's causing it, killing a second process when it happens, is a cheap workaround.

    I believe MS are aware of this problem and it should be fixed in the .NET Framework v1.1 SP2.

  • ASP.NET, w3wp.exe, 100% CPU Usage and McAfee VirusScan Enterprise

    Recently I've been experiencing a strange problem on one of our development servers that was hosting an ASP.NET application. The server in question was running Windows Server 2003 with IIS6 and VirusScan Enterprise v8.0i.

    I was noticing that any ASP.NET page that was being hit would cause the CPU usage to jump to 100% for a period of a few seconds, before returning to it's typical 2-3% - The offending process? w3wp.exe.

    I ruled out (as far as possible) the application as the fault, simply because the same application was running on a Windows 2000 Server as well as an identical Windows Server 2003 without any issue.

    Running adplus (Windows Debugging Tools) revealed some interesting information, but nothing concrete. Further investigation pointed me to possibly McAfee VirusScan Enterprise, which had recently been upgraded and was a different version to that running on the other servers.

    To cut a long story short, McAfee have introduced 'Buffer Overflow Protection' into VirusScan Enterprise v8.0i, which if set to 'Protection Mode' seems to interfere with w3wp.exe and throw the processors to 100% - disable it and no problem.

    So, if you're running VS Enterprise v8.0i and start seeing strange 100% CPU usage, check that you have 'Buffer Overflow Protection' disabled, or set to 'Warning Mode', which might also solve the problem - For me, disabling is the route I'm going...

Copyright ©2004-2007 Kevin Gearing. All Rights Reserved.
Powered by Community Server (Non-Commercial Edition), by Telligent Systems