Enable-DbaAgHadr fails when run on servers with PolyBase installed

[packfan73]

Verified issue does not already exist?

I have searched and found no existing issue

What error did you receive?

WARNING: [10:22:33][Update-ServiceStatus] (MSSQLSERVER on SQL-node1) The attempt to stop the service returned the following error: The se
rvice cannot be stopped because other services that are running are dependent on it.
WARNING: [10:22:33][Update-ServiceStatus] (MSSQLSERVER on SQL-node1) Run the command with '-Force' switch to force the restart of a dependent SQL Agent

Steps to Reproduce

Run command on servers with the PolyBase feature installed:

Enable-DbaAgHadr -SqlInstance SQL-node1, SQL-node2 -Force

Please confirm that you are running the most recent version of dbatools

ModuleType Version Name ExportedCommands

---

Script 2.1.22 dbatools {Select-DbaObject, Set-DbatoolsConfig, Add-DbaAgDatabase, Add-DbaAgListener...}

At the time I ran the Enable-DbaAgHadr command this was the latest.

Other details or mentions

Wasn't really sure why it wasn't working as it worked fine for numerous server builds prior to this. I decided to try stopping the SQL Server Service directly and it prompted me for not just SQL Agent but also the PolyBase services. These are not accounted for in the modules, which probably isn't too surprising as PolyBase isn't the most common service out there. I also noticed that these services aren't in the Stop-DbaService -Type list, only Agent,Browser,Engine,FullText,SSAS,SSIS and SSRS are covered.

What PowerShell host was used when producing this error

Windows PowerShell (powershell.exe), Windows PowerShell ISE (powershell_ise.exe)

PowerShell Host Version

PSVersion 5.1.17763.5328
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.5328
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

SQL Server Edition and Build number

SQL Server 2022 CU12

.NET Framework Version

PSChildName Version

---

Client 4.8.03761
Full 4.8.03761
Client 4.0.0.0

[potatoqualitee]

thank you for the report @packfan73

@claude please research to understand what is going on and let me know. if it can be fixed, pls create a PR

[claude]

Claude finished @potatoqualitee's task —— View job • claude/issue-9443-20251028-0310 • Create PR ➔

---

Enable-DbaAgHadr PolyBase Issue - Fixed ✓

Tasks

• Research Enable-DbaAgHadr command and service management code
• Understand how service dependencies are currently handled
• Identify PolyBase service types and requirements
• Implement fix to handle PolyBase services
• Update tests if needed
• Commit and push changes
• Provide PR URL

Findings

The issue is clear now. When Enable-DbaAgHadr runs with -Force, it calls Stop-DbaService and Start-DbaService to restart the SQL Server services (lines 123-124 in Enable-DbaAgHadr.ps1). However:

Current State:

• Get-DbaService.ps1 (line 120): Already supports PolyBase and Launchpad service types
• Stop-DbaService.ps1 (line 106): Missing PolyBase and Launchpad - only has: Agent, Browser, Engine, FullText, SSAS, SSIS, SSRS
• Start-DbaService.ps1 (line 93): Missing PolyBase and Launchpad
• Restart-DbaService.ps1 (line 102): Already supports PolyBase and Launchpad

The Problem:
When stopping the Engine service with PolyBase installed, Windows requires PolyBase services to be stopped first (they are dependencies). However, Stop-DbaService doesn't recognize PolyBase as a valid service type, so it can't automatically stop dependent PolyBase services.

Changes Made

1. Stop-DbaService.ps1:

   • Added PolyBase and Launchpad to the ValidateSet for the Type parameter
   • Updated help documentation to include these service types
   • Enhanced Force logic to automatically include PolyBase services when stopping Engine services
   • Now when -Force is used with Engine services, it will automatically stop both Agent and PolyBase dependencies

2. Start-DbaService.ps1:

   • Added PolyBase and Launchpad to the ValidateSet for the Type parameter
   • Updated help documentation to include these service types

3. Update-ServiceStatus.ps1:

   • Updated warning message to mention both SQL Agent and PolyBase as dependent services

These changes ensure that Enable-DbaAgHadr -Force will now properly handle PolyBase service dependencies when restarting SQL Server services.

Summary

The fix has been implemented and pushed. This brings Stop-DbaService and Start-DbaService in line with Get-DbaService and Restart-DbaService, which already supported these service types. The enhanced Force logic in Stop-DbaService now automatically handles PolyBase dependencies, so Enable-DbaAgHadr -Force will work correctly on servers with PolyBase installed.

---

Branch: claude/issue-9443-20251028-0310 |