Microsoft Support Team's IIS Blog
-
Caution while xcopying IIS 7.0 config files
Metabase.xml is the central store where IIS 6.0 stores most of its configuration information. Its a plain text file and stores all the information in a simple XML format. The XML format naturally raised a notion of being able to XCOPY the config file to another server and transferring the settings with it. But if you copy over a metabase.xml file from another server your IIS admin service will no longer start. This happens because the metabase.xml file contains ACLs that control access to any metabase key. Stored under the AdminACL tag these keys are encoded based on the machinekeys of the server. When you move the metabase.xml to another server the keys can no longer be decoded and hence your IIS Admin service will not be able to start.
-
Changes to Application Pool identities in IIS 7.5 [BETA]
IIS 6.0 introduced a lot of features to increase reliability and security. As an architectural change the worker process w3wp.exe was introduced. To increase security IIS 6.0 by default launched the worker process using the NTAuthority\Network Service account. Network Service is a low privilege predefined account that was introduced in Windows 2003. All guidance/documentation recommend running the worker process under the Network Service.
-
High Memory due to System.WeakReference
-
ASP.NET - AJAX functionality not working on the page | Getting ‘Sys’ is undefined
When the ASP.NET AJAX Functionality is not working on a web page, it is usually due to the fact that the javascript needed for AJAX is not sent to the client from the server for some reason.
-
Troubleshooting HTTP Compression in IIS 6.0
Cross-posted from http://blogs.msdn.com/mike
-
Internet Explorer resets the TCP connection after receiving an HTTP response from IIS
A problem was seen where Internet Explorer clients would reset the TCP connection between them and the IIS server when they received an HTTP 200 response for static content from IIS. The problem manifests itself to end users as slow performance of the web application they are browsing to. In a network trace, we could see that when the client was making its request, it was including the If-None-Match and If-Modified-Since headers in its request. It was doing this because the client (IE) had a version of the requested resource already in its client-side cache. By sending these headers, the client is essentially telling the web server to only send the resource back as a response IF the content is newer than that which is in the client side cache. The client's request looks like this:
-
HTTP 400 Bad Request when client terminates request headers improperly
-
HTTP 400 Bad Request when client sends invalid HTTP:Host header value
-
SCCM 2007 Charting functionality does not work on 64 bit IIS
System Center Configuration Manager (SCCM) has a nice functionality of displaying report data as charts. When deployed on a 64 bit IIS 6.0 machine these chart displays may stop working and you will start getting the following error message.
-
ASP.net Hang in IIS 7.0
When hosting an ASP.net web application on IIS7, and you have the application running in integrated pipeline mode, you may find that users complain that the application performs slowly. This may occur if your website is busy, handling 12 or more requests concurrently, and those requests are handled asynchronously as opposed to synchronously. The same application may appear to not suffer from poor performance when hosted on an IIS 6.0 server, or if the IIS7 site is set to run in Classic mode.