FDLauncher cannot be stopped automatically

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.

If you are using Full text index, then you should have a service named 'MSSQLFDLauncher', and usually it should be stopped automatically when you stop SQL Server serivce. This is the expected behavior because SQL Server will send request to service control manager to stop the FDlauncher.

But recently I'm trying to configure my SQL Server service account with the GMSA account, however, when I stopped SQL Server, the FDLauncher was not stopped automatically. So I collected a service ETL log, and found below errors:

[6] 0008.41C8::03/07/22-14:00:27.5646147 [SCM] scopen_cxx1027 ScOpenService() - ScOpenService: ScAccessValidate Failed 5, service MSSQLFDLauncher

The GMSA account was configured with all of the permissions required by below public doc before I used it,

https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-windows-service-accounts-and-permissions?view=sql-server-ver15 

But seems it requires more priviledge to control the service, so after a short time research, I got to know how to grant the permission to control a service, we have several ways actually:

http://woshub.com/set-permissions-on-windows-service/#:~:text=How%20to%20Allow%20Non%20Admin%20Users%20to%20Start,way%20to%20manage%20service%20permissions%20is...%20See%20More. 

After granted the 'Read Control','Service Start','Service Stop' permission to the account, the FDlauncher can be stopped correctly.