windows-server-2008

What is the big deal with HTTP.SYS in IIS 7? From what I understand, it is low level which is good for security. Why? There is no context switching which could be expensive. Why? Please explain. Thanks! Lex Li The benefits are already well documented, http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/a2a45c42-38bc-464c-a097-d7a202092a54.mspx?mfr=true By using HTTP.sys to process requests, IIS 6.0 delivers the following performance enhancements: Kernel-mode caching. Requests for cached responses are served without switching to user mode. Kernel-mode request queuing.

We got a .NET WCF service that should be 100% uptime ideally. But sometimes we have a memory leaking issues in our application that caused by 3rd party DB connectivity component. We configured nnCron to watch for process existence and when the process of that service is exited, it should start it again. But when the app is crashing down windows pops up an noisy window informing that app has crashed. Here it is: And only when we click on dumb "Close the program" button, the process really disappearing from system. And only after that nnCron restart service. We don't want to monitor this window

I recently published my first MVC 2 project to a commercial web server, running Windows 2008, and which purportedly supports other MVC sites without issue, but have been experiencing some problems. Here is the high-level structure of the project. As you can see, it is very simple: But, after the site is published, and I navigate to the URL, I get "HTTP Error 403.14 - Forbidden: The Web server is configured to not list the contents of this directory." So, I contacted the web host about it and was told I had to include a default landing page, such as Default.aspx, Index.aspx, etc. I doubted this

We are receiving a problem whereby every time we copy a dll to the bin directory, our main domain on the website grinds to a halt and the only way to bring it back up is by restarting the "WWW Publishing Service". We run a website which contains a number of IIS applications running off a single server where each of these applications are configured to run off different application pools. We have a large codebase which contains over 280 aspx pages across the site. Our main domain contains about 100 aspx pages whilst the subdomains contain 15 or 20 each. When we do a build we are currently

I have the following set up: Win2008 server Ionic.zip reference module A seperate drive for building the zip files .NET 4.0 The web app builds zip packages, on the fly, and allows the client to download the package. This system has worked wonderfully... until now. Recently we added some larger files (2GB to 11GB) that all need to be wrapped up in a package before downloading to the client. Originally I had this system set up to happen all on the C: (a mistake). Right away, especially with the larger sized files, I started getting "There is not enough space on the disk" errors. The first thing

I have hosted my Webapp on server 1 and my database on server 2 But i m getting following error "Communication with the underlying transaction manager has failed." I googled and found a post which mentioned that it is the issue of DTC(Distributed Transaction) I enabled DTC on server2(DB server) and made an exception of it in Firewall. But still same error. Here is the full stack trace Message: System.Transactions.TransactionManagerCommunicationException: Communication with the underlying transaction manager has failed. ---> System.Runtime.InteropServices.COMException: The MSDTC transaction