maxAllowedContentLength in IIS 7
After migrating some of my webapps from IIS 6 to IIS 7, I noticed that I was no longer able to upload files larger than 30 MB. It turns out there is a new setting in IIS 7 which by default restricts maximum allowed content length for a request to 30 MB.
The typical error message you will see in your browser is “The connection to the server was reset while the page was loading.” or something similar.
To allow uploading of larger files than 30 MB, you can add this to your web.config file.
<system.webServer> <security> <requestFiltering> <requestLimits maxAllowedContentLength="1000000" /> </requestFiltering> </security> </system.webServer>
Running an ASP.NET website on 64-bit
I'm in the process of migrating our old Windows Server 2003 boxes (32 bit) to Windows Server 2008 (64 bit) boxes and have several ASP.NET websites that have to be moved. After setting up the websites on the new box, I got this error:
"Could not load file or assembly 'System.Data' or one of its dependencies. An attempt was made to load a program with an incorrect format."
One way of solving the problem was to enable the option "Enable 32-Bit Applications" on the IIS application pool, to force the worker process to run in 32 bit mode. This works, but is no good, because I want the app to run in 64 bit mode.
After some poking around, and by using a tool called corflags.exe, I found out that my webapps had a separate copy of System.Data.dll in their bin folders, which was loaded instead of the installed 64 bit versions of System.Data.dll. The problem was fixed by deleting these dlls from the webapp's bin folder. Tada!
Some more great info on the same topic can be found in the great blog post 32bitness and 64bitness and migrating DasBlog on IIS7 and ASP.NET under Vista64 written by Scott Hanselman.
Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode
Today I installed VMware Server in order to run Windows Server 2008 x64 as a guest OS. My laptop has a 64 bit processor and I'm running Windows 7 x64 on it, so I assumed it should work just fine to install Windows Server 2008 x64 in WMware. However, when trying to boot from the installation DVD, I got the error "Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode." as shown in the screenshot below.

To make sure the CPU was really able to run 64 bit, I downloaded and ran the Workstation Processor Check for 64-Bit Compatibility. As expected, this tool showed that the CPU should work just fine with a 64-bit guest OS.

After some more investigation, it turns out there is a BIOS setting for enabling virtualization. After enabling "Intel Virtualization Technology", the problem was fixed.

How to find out what application pool is using CPU
Recently, one of my web servers was using a lot of CPU. This server is hosting several websites, each running in it’s own application pool. Each application pool spins up it’s own w3wp.exe process. When looking at task monitor, there is no information about what application pool each of the worker processes are serving.
You could however, easily figure this out by running a great tool called Process Explorer, which is a freely available tool from Sysinternals/Microsoft.
To figure our what application pool is consuming most CPU, start Process Explorer. You'll then see a window similar to the one below. Find the w3wp.exe process that consumes most CPU, right click on it and select "Properties".

In the properties window, click the tab "Environment". You'll there find the name of the app pool as shown below.

Updates on stoverud.com
If you have visited this website recently (or not so recently) you have might noticed that it has not been updated since 2002. I'm not going to add a lot of new content, but I thought it was better to have nothing, than to have a whole lot of outdated content.
If you for some reason were looking for some of the old contents on this website, here are some links:



