“Service Unavailable (HTTP 503)” and Response.TransmitFile() problems on Windows Server 2003
During QA testing of a new Asp.Net web site, in our customers production environment, we ran into the above 2 problems intermittently.
When requesting the default page (or any page, even static htm files) from the site, the web browser would sometimes get “Service Unavailable” errors (both IE and FireFox). We were also seeing our C# code used to download files securely (see the Downloading Files Securely with Asp.Net post) not functioning properly; the web browser would just render a blank page, and never receive the file.
These problems did not occur in our test environment, so initially we assumed it was some environmental / configuration issue.
The Network/Web Administrator finally realized his configuration choice of ‘Throttle Bandwidth” for the IIS Site was the source of the problem.
This option can be enabled/disabled and configured for the entire web server and/or individual sites (application pools). The site level configuration overrides the server setting for that site.
I have a decent understanding of the implementation of Bandwidth Throttling in IIS 6 (relative to the HTTP.sys listener in kernel mode, content caching, and application pools). Documentation of this topic seemed poor from some initial Googling and MSDN Library searches. I am not going to attempt to explain my understanding of the implementation here…keeping it simple.
This setting can affect both inbound and outboud network traffic! (Both your HTTP Request and Response streams)
Technologies
Visual Studio .Net 2003, SQL Server 2000, C#, Asp.Net, Windows Server 2003, IIS 6
Related Links
When requesting the default page (or any page, even static htm files) from the site, the web browser would sometimes get “Service Unavailable” errors (both IE and FireFox). We were also seeing our C# code used to download files securely (see the Downloading Files Securely with Asp.Net post) not functioning properly; the web browser would just render a blank page, and never receive the file.
These problems did not occur in our test environment, so initially we assumed it was some environmental / configuration issue.
The Network/Web Administrator finally realized his configuration choice of ‘Throttle Bandwidth” for the IIS Site was the source of the problem.
This option can be enabled/disabled and configured for the entire web server and/or individual sites (application pools). The site level configuration overrides the server setting for that site.
I have a decent understanding of the implementation of Bandwidth Throttling in IIS 6 (relative to the HTTP.sys listener in kernel mode, content caching, and application pools). Documentation of this topic seemed poor from some initial Googling and MSDN Library searches. I am not going to attempt to explain my understanding of the implementation here…keeping it simple.
This setting can affect both inbound and outboud network traffic! (Both your HTTP Request and Response streams)
Technologies
Visual Studio .Net 2003, SQL Server 2000, C#, Asp.Net, Windows Server 2003, IIS 6
Related Links
posted by Marty Supple at 2:18 PM
0 Comments:
Post a Comment
<< Home