Date post: | 08-Apr-2018 |
Category: |
Documents |
Upload: | yasser-mohammed |
View: | 229 times |
Download: | 0 times |
of 17
8/7/2019 debugging steps
1/17
CRASH DUMPS:
1. In order to take Crash dumps from the server we use debug diagnostic tool whichcan be downloaded from here.
http://www.microsoft.com/downloads/en/details.aspx?
FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=en
2. Go to StartAll ProgramsDebug Diagnostic Tools 1.1Debug Diag 1.1 (x86)
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=enhttp://www.microsoft.com/downloads/en/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=enhttp://www.microsoft.com/downloads/en/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=enhttp://www.microsoft.com/downloads/en/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=en8/7/2019 debugging steps
2/17
3. Select All IIS/COM+ related processes and click next
8/7/2019 debugging steps
3/17
4. Select Add rule and click on Breakpoints
8/7/2019 debugging steps
4/17
8/7/2019 debugging steps
5/17
6. Click on Next
8/7/2019 debugging steps
6/17
7. Click on Activate the rule now and then select finish.
8/7/2019 debugging steps
7/17
8. Following is the last screen for Crash Dumps.
8/7/2019 debugging steps
8/17
HIGH CPU/MEMORY/HANG DUMPS:
1. Go to StartAll ProgramsDebug Diagnostic Tools 1.1Debug Diag 1.1 (x86)
8/7/2019 debugging steps
9/17
2. Go to task manager and identify the process which is utilizing high CPU. Theprocess id for a particular application pool (w3wp.exe) which is taking high CPU can
be identified by the command.
cscript iisapp.vbs
8/7/2019 debugging steps
10/17
8/7/2019 debugging steps
11/17
6. Go to Start All Programs Debugging Tool for Windows (x86) WinDbg
Click on FileSymbol File Path
7. In the resulting dialog box, enter the following.
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 folderC:\Program Files\Debugging Tools for Windows (x86)
9. Now download psscor2 which can be found herehttp://www.microsoft.com/downloads/en/details.aspx?FamilyID=5c068e9f-ebfe-48a5-
8b2f-0ad6ab454ad4&displaylang=en
Run the exe file and extract the psscor2.dll from the zip file to the folderC:\Program Files\Debugging Tools for Windows (x86)
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5c068e9f-ebfe-48a5-8b2f-0ad6ab454ad4&displaylang=enhttp://www.microsoft.com/downloads/en/details.aspx?FamilyID=5c068e9f-ebfe-48a5-8b2f-0ad6ab454ad4&displaylang=enhttp://www.microsoft.com/downloads/en/details.aspx?FamilyID=5c068e9f-ebfe-48a5-8b2f-0ad6ab454ad4&displaylang=enhttp://www.microsoft.com/downloads/en/details.aspx?FamilyID=5c068e9f-ebfe-48a5-8b2f-0ad6ab454ad4&displaylang=en8/7/2019 debugging steps
12/17
8. Go to File Open Crash Dump
8/7/2019 debugging steps
13/17
9. Select the dump file which can be found in the location C:\ProgramFiles\DebugDiag\Logs\Misc
8/7/2019 debugging steps
14/17
10. The following screen comes up once we select the dump file
8/7/2019 debugging steps
15/17
8/7/2019 debugging steps
16/17
12. Then we need to load psscor2 which can be loaded by using the command
.load psscor2
8/7/2019 debugging steps
17/17
13. The aspx pages can be seen by using the command
!aspxpages
14. Other commands can be found in here
http://windbg.info/download/doc/pdf/WinDbg_cmds.pdf
http://windbg.info/download/doc/pdf/WinDbg_cmds.pdfhttp://windbg.info/download/doc/pdf/WinDbg_cmds.pdf