Use Active Log to quickly resolve IIS server failures

IIS (Internet Information Server) is a Web service component provided by Windows. I have been using Windows 2000 Server to build a Web server to support Asp web pages. In order to "advance with the times," I recently started using the popular Windows 2003 Server.

After configuring IIS, all Htm static pages and most Asp pages are not affected, but some Asp pages have an "HTTP500 internal error" problem that cannot be browsed normally (Figure 1). Is Windows Server 2003 IIS not as good as Windows 2000? I am determined to check out the water.

Figure 1

When the system prompts "HTTP500 internal error" problem, it often makes the network management a mess, fortunately I have no problem with these Asp pages themselves, because they are in Windows 2000 The next can be displayed normally, so the reason for the error is attributed to the problem of IIS. First of all, I tried to search on Baidu website with "HTTP500 internal error" as the keyword. The information I found was quite a lot, but it was not suitable for the problems I encountered. But from this information, I noticed that there is an important message of "activity log" in IIS. The information recorded in the log should be detailed. With this in mind, I started the following experiment again: Open "Internet Information Services (IIS) Manager" by going to "Start → Settings → Control Panel → Administrative Tools → Internet Information Services (IIS) Manager". Then expand my "axzx" site on the site, right click on it, select "Properties" and go to the site properties page (Figure 2).

Figure 2

From the figure, you can see that IIS6 uses the "W3C Extended Log", and then click the "Properties" button on the right, from which we can get the path where the log is stored. According to the given path, find this log file (exyymmdd.log), open it with Notepad, and find such a message at the end of the file (Figure 3), and then use the "not allowed _Path_ character" Search for keywords, and found the corresponding solution:


Figure 3

In Figure 2, switch to the "Home Directory" tab, in the pop-up dialog box Click the "Configure" button to switch to the "Options" tab. Originally 2003 for security reasons, the "Enable Parent Path" feature is turned off by default, causing some Asp pages to not open. Of course, these pages that cannot be opened have such a common feature that there are "../" characters used to call the parent directory, so an error occurs. Put the check box to the left of "Enable Parent Path" to the checkmark (Figure 4). After confirming, browse the Asp file again. The long-lost page appears again, and the problem is solved successfully.


Figure 4

In short, there are many reasons for the "HTTP500 internal error" problem, but it is very general in the browser, so it is necessary to analyze the specific problem. The "activity log" is a pair of "eyes" that IIS provides us with to analyze the problem. With this pair of "eyes", we can find the cause of the problem. Of course, IIS's "activity log" has other uses. The author is just here to attract attention, and I hope that everyone will pay attention to it.