Skip to content
This repository was archived by the owner on Oct 20, 2025. It is now read-only.

Known Issues

Jump to bottom
JosephPilov-msft edited this page Oct 4, 2021 · 7 revisions

Known Issues

  1. I receive error "Unable to find SQL Server client tools such as sqldiag.exe from this machine. Data collection will fail". If you configure pssdiag for the wrong version, you will receive this error. for example, you configure pssdiag for SQL 2012 but the server only has SQL 2016 installed.
  2. I receive error "There are no instances of version 13 on this computer" when I run Pssdiag SQL 2016 SP2. Service Pack 2 introduced some registry key changes for SQL version information. This is fixed in SP2, Cumulative Update 3. As a workaround, you can specify the particular instance name AND use wildcard * (instead of 13) in SQL version (ssver) in PSSDiag.XML. For example, for a default instance : <Instance name="MSSQLSERVER" user="" windowsauth="true" ssver="*">

Clone this wiki locally