In order to perform its activities successfully, the Internet Information Services (IIS) World Wide Web Publishing Service (W3SVC) must be free of any I/O errors involving file access, memory availability, and network connections. In addition, any scripts that are used must be accessible and running, and any include files must be configured correctly.

Check file access

Possible resolutions include the following:

• If W3SVC was unable to read a file, verify that the file indicated in the error message exists and that W3SVC has permissions to the file.

• If the file was too big, reduce its size.

• The event log message may contain an error number that can provide more information about the issue. To do this, see the following steps.

Check for a specific error number:

To check for a specific error number:

• In the Event Viewer, select the event that you received.

• Click the Details tab, then Friendly View.

• If a specific error number is available, the words Binary data: should appear.

• Note the number after the colon under In Words.

Find out more about a specific error number

To learn more about a specific error number:

• Download the Err.exe utility from the Microsoft Exchange Server Error Code Look-up page.

• Click Start, All Programs, Accessories, and then Command Prompt.

• At the command prompt, navigate to the directory where you downloaded Err.exe. For example, if you downloaded Err.exe to C:\Err, type cd C:\Err.

• Type err errornumber to obtain more information about the error. For example, if the specific error number is 80070005, type err 80070005.

• In the example in Step 4, the error resolves to ERROR_ACCESS_DENIED, so your next step would be to check a permissions issue.