| Event Id | 1032 |
| Source | Microsoft-Windows-IIS-W3SVC |
| Description | The World Wide Web Publishing Service (WWW Service) did not configure logging properties for site %1. The site's log file directory path may be a mapped network path. Using a mapped network path as the site's log file directory is not supported by IIS. Use a UNC path instead. |
| Event Information | According to Microsoft : Cause : This event is logged when the World Wide Web Publishing Service (WWW Service) did not configure logging properties for site. Resolution : Set a valid log directory path To resolve this, edit the logging path for the Web Site so that it has the following characteristics: 1.The computer name or share name in the file path must be valid. 2. If a remote drive is needed, specify a UNC Path. Mapped drives must are not supported. 3.The computer account of the front-end Web server must have permissions on the specified path. 4.The directory path specified must exist and be fully qualified. To edit the path, use the following procedure. Note: To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To edit the log file path for a 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 Connections pane, select the Web site whose logging you have to configure. 4. In Features View , click Logging . The Logging window appears. 5. In the Logging window, make sure that the log directory that is specified meets the criteria specified in this procedure. 6. In the Actions pane, click Apply . Verify : To verify that a Web site is started, you can use either IIS Manager or the appcmd command line utility. To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority. To verify that the Web site is started by using the appcmd command line utility: 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.Change the directory to %SystemDrive%\Windows\System32\inetsrv. 3.Run the following command: appcmd.exe list site -site.name:"Site Name". If the Web site is started, the output will resemble the following: SITE "Default Web Site" (id:1,bindings:http/*:80:,state:Started) To verify that the Web site is started by using IIS Manager: 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 Connections pane, expand the computer name. 4.In the Connections pane, click the Sites node. 5.In Features View, look for the Web site name. The Web site status will be indicated under the Status column. If the Web site is started and is using the HTTP protocol, Started(http) will appear. |
| Reference Links | Event ID 1032 from Source Microsoft-Windows-IIS-W3SVC |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.