CHRISdotTODD

I found that IIS 7 on Windows 2008 Server to be much different from prior versions of IIS. The first hurdle was to realize that Classic ASP isn't installed by default. In searching board posts to solve my issue, I found countless posts with directions to install Classic ASP. So getting this far, I was unable to process my HTML files that had embedded Classic ASP code, In prior versions of IIS, you could just add *.html to the previous defined *.asp listing. With IIS 7 though, this created problems with the .asp pages, and did not solve the issue either. The trick is to make a new entry in the HandlerMappings specifically for *.html. Request path: *.html Executable: %windir%\system32\inetsrv\asp.dll Name: anything meaningful to you Mapping: File Verbs: GET,HEAD,POST Access: Script Once you've completed this... Go to %windir%\system32\inetsrv\config\applicationHost.config file Find the new entry (search on the name you set in the HandlerMapping) Remove the preCondition port...

With increasingly more complex web pages, I found myself running into a limit in the number of IIS connections allowed for the constrained web server on Windows XP. By default Microsoft has limited the connections to 10. Even when I changed the time to release connections down to 5 minutes, I was still running into problems. With a little Google searching, I found a solution ( here , here , and here ). Apparently the hard-coded limitation Microsoft has set is 40 connections. The trick is determining how to raise the level from 10 to 40. There's a script, adsutil, that can do this for you. Go to the Command Prompt and navigate to C:\Inetpub\AdminScripts. Enter "adsutil set w3svc/MaxConnections 40". If you get an error message, "This script does not work with WScript," click OK and click Yes to make Cscript as the default script for VBscript. When this completes, go back to the Command Prompt and press F3 (repeats last command) and Enter. If you were successful, t...

When developing locally on IIS, with the addition of AJAX, I found myself running out of connections -- the default is 10. Turns out you can bump the connections up to 40. Here's what you need to do: Open the command prompt Navigate to \inetpub\adminscripts Enter the following command: cscript adsutil.vbs set w3svc/MaxConnections 40 Restart IIS ( you can use iisreset at the same command prompt) That's all there is to it.

Occasionally I find where IIS is hung, and I hate to have to reboot. Fortunately I found a web page that lists the command and switches you can use from the command line to accomplish the task. This is the same site, psacake.com that notified us of companies that would be closing after Christmas, so avoid getting gift cards from them.

This is a little 'techy' for my typical blog posts, but I had a heck of a time finding an answer online. I recently got a new laptop and needed to reconfigure my ASP development environment. I kept running into one problem, where my home page displayed ASP code at the top ( ...), instead of executing. Turns out you need to add to the basic ASP configuration to execute ASP code that is in HTML pages. Of course that seems like a no-brainer, but I don't recall having done that in the past. Here's the steps to do this: Go to Administrative Tools in the Control Panel Launch Internet Information Services (IIS) Go to your (default) website and open Properties Go to the Home Directory tab Click the Configuration.. button under the Application Settings section On the Mappings tab, click Add Enter the following information: Executable: c:\windows\system32\inetsrv\asp.dll Extension: .html Verbs | Limit to : GET,HEAD,POST,TRACE Check the boxes: Script Engine and Check tha...