On a .Net production server, I am unable to look at the Application trace. The web server returns a 404 error. When copying the files on my local computer, the trace works, making further testing impractical.
在.Net生产服务器上,我无法查看应用程序跟踪。 Web服务器返回404错误。在本地计算机上复制文件时,跟踪有效,进一步测试不切实际。
The trace seems to be correctly set:
跟踪似乎正确设置:
<trace enabled="true" requestLimit="20" pageOutput="true"
traceMode="SortByTime" localOnly="false" />
edit:
crap, I was trying to reply to it directly since I lost 2 hours on that and that some googling showed I was not the only one who stumbled there. Apparently I can't accept my own answer :)
废话,我试图直接回复它,因为我失去了2个小时,并且一些谷歌搜索显示我不是唯一一个偶然发现的人。显然我不能接受我自己的答案:)
1 个解决方案
#1
1
First of all, check whether the trace works whith a minimal trace directive:
首先,检查跟踪是否适用于最小跟踪指令:
<trace enabled="true" />
should work in any case.
应该在任何情况下都有效。
Then check the IIS configuration: an URL rewriting rule might be interfering with the trace.axd url.
然后检查IIS配置:URL重写规则可能会干扰trace.axd url。
If this is not the case, check whether the server accepts the .axd extension (Manage IIS>Properties>Home Directory>Configuration: The .axd extension should be present, executed by aspnet_isapi.dll, and not verifying that the file exists)
如果不是这种情况,请检查服务器是否接受.axd扩展名(管理IIS>属性>主目录>配置:应存在.axd扩展名,由aspnet_isapi.dll执行,而不验证该文件是否存在)
#1
1
First of all, check whether the trace works whith a minimal trace directive:
首先,检查跟踪是否适用于最小跟踪指令:
<trace enabled="true" />
should work in any case.
应该在任何情况下都有效。
Then check the IIS configuration: an URL rewriting rule might be interfering with the trace.axd url.
然后检查IIS配置:URL重写规则可能会干扰trace.axd url。
If this is not the case, check whether the server accepts the .axd extension (Manage IIS>Properties>Home Directory>Configuration: The .axd extension should be present, executed by aspnet_isapi.dll, and not verifying that the file exists)
如果不是这种情况,请检查服务器是否接受.axd扩展名(管理IIS>属性>主目录>配置:应存在.axd扩展名,由aspnet_isapi.dll执行,而不验证该文件是否存在)