Skip to content

Commit 5e98c53

Browse files
committed
[Troubleashoot] New troubleshoot article
1 parent 7bd755a commit 5e98c53

File tree

1 file changed

+85
-0
lines changed

1 file changed

+85
-0
lines changed
Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
---
2+
title: Get Full Memory Dump to troubleshoot SQL Server Management Studio (SSMS)
3+
Description: Troubleshooting a SSMS hang or crash by collecting a full memory dump
4+
ms.prod: sql
5+
ms.prod_service: "sql-tools"
6+
ms.technology: ssms
7+
ms.topic: how-to
8+
ms.assetid: c28ffa44-7b8b-4efa-b755-c7a3b1c11ce4
9+
author: markingmyname
10+
ms.author: maghan
11+
manager: craigg
12+
ms.reviewer: dineth, sstein
13+
ms.custom: ""
14+
ms.date: 05/17/2019
15+
---
16+
17+
# Get Full Memory Dump
18+
19+
[!INCLUDE](../../includes/appliesto-ss-asdb-asdw-xxx-md.md)
20+
21+
In this article you learn how to capture diagnostic information to troubleshoot a crash or a hang that you experienced from SQL Server Management Studio (SSMS).
22+
23+
1. Download [ProcDump](https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx)
24+
25+
2. Unzip the download into a folder
26+
27+
3. Open Command Prompt and run the following command:
28+
29+
```cmd
30+
<PathToProcDumpFolder>\procdump.exe -e -h -ma -w ssms.exe
31+
```
32+
33+
It should prompt you to accept a license agreement, select **Agree**.
34+
35+
4. Start SQL Server Management Studio (SSMS) if not started already
36+
37+
5. Reproduce the issue
38+
39+
6. Text should appear in the cmd prompt about writing the dump file, wait for that to finish
40+
41+
7. Create a new folder and copy the *.dmp file that is written out to that folder
42+
43+
8. Copy the following files into the same folder:
44+
45+
<li> "C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscordacwks.dll"
46+
47+
<li> "C:\Windows\Microsoft.NET\Framework\v4.0.30319\SOS.dll"
48+
49+
<li> "C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll"
50+
51+
9. Zip up the folder
52+
53+
## Get Full Memory Dump of SSMS when it throws an OutOfMemoryException (can be any managed exception)
54+
55+
To capture diagnostic information to troubleshoot an OutOfMemoryException from SSMS, please follow the steps as below:
56+
57+
1. Download [ProcDump](https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx)
58+
59+
2. Unzip the download into a folder
60+
61+
3. Open Command Prompt and run the following command:
62+
63+
```cmd
64+
<PathToProcDumpFolder>\procdump.exe -e 1 -f System.OutOfMemoryException -ma -w ssms.exe
65+
```
66+
67+
It should prompt you to accept a license agreement, select **Agree**.
68+
69+
4. Start SQL Server Management Studio if not started already
70+
71+
5. Repro the issue
72+
73+
6. Text should appear in the cmd prompt about writing the dump file, wait for that to finish
74+
75+
7. Create a new folder and copy the *.dmp file that is written out to that folder
76+
77+
8. Copy the following files into the same folder:
78+
79+
<li>"C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscordacwks.dll"
80+
81+
<li>"C:\Windows\Microsoft.NET\Framework\v4.0.30319\SOS.dll"
82+
83+
<li>"C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll"
84+
85+
9. Zip up the folder

0 commit comments

Comments
 (0)