Академический Документы
Профессиональный Документы
Культура Документы
1. In order to take Crash dumps from the server we use debug diagnostic tool which
can be downloaded from here.
http://www.microsoft.com/downloads/en/details.aspx?
FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=en
cscript iisapp.vbs
3. Navigate to the Process tab and select the process id which is taking high CPU.
Right click on the particular process id and select create Full UserDump.
Download the Windows SDK tool which consists of the debugging tools for windows,
which includes windbg tool.
http://www.microsoft.com/downloads/en/details.aspx?
FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b&displaylang=en
6. Go to Start All Programs Debugging Tool for Windows (x86) WinDbg
SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
8. Copy the sos.dll (can be found in .Net framework folder present on the server,
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727) and place it in the folder
C:\Program Files\Debugging Tools for Windows (x86)
Run the exe file and extract the psscor2.dll from the zip file to the folder
C:\Program Files\Debugging Tools for Windows (x86)
8. Go to File Open Crash Dump
9. Select the dump file which can be found in the location C:\Program
Files\DebugDiag\Logs\Misc
10. The following screen comes up once we select the dump file
11. Next step would be to load sos.dll file, which can be loaded by using the
command
.load sos.dll
12. Then we need to load psscor2 which can be loaded by using the command
.load psscor2
13. The aspx pages can be seen by using the command
!aspxpages
http://windbg.info/download/doc/pdf/WinDbg_cmds.pdf