Share via

Event ID 1134 — IIS W3SVC Logging

  • Article

Applies To: Windows Server 2008 R2

An Internet Information Services (IIS) Web server can be configured for Site, Central Binary, or Central W3C logging. In Central W3C logging, all client requests for all sites are logged to a single log file in W3C centralized format on the server. Central Binary logging also logs all sites centrally to a single file, but does so in centralized binary format. In Site logging, all client requests are logged at the site level, not centrally at the server level. These logging types depend on the World Wide Web Publishing Service for their configuration.

Event Details

Product: Internet Information Services
ID: 1134
Source: Microsoft-Windows-IIS-W3SVC
Version: 7.5
Symbolic Name: W3SVC_WS03_EVENT_CENTRALIZED_W3C_LOGGING_NOT_CONFIGURED
Message: The World Wide Web Publishing Service (WWW Service) failed to configure centralized W3C logging properly. The data field contains the error number.

Resolve

Stop and restart the W3SVC

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To stop and restart the World Wide Web Publishing service:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. At the command prompt, type net stop w3svc.
  3. At the command prompt, type net start w3svc.

Verify

To verify that logging is working, follow these steps:

  • Note the Site ID and test browse the site.
  • Check the log file directory.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Note the Site ID and Test Browse the site

To note the Site ID and Test Browse the site:

  1. Click Start, click Control Panel, and then click Administrative Tools.
  2. Right-click Internet Information Services (IIS) Manager and select Run as administrator.
  3. In the IIS Manager Connections pane, expand the computer name.
  4. Click Sites. A list of the server's Web sites appears in Features View on the right.
  5. Under the ID column in Features View, note the ID of the Web site for which you want to verify the logging.
  6. In Features View, single-click the Web site that you want to verify.
  7. In the Actions pane, click the link under Browse Web Site. The Web page for the site should appear.

Check the log file directory

To check the log file directory:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

  2. Navigate to the log file directory. If you are using the default location, type cd %SystemDrive%\inetpub\logs\LogFiles\W3SVCnumber, where number corresponds to the Web site ID that you noted earlier. For example, the site ID for the Default Web Site is typically 1, so the directory name that you type would be W3SVC1.

  3. Type dir /od to list the log files. The most recent log file appears last in the list. W3C log files will have the format u_exyymmdd, where yymmdd represents the year, month, and date in six-digit format. The last log file in the list should have today's date and a recent time stamp.

  4. Type notepad logfilename to open the last (most recent) log file. Your test browse should have resulted in the log file being created and/or your test browse being logged in the file.

    Note:  There might be a short delay between the time of the test browse and the time that the test browse is logged.

IIS W3SVC Logging

Internet Information Services (IIS) 7.5