IIS 7 500错误处理情况
我在 IIS 7 上使用 Server.GetLastError() 的经典 ASP 应用程序，并添加了此脚本，该脚本将错误详细信息作为 IIS 中的自定义“500.100”错误写入数据库以执行此 URL。到目前为止，当应用程序出现错误时，它可以在大多数情况下正常工作。但是，我在 IIS 日志中注意到许多人都收到 ASP_0147 |内部服务器错误，带有 500 错误，没有进一步的解释。
我正在尝试使用上述方法捕获 IIS 日志中显示的此错误，但是，使用我制作的应用程序不会捕获这些错误（写入数据库），而其他类型的错误也会被捕获，但唯一的错误是使用我制作的脚本/数据库捕获的错误已经在 IIS 日志中显示出完整的错误详细信息。
所以问题是，如何使用自定义错误捕获数据库中 IIS 日志中仍然发生的错误？因为我使用的方法显然不能捕获 IIS 日志中显示的所有错误，只能捕获日志中显示的带有解释的错误。或者，如果我将错误“功能设置”更改为“详细错误”（因为现在已设置为“仅针对本地请求详细”），它会显示在 IIS 日志等中吗？为什么我在 IIS 日志中仅在某些内容上看到 500 错误，而在其他内容上却看不到？谢谢。
I am on IIS 7 with a Classic ASP application using Server.GetLastError() and i added this script that writes the error details to a database as a custom '500.100' error in IIS to execute this URL. So far it's been working on most situations when there is an error in the application. However, I am noticing in the IIS log that many people are getting ASP_0147 | Internal Server Error with a 500 error and no further explanation.
I am trying to catch this error showing up in the IIS Log using the method explained above, however, these errors are not being caught (written to database) using the application i made, whereas other types of errors are being caught, but the only errors that are being caught using the script/database i made, already show up with the entire error details in the IIS log.
So the question is, how can i catch the errors still happening in the IIS Log in the database using custom errors? because the method i'm using obviously isn't catching all the errors that show in the IIS Log, only the ones with an explanation being displayed in the log. Or, if I change the Error 'Feature Settings' to 'Detailed Errors' (because now its set on, Detailed only for Local Requests) will it show up in the IIS log, etc? Why am i only seeing 500 error in the IIS Log on certain things, but not on others? Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这可能是应用程序停顿。
如果服务器同时收到大量请求，导致服务器“忙碌”，它会停止某些请求并可能拒绝它们。这可能会产生误报 500 错误，错误描述为
(0x0)。This could be an application stall.
If the server gets a lot of requests on the same time, causing the server to "get busy", it stalls some of the requests and possibly denying them. This could give a false-positive 500 error with the error-description
(0x0).