{"id":2083,"date":"2023-02-03T13:43:26","date_gmt":"2023-02-03T13:43:26","guid":{"rendered":"https:\/\/www.theSQLReport.com\/?p=2083"},"modified":"2023-02-03T13:43:26","modified_gmt":"2023-02-03T13:43:26","slug":"using-microsofts-troubleshootingscript-version-2-tssv2-toolset-to-collect-support-information","status":"publish","type":"post","link":"https:\/\/www.theSQLReport.com\/?p=2083","title":{"rendered":"Using Microsoft’s TroubleShootingScript Version 2 (TSSv2) Toolset to Collect Support Information"},"content":{"rendered":"

(If pictures are not being displayed below, try viewing this post in Microsoft Edge browser)<\/p>\n

When opening a support case with Microsoft for SQL Server, sometimes they ask for information about your Windows server that SQL Server is having issues.<\/p>\n

Sharing my notes on how to collect on how to use Microsoft’s TroubleShootingScript Version 2 (TSSv2) toolset to collect logs & other information need for a case with Microsoft.<\/p>\n

1.<\/h1>\n

Download the TSSv2 utility:<\/strong><\/u><\/u><\/p>\n

Go to\u00a0https:\/\/aka.ms\/GetTss<\/a><\/strong><\/u><\/u><\/p>\n

(link still works as of this writing)<\/u><\/u><\/p>\n

Website will automatically download file\u00a0TSSv2.zip<\/strong><\/p>\n

2.<\/h1>\n

Copy the downloaded file (tssv2.zip) to the server (or servers if belonging to AlwaysOn Availability Groups) with issues. It is preferred (Microsoft’s preference) to put TSSv2 into C:\\Temp<\/strong><\/p>\n

<\/u>\u00a0<\/u>ATTENTION: Run on all servers if using High Availability<\/strong><\/p>\n

\"\"<\/a><\/p>\n

3.<\/h1>\n

Extract its contents (right-click to extract) in a folder (i.e C:\\Temp\\Tssv2<\/strong>)<\/p>\n

\"\"<\/a><\/p>\n

4.<\/h1>\n

Then hit the Extract<\/strong> button.<\/p>\n

\"\"<\/a><\/p>\n

5.<\/h1>\n

Open an administrative Powershell session.\u00a0 That can be done by right clicking on the Powershell icon, and choosing “Run as administrator<\/strong>“.\u00a0 Please note that the TSSv2 utility need the administrative permissions to collect the needed information.<\/p>\n

\"\"<\/a><\/p>\n

6.<\/h1>\n

The TSSv2 utility needs to run in the extracted folder. Type:\u00a0 cd\u00a0 C:\\Temp\\Tssv2<\/strong><\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

7.<\/h1>\n

Type (or cut & paste):<\/u><\/u><\/p>\n

.\\TSSv2.ps1 -SDP SQLBase -noPSR -AcceptEula<\/strong><\/u><\/u><\/p>\n

and hit Enter key.<\/p>\n

\"\"<\/a><\/p>\n

8.<\/h1>\n

If this is the first time you are running it, the following message will appear and you just need to choose\u00a0R\u00a0<\/strong>or\u00a0A<\/strong><\/p>\n

9.<\/h1>\n

After few seconds\/minutes it will ask you if you allow the collection to gather security event logs. Type\u00a0Yes<\/strong> and hit enter.<\/p>\n

\"\"<\/a><\/p>\n

10.<\/h1>\n

A pop-up status box may appear to show the utility is running.\u00a0 Depending on the server, it may run for about 5 minutes.<\/p>\n

<\/u>\u00a0<\/u>Click though any errors that may appear, like “zip file not found.”<\/p>\n

\"\"<\/a><\/h1>\n

11.<\/h1>\n

After some minutes the collector will finish and a message will be displayed, \u00a0 givng the output files will be store as\u00a0zip\u00a0<\/strong>on the path given at the ending message.<\/p>\n

\"\"<\/a><\/p>\n

12.<\/h1>\n

At this writing, the location of the zip file will be in the C:\\MS_DATA\\SDP_SQLBase<\/strong> folder.\u00a0 Copy that zip file, and upload it to your Microsoft case.<\/p>\n

\"\"<\/a><\/p>\n

Side Note:<\/strong><\/p>\n

Every time I run this utility, my security team reaches out to me because of the number of security alerts that this utility sets off (very locked down environment).\u00a0 This utility does collect registry information.\u00a0 Once the zipped file has been uploaded to your case, best to remove these files the TSSv2 utility collected from the server.<\/p>\n","protected":false},"excerpt":{"rendered":"

(If pictures are not being displayed below, try viewing this post in Microsoft Edge browser) When opening a support case with Microsoft for SQL Server, sometimes they ask for information … Continue Reading →<\/a><\/p>\n","protected":false},"author":1,"featured_media":2089,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[204,206,205,203],"class_list":["post-2083","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sql-server","tag-microsoft-case","tag-powershell","tag-sqlbase","tag-tssv2"],"_links":{"self":[{"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/posts\/2083"}],"collection":[{"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2083"}],"version-history":[{"count":7,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/posts\/2083\/revisions"}],"predecessor-version":[{"id":2100,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/posts\/2083\/revisions\/2100"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/media\/2089"}],"wp:attachment":[{"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2083"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2083"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2083"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}