Knowledge Base
Setup Logging in IIS 5.0PSS ID Number: 249025
Article Last Modified on 3/9/2000
--------------------------
The information in this article applies to:
Microsoft Internet Information Services 5.0
--------------------------
This article was previously published under Q249025
SUMMARY
Microsoft Internet Information Services (IIS) 5.0, included with Windows 2000, generates a Setup log file that can be used for Setup troubleshooting. This log file can be used to debug installation difficulties that are discovered after you attempt to install IIS. The "More Information" section of this article explains how IIS Setup works, and how to read the log file entries.
MORE INFORMATION
How IIS Setup Works
IIS Setup is an optional component in the Windows 2000 Setup program; it gets called by the Windows 2000 Setup program, along with all other the optional components. The optional components are all listed in the Sysoc.inf file located in the %Windir%\Inf directory. The Windows 2000 Optional Component Manager (Ocmanage.dll) loads the Sysoc.inf file during Setup and calls the Setup DLLs described in the Sysoc.inf file. These components get different calls during various stages of Setup.
The names of the DLLs are descriptive of the actions performed. For example, OC_INIT_COMPONENT requests the DLL to do its initialization routines. OC_QUEUE_FILE_OPS is called when the DLL fills its file queue with the list of files to install. OC_ABOUT_TO_COMMIT_QUEUE is called right before the files actually get copied to disk, and OC_COMPLETE_INSTALLATION is where the components' configuration settings are completed.
The Iis5.log File
The Iis5.log file contains a log of the activities that occur during Setup. Any failures that occur during Setup are reported in the Iis5.log file. The log file's operations are controlled by the Setup INF file, located in the %Windir%\Inf directory. (Iis.inf is specified in %Windir%\Inf\Sysoc.inf). The entry in the Sysoc.inf file that corresponds with IIS Setup looks similar to the following:
iis=iis.dll,OcEntry,iis.in
This entry shows that the IIS setup DLL file is Iis.dll, the entry point to the DLL is OcEntry, and the configuration file that Iis.dll uses to configure IIS is Iis.inf.
An entry in the Iis.inf file can be used to specify the level of detail in the Iis5.log file. The parameter is named DebugLevel, and is listed in the [SetupInfo] section. The DebugLevel parameter can have the following numerical values:
0 – Show only errors
1 – Log warnings
2 – Trace level 1 (The least verbose option of the trace options.)
3 – Trace level 2
4 – Trace level 3
The following code is an example of logging in the Iis5.log file. This example shows that Setup is registering the Asp.dll file:
[10/20/1999 16:40:53] OC_COMPLETE_INSTALLATION:i
[10/20/1999 16:40:53] OC_COMPLETE_INSTALLATION:i
[10/20/1999 16:40:53] OC_COMPLETE_INSTALLATION:i
[10/20/1999 16:40:53] OC_COMPLETE_INSTALLATION:i
[10/20/1999 16:40:54] OC_COMPLETE_INSTALLATION:i
[10/20/1999 16:40:54] OC_COMPLETE_INSTALLATION:i
[10/20/1999 16:40:54] OC_COMPLETE_INSTALLATION:i
[10/20/1999 16:40:54] OC_COMPLETE_INSTALLATION:i
The following code is an example of a failure to register the Asp.dll file:
[12/7/1999 14:24:0] OC_INIT_COMPONENT:!FAIL!
[12/7/1999 14:24:0] OC_INIT_COMPONENT:CallProc
REFERENCES
http://www.microsoft.com/t
http://www.microsoft.com/t
Additional query words: iis 5
Keywords: kbinfo KB249025
Technology: kbiis500 kbiisSearch
--------------------------
Send feedback to Microsoft
© 2003 Microsoft Corporation. All rights reserved.
Main Topics
Browse All Topics
by: PeteLongPosted on 2003-07-30 at 08:17:09ID: 9037051
Knowledge Base
HOW TO: Troubleshoot ASP in IIS 5.0PSS ID Number: 309051
Article Last Modified on 10/26/2002
--------------------------
The information in this article applies to:
Microsoft Internet Information Services 5.0, when used with:
the operating system: Microsoft Windows 2000
--------------------------
This article was previously published under Q309051
IN THIS TASK
SUMMARY
How to Troubleshoot ASP in IIS 5.0
SUMMARY
This step-by-step article describes the troubleshooting steps to take if ASP (Active Server Pages) stops responding on an Internet Information Services (IIS) 5.0 Web server. The platform may be any version of Windows 2000.
back to the top
How to Troubleshoot ASP in IIS 5.0
NOTE: Before you begin, ensure that .html or .htm files open on the Web server in question. If these files do not open, this is not an ASP issue.
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:
288245 PRB: Global.asa Does Not Fire from Personal Web Server on Windows 98
265275 FP2000: Global.asa Does Not Run in FrontPage Web
173742 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:
301919 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>cs
308622 HOW TO: Perform Administration Tasks in IIS from a Command Prompt
297989 PRB: Configured Identity Is Incorrect for IWAM Account
255770 PRB: Logon Failure: Unknown User Name or Bad Password When You Run Out-of-Process Webs
236007 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.co
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:
271071 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.
In the system event log, look for the following events:
Source: DCOM Event ID: 10010 User: NT AUTHORITY\SYSTEM Description: The server {3D14228D-FBE1-11D0-995D-0
This error message is followed in the event log by a warning message like the following:
Source: W3SVC Event ID: 36 User: N/A Description: The server failed to load application 'AppPath'. The error was 'Server execution failed'.
You may also see entries like the following in your %SystemRoot%\Iis5.log file:
OC_ABOUT_TO_COMMIT_QUEUE:U
If you receive these error messages, the NT AUTHORITY\Authenticated Users or NT AUTHORITY\INTERACTIVE entry has been removed from the Users group. To resolve the problem, make sure that Authenticated Users and INTERACTIVE are members of the Users Group for that computer.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
327153 PRB: ASP Pages Do Not Process and DCOM Event 10010 Appears in System Log
As a last resort, you can re-create the IIS packages. To do this, follow these steps:
Browse to Component Services and delete the following packages:NOTE: To delete the packages, you must first open the properties of the package, click the Advanced tab, and then click to clear the Disable Deletion check box.
IIS In-Process Applications
IIS Out-of-Process Pooled Applications
IIS Utilities
Open a command prompt, and then use the following command to switch directories:
cd %windir%\system32\inetsrv
Run the following commands:
rundll32 wamreg.dll, CreateIISPackage
NOTE: "CreateIISPackage" must be typed exactly; it is case-sensitive.
regsvr32 asptxn.dll
Close and reopen Component Services. You should see all three IIS COM+ applications that have been recreated.
Run IISRESET from a command line and test any ASP page that previously did not load correctly.
back to the top
Additional query words: iwam ID 36 10010 500 59 C000003b
Keywords: kbhowto kbHOWTOmaster KB309051
Technology: kbiis500 kbiisSearch kbOSWin2000 kbOSWinSearch
--------------------------
Send feedback to Microsoft
© 2003 Microsoft Corporation. All rights reserved.