- Static HTML (.htm or .html files)
- Active Server Pages (ASP) pages (.asp files)
To test IIS's ability to serve HTML (static) content.
Create a file called Hello.htm in the content folder for IIS (by default, this is C:\Inetpub\Wwwroot) that contains the sample code listed below.
http://localhost/hello.htm from the Web browser that is installed on the IIS server.
<TITLE>HTML Test Page</TITLE>
If you see "Hello World" below, then HTML pages are serving properly.
To test IIS's ability to serve ASP (dynamic) content.
Create a file called Hello.asp in the content folder for IIS (by default, C:\Inetpub\Wwwroot), that contains the following sample code,
http://localhost/hello.asp from the Web browser that is installed on the IIS server.
<TITLE>ASP Test Page</TITLE>
If you see "Hello World" below, then ASP pages in this Web application are serving properly.
The Hello.htm and Hello.asp samples can also be downloaded.
The following file is available for download from the Microsoft Download Center:
Release Date: May-17-2001
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
The Hello.exe file contains the following files:
Hello.asp Displays ProperlyIf the phrase "Hello World" is displayed properly on the ASP test page, but another ASP page does not serve properly, the following reasons may apply:
- The failing ASP page is running in a separate process from the Web application that is running the Hello.asp test page. Each process (Inetinfo.exe, Mtx.exe, or Dllhost.exe) that is capable of serving ASP pages (or any other Internet Server API application) has its own thread pool, which is separate from the thread pool in other processes. If one process is experiencing blocking (also known as ASP queuing, which occurs when all available threads are in use but additional requests continue to come in), a separate process may continue serving ASP pages properly because it has its own thread pool from which to execute requests.
- The failing page is not executing static HTML or ASP content. If the failing page is a Common Gateway Interface (CGI) application, see the following Microsoft Knowledge Base article for additional information on troubleshooting CGI applications: If the failing page is executed by an ISAPI application developed by a third-party company, contact that third party for technical support.
Hello.asp Does Not Display Properly
- If the phrase "Hello World" is not displayed on the ASP page, it is possible that the ASP threads are queued, blocked, or deadlocked, which requires additional problem-solving that is beyond the scope of this article.
- The failing ASP page contains a problem that is preventing IIS from properly serving ASP content (see the thread pool/ASP queuing information earlier in this article). If custom COM objects are in use on any of the pages that are failing, you can try contacting the vendor of those COM objects or the developer of that page for technical support. To determine if COM objects are in use, search for occurrences of "Set" (Microsoft Visual Basic Script) or "var" (Microsoft JScript). If either of those keywords exist, the COM object called is in the parentheses following CreateObject (VBScript or JScript) or ActiveXObject (JScript).
Hello.htm Does Not Display ProperlyIf Hello.htm does not display properly, one of the following reasons may apply:
- IIS is not listening on the IP address and port requested by the client.
- Networking issues are preventing the client from reaching the server (consider testing with a Web browser on the IIS server).
Problem Isolation with Web-Based Applications
Tuning Internet Information Server Performance
Artikelnummer: 279729 – Letzte Überarbeitung: 17.03.2009 – Revision: 1