Under Windows 2003, use the adjustment test ASP program common errors and processing methods

Because of work, I often need to use Asp to develop some small programs. When developing and using related programs under Windows 2000, there is generally no problem, and it is easy to solve. However, because the author used Windows 2003 Server in an early adopter, the development of related programs has such problems. For example, the browser cannot display detailed error information, and always gives an error when connecting to Access, which makes the author miserable. After many practices and reviewing some of the reference materials, I have some experience in dealing with related issues. Now I can finally debug and use the related programs under Windows 2003 Server, so I will share them with you here. A lot of criticism and correction.

One of the errors: You can't display debugging information on the browser side, only HTTP 500 errors.

Unexpectedly, as long as you have developed the Asp program, this error will definitely occur. It doesn't matter if such an error occurs, after all, it can be solved according to the error reason displayed on the browser. However, under Windows 2003 Server + IIS 6.0, only "internal server error" is reported. There is no specific information, which makes people depressed. In general, you can use IIS to start debugging ASP programs (the option to mark the red) by the following configuration. See Figure 1 and Figure 2 for details. To appear this configuration item, right click on the website you posted in IIS (usually the default website), select Properties, in the pop-up options, click the home directory, click the configuration button to appear as shown in Figure 1 and Figure 2. Option.

Figure 1 Enabling the parent path

Figure 2 Enabling the ASP program debugging

But it is very strange that after making these changes, the browser still does not display the error message properly. I always thought that this was a problem with the IIS server. Finally, through multiple sources of information, I finally found out that it was an Internet Explorer problem. It can be displayed normally by making the following configuration (modified by the option of red, the default hook and the picture below show the opposite). Click on the Internet Explorer - Tools - Internet option to display the following options page:

Figure 3 Internet Options Configuration

After the above changes, the error message can be displayed normally. It is also convenient when debugging errors. I think when I was debugging, I don’t know why I can’t display the error message, I can only go to the log. . . . . . That pain!