I’m writing this as a reminder to myself for a problem I just had to solve. When running the PSSDIAG tool, if you are running it against SQL 2016 SP2 or higher, you may get the following error:
There is no instance named “YourServer”
Message: The parameter is incorrect
The reason for this is that the INSTANCE value in the pssdiag.xml config file is set to the SQL Server name instead of the default instance name. Luckily, this is an easy fix. If you are running the default instance of SQL, look in the pssdiag.xml file and find the following “Instance” XML tag:
|
1 2 3 |
<Instance name="YourServer" user="" windowsauth="true" ssver="13"> |
Once you’ve found it, you can change it to:
|
1 2 3 |
<Instance name="MSSQLSERVER" user="" windowsauth="true" ssver="13"> |
Simply replacing “YourServer” with the default instance name of “MSSQLSERVER” should be all you have to do. Just save it and try to run the tool again. I was able to figure this out by reading through this Microsoft Docs article.
YMMV, but that’s what worked for me!
Pingback: There Is No Instance Named X Error in PSSDiag – Curated SQL