AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
.net framework v4.0.30319 download11/6/2022 ![]() ![]() Once you've reproduced the crash, gather the following items and include them in your bug report: Exercise the application to reproduce the crash.Add the following configuration to the yaml file to enable verbose logging and logging of every method JIT-compiled by the CLR:.File > Open > C:\ProgramData\Contrast\dotnet\contrast_security.yaml.Start > Notepad > Right click > Run as Administrator.Create a folder to store the dumps and then set ProcDump as the default debugger on occurrence of a crash by running the following commands from an administrator command prompt - for example:.Download the current version of ProcDump from the Microsoft documentation site to the Windows server with the agent.Set up the ProcDump utility to capture crash dumps automatically.Once you confirm that the observed bug is a process crash, you're ready to gather information to file a bug.Ĭomplete the following steps to gather information to send to Contrast Support. 0, time stamp: 0x59a63e48įaulting application start time: 0x01d337d711f21e68įaulting application path: c:\windows\system32\inetsrv\w3wp.exeįaulting module path: C:\Windows\Microsoft.NET\Framework64\v9\clr.dll 16384, time stamp: 0x5215df96įaulting module name: clr.dll, version. The "Application Error" entry has details similar to: Faulting application name: w3wp.exe, version. NET Runtime at IP XXXXXXXXX with exit code YYYYYYY The ".NET Runtime" error has details such as:ĭescription: The process was terminated due to an internal error in the.The Windows Event Log ( Event Viewer > Windows Logs > Application) has Error entries for the. The web application is unresponsive after installing the. Unhandled Managed Exception/Page Error/500 or Excessive Resource Usageĭetermine whether the worker process crashedĬheck your scenario against the following indicators to determine whether the worker process crashed.There are two primary types of issue for which Contrast needs to gather process dumps: Note: log_discovered_routes is needed only if troubleshooting route coverage related issues. You can change which information is logged by setting the logging level in your contrast_security.yaml file to TRACE as follows: agent: If so, paste the paths into the Windows Explorer location you may need to replace the drive letter C with D. Depending on the setup of the Windows profile and folder view settings, the folders may be hidden. NET Framework agent logs information to the logs folder within C:\ProgramData\Contrast\dotnet\, the Windows 2008/2012 /2016 ProgramData folder. The article details the steps needed to gather additional logs and process dumps as needed. Deeper logging and perhaps a dump of the worker process(es) will often be needed for successful troubleshooting of such issues. In certain are scenarios, bad instrumentation can cause a web server process to crash or a specific page to error out. NET Framework agent logs only INFO level messages by default, but when troubleshooting specific issues it is often necessary to change that level to obtain additional detail on what the agent is seeing and doing. ![]()
0 Comments
Read More
Leave a Reply. |