freb

Getting Trace messages into Failed Request Tracing from Controllers

雨燕双飞 提交于 2019-12-12 18:18:46
问题 On ASP.NET MVC Preview 5, we're having trouble getting any trace messages from Global or Controllers to appear in either a page (View) or Failed Request Tracing (FREB). Neither of these calls work in a Controller Action: HttpContext.Trace.Write("hello"); System.Diagnostics.Trace.WriteLine("world"); There are no issues with trace statements in a Page's code-behind; those messages appear correctly. 回答1: Those calls happen before the Page (ViewPage) is even created so you need to enable tracing

IIS 500 Error WCF Service and Failed Request Tracing not info

久未见 提交于 2019-12-08 03:30:56
问题 I have a WCF service running in IIS 8.5 on Windows Server 2012 R2 with AppPool Integrated. I open url in the server: http://localhost:50123/MyService.svc I have HTTP 500 Internal Server Error . (IExplorer cannot show the page) I have not found the problem in Event logs, IIS Logs. I apply this steps: https://peter.hahndorf.eu/blog/iislogging.html Disable IE “Friendly HTTP error messages” <customErrors mode=”Off” /> <httpErrors errorMode="Detailed" /> <serviceMetadata httpGetEnabled="true"/>

Why is the AspNetSessionData stage of page processing delaying my page by 20+ seconds?

断了今生、忘了曾经 提交于 2019-12-05 02:07:22
问题 I have a web application that uses ASP.NET with "InProc" session handling. Normally, everything works fine, but a few hundred requests each day take significantly longer to run than normal. In the IIS logs, I can see that these pages (which usually require 2-5 seconds to run) are running for 20+ seconds. I enabled Failed Request Tracing in Verbose mode, and found that the delay is happening in the AspNetSessionData section. In the example shown below, there was a 39-second gap between