Article 463

If a Global.asa file exists in the root of your Web site, rename it as Global.old, stop and restart the Web services, and then create a test ASP page in Notepad with the following code:
```
<%
   Response.Write "This is a test ASP page."
%>
```
Save this file as Test.asp in the root of your Web site, and try to open the file on the Web server.

If ASP pages load in your Web browser after you have performed this step, the problem is with the Global.asa file. If ASP pages still do not load, proceed to step 2.

For additional information on troubleshooting the Global.asa file, click the article numbers below to view the articles in the Microsoft Knowledge Base:

Q288245 PRB: Global.asa Does Not Fire from Personal Web Server on Windows 98

Q265275 FP2000: Global.asa Does Not Run in FrontPage Web

Q173742 FIX: Global.asa Is Not Executed If Restricting Web Access
Set the application protection for the Web site to Low and stop and restart the IISAdmin service. If ASP pages load in your Web browser after you have performed this step, the issue is with the IWAM account, and you can proceed to step 3. If ASP pages still do not load, check Component Services in Administrative Tools to ensure that you can view the IIS packages. This ensures that Component Services is not failing. Make sure the following users exist in the local Users group:
- NT AUTHORITY\Authenticated Users
- NT AUTHORITY\INTERACTIVE
For more information on troubleshooting the Component Services snap-in, see the following Knowledge Base article:

Q301919 PRB: Cannot Expand 'My Computer' in Component Services MMC Snap-In
If ASP pages load in your Web browser after you have performed step 2, set the site back to Medium or High application protection, and add the IWAM account to the local Administrators group. If ASP pages load in your Web browser after you have performed this step, a permissions issue involving the IWAM account exists, and you can proceed to step 4. If ASP pages still do not load, run the Synciwam.vbs utility from a command line.

To do this, open a command prompt and type C:\Inetpub\adminscripts>cscript synciwam.vbs.
For additional information on situations in which the IWAM user account causes ASP to fail, see the following Knowledge Base articles:

Q308622 HOW TO: Perform Administration Tasks in IIS from a Command Prompt
Q297989 PRB: Configured Identity Is Incorrect for IWAM Account
Q255770 PRB: Logon Failure: Unknown User Name or Bad Password When You Run Out-of-Process Webs
Q236007 Domain Controller Demotion Causes Out-of-Process Applications to Fail
To resolve permissions issues with the IWAM account, use the Regmon and Filemon third-party products for Windows 2000. To download these these utilities, see the following Web site:

http://www.sysinternals.com

Run these utilities while you make a request for an ASP page, then search for "ACCDENIED" in Regmon and "FAILURE" in Filemon for the Dllhost.exe process.

NOTE: Do not be alarmed if you see "access denied" for the Iexplore.exe (Microsoft Internet Explorer) process. This is common behavior.

For more information on the minimum permissions that are required for IIS to function properly, see the following Knowledge Base article:

Q271071 Minimum NTFS Permissions Required for IIS 5.0 to Work

After you have identified "access denied" error messages for the Dllhost.exe process, use Regedt32 to make any necessary modifications to NTFS permissions in the registry.
After you install Internet Information Services (IIS) 5.0, and you browse ASP or HTML pages from the console of the Web server or another workstation on the network, the Web service may return the following error message:

HTTP 500 - Server Application Error

The Default Web Site may be in a Running state. If you run the netstat -an command from a command prompt, you may notice that the Web server's IP address is listening on TCP port 80, which is the default HTTP port.

NOTE: When you are troubleshooting problems using the Advanced Internet Options in Internet Explorer 5.0, more descriptive error messages are usually returned by disabling the Show friendly HTTP error messages option. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
The following items may appear in the Event Viewer on the IIS 5.0 computer:
- Application Log: COM+ error with Event ID 4099
- System Log: W3SVC error with Event ID 59
- System Log: W3SVC warning with Event ID 36.
The Iis5.log file (located in the WINNT folder) may contain the following error message:

0x8004e00f=COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator

When you try to open the Component Services snap-in, which is used for COM+ administration, the Microsoft Management Console (MMC) may stop responding.
Cause
Internet Information Services 5.0 relies on COM+, which in turn relies on the Distributed Transaction Coordinator (DTC) service for functionality. The DTC version-checking feature, included in versions of SQL Server that were developed prior to Windows 2000, does not recognize the version properties used by Windows 2000. As a result, the SQL Server DTC Setup utility removes the DTC service installed by Windows 2000. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
Resolution
To resolve this problem, perform the following steps:
1. Verify that the version number of the Dtcsetup.exe application (located in the c:\Winnt\System32 directory by default) is 1999.9.3422.24 or later.
2. Run the Dtcsetup.exe application to install the DTC service.
3. Start the DTC service.
4. In Control Panel, double-click the Add/Remove Programs icon.
5. Select Add/Remove Windows Components, remove Internet Information Services (IIS) 5.0, and then reinstall it from the Windows 2000 CD.
Status
Microsoft has confirmed this to be a problem in SQL Server versions 6.5 and 7.0 and MSDE version 1.0.

See this article for more details:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q257267
As a last resort, you can recreate the IIS packages. To do this, follow these steps:
1. Browse to Component Services and delete the following packages:
  - IIS In-Process Applications
  - IIS Out-of-Process Pooled Applications
  - IIS Utilities
2. Open a command prompt and switch to the following folder:
```
%windir%\system32\inetsrv rundll32 wamreg.dll, CreateIISPackage
```
  NOTE: CreateIISPackage must be typed exactly; it is case-sensitive.
3. Close and reopen Component Services. You should see all three IIS COM+ applications that have been recreated.
4. Run IISRESET from a command line and test any ASP page that previously did not load correctly.

Cause

Resolution

Status