Archives
-
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.
-
WebBaseEvent.Raise method fails in Application_Start event with a NullReferenceException on IIS 7.0
If you implement custom health monitoring events in ASP.NET chances are that you should have worked with WebBaseEvent or WebErrorEvent classes and used the WebBaseEvent.Raise() method to fire those events. Recently an interesting issue related to this WebBaseEvent.Raise() was brought to my notice.
-
Metabase auditing on IIS 7.5 [BETA]
Metabase auditing is a very useful feature which allows us to track changes that are made to the IIS metabase. It was introduced with SP1 on Windows 2003 (IIS 6.0). When enabled information such as time and user account that made the change to the metabase get logged to the event logs which can be very useful to track changes.
-
Report Viewer Toolbar does not render properly on IIS 7.0
I was recently working on a reporting web application that uses the Report Viewer ( ReportViewer ) control that ships with SQL Server Reporting Services (SSRS). The Report Viewer control was rendering perfectly when I was developing using Visual Studio 2008. The trouble started when I published the web application to an IIS 7.0 server. The Toolbar was completely broken and showed up something like this.
-
SSL stops working in IIS7
Thanks to Robert Patrick for submitting these issues
-
<location> Tag Causes Local Automatic ASP.NET debugging not to work in Visual Studio
This week I got an interesting issue altogether. One of my customers was unable to debug ASP.NET 3.5 application locally using Visual Studio 2008. The application was created using Web Application Project. When we started the application using "Start Debugging (F5)", page came up fine but debugger was not getting attached to process. In Visual Studio we could still see the "Play" button for starting debugging. We didn't get any errors either in Visual Studio or in Event Logs. At the same time when we try attaching the Visual Studio debugger manually then it worked fine.