Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot start a custom-named pssdiag service using the /A parameter #195

Open
PiJoCoder opened this issue Oct 6, 2022 · 0 comments
Open
Labels
wave 2 consider this issue for next wave of fixes

Comments

@PiJoCoder
Copy link
Contributor

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Cannot start a custom pssdiag service using
pssdiag.ps1 START /A "pssdiag1"

**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem **

powershell -File pssdiag.ps1 -R -A "pssdiag_joe"
powershell -File pssdiag.ps1 start -A "pssdiag_joe"

Error:
C:\temp\pssd\pssdiag.ps1 : Parameter set cannot be resolved using the specified named parameters.
+ CategoryInfo : InvalidArgument: (:) [pssdiag.ps1], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : AmbiguousParameterSet,pssdiag.ps1

What is the expected behavior?
To be able to run the second command above

Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?

@PiJoCoder PiJoCoder added the wave 2 consider this issue for next wave of fixes label Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wave 2 consider this issue for next wave of fixes
Projects
None yet
Development

No branches or pull requests

1 participant