-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Troubleashoot] New troubleshoot article
- Loading branch information
1 parent
7bd755a
commit 5e98c53
Showing
1 changed file
with
85 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,85 @@ | ||
--- | ||
title: Get Full Memory Dump to troubleshoot SQL Server Management Studio (SSMS) | ||
Description: Troubleshooting a SSMS hang or crash by collecting a full memory dump | ||
ms.prod: sql | ||
ms.prod_service: "sql-tools" | ||
ms.technology: ssms | ||
ms.topic: how-to | ||
ms.assetid: c28ffa44-7b8b-4efa-b755-c7a3b1c11ce4 | ||
author: markingmyname | ||
ms.author: maghan | ||
manager: craigg | ||
ms.reviewer: dineth, sstein | ||
ms.custom: "" | ||
ms.date: 05/17/2019 | ||
--- | ||
|
||
# Get Full Memory Dump | ||
|
||
[!INCLUDE](../../includes/appliesto-ss-asdb-asdw-xxx-md.md) | ||
|
||
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). | ||
|
||
1. Download [ProcDump](https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx) | ||
|
||
2. Unzip the download into a folder | ||
|
||
3. Open Command Prompt and run the following command: | ||
|
||
```cmd | ||
<PathToProcDumpFolder>\procdump.exe -e -h -ma -w ssms.exe | ||
``` | ||
It should prompt you to accept a license agreement, select **Agree**. | ||
4. Start SQL Server Management Studio (SSMS) if not started already | ||
5. Reproduce the issue | ||
6. Text should appear in the cmd prompt about writing the dump file, wait for that to finish | ||
7. Create a new folder and copy the *.dmp file that is written out to that folder | ||
8. Copy the following files into the same folder: | ||
<li> "C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscordacwks.dll" | ||
<li> "C:\Windows\Microsoft.NET\Framework\v4.0.30319\SOS.dll" | ||
<li> "C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll" | ||
9. Zip up the folder | ||
## Get Full Memory Dump of SSMS when it throws an OutOfMemoryException (can be any managed exception) | ||
To capture diagnostic information to troubleshoot an OutOfMemoryException from SSMS, please follow the steps as below: | ||
1. Download [ProcDump](https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx) | ||
2. Unzip the download into a folder | ||
3. Open Command Prompt and run the following command: | ||
```cmd | ||
<PathToProcDumpFolder>\procdump.exe -e 1 -f System.OutOfMemoryException -ma -w ssms.exe | ||
``` | ||
It should prompt you to accept a license agreement, select **Agree**. | ||
4. Start SQL Server Management Studio if not started already | ||
5. Repro the issue | ||
6. Text should appear in the cmd prompt about writing the dump file, wait for that to finish | ||
7. Create a new folder and copy the *.dmp file that is written out to that folder | ||
8. Copy the following files into the same folder: | ||
<li>"C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscordacwks.dll" | ||
<li>"C:\Windows\Microsoft.NET\Framework\v4.0.30319\SOS.dll" | ||
<li>"C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll" | ||
9. Zip up the folder |