microsoft / microsoft/sql-server-samples
invoke-sqlassessment returns warning
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 11.2k
- Forks
- 9.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 14
Description
PS 5.1, Windows 2019 , SQL 2019, SQLSERVER module 21.1.18245
"sqlag000" is the local server name / default instance. Execution policy is unrestricted (to test).
Get-SqlInstance -ServerInstance sqlag000 | invoke-sqlassessment
WARNING: Checks 'AgentSvcStoped', 'BrowserSvcStoped', 'DtsSvcStoped', and 2 more have been skipped because they need access to PowerShell
In the SQL Server logs, I see "Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed."
All of the servers use integrated authentication.
I get the same warning message from all of the 2019 servers I'm testing.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the warning with Get-SqlInstance -ServerInstance sqlag000 | Invoke-SqlAssessment using SQLSERVER module 21.1.18245 on the stated Windows and SQL Server versions. Start by tracing how the command authenticates and why AgentSvcStoped, BrowserSvcStoped, DtsSvcStoped, and the other checks are skipped. Done means the cause of the integrated-authentication failure is identified and the warning behavior is corrected or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100