Smbup error starting the service windows#

Because the KdsSvc service is set to be triggered as soon as one of these RPC queries occurs, the service should start (in theory).The LDAP server thread calls in to the Microsoft Key Distribution Service Provider (kdscli.dll), where it tries to find server components: Microsoft Key Distribution Service (KdsSvc), RPC endpoint from the RPC endpoint mapper (EPM).When the LDAP request is performed on a domain controller, the LDAP query can be sent back to the local server, where it is handled by a different thread in LSASS, which is the same process that issued the query.While handling the request, LSASS tries to do a Lightweight Directory Access Protocol (LDAP) search for the msDS-ManagedPassword attribute. The logon request is sent to the Local Security Authority process (lsass.exe, LSASS) that is running on the computer.

Smbup error starting the service windows#

When Windows tries to start a service that is configured to use a group Managed Service Account (gMSA), the Service Control Manager (SCM) tries to log on by using the account information for the service.

During startup, Windows enumerates all automatic services and tries to start them.

Here is an actual explanation about how GMSA account needs Microsoft Key Distribution Service is.

SQL Server Services running under the context of a gMSA service account, gMSA service relies on KDS service, however the 'Microsoft Key Distribution Service' service is not started on the domain controller. When we checked Windows Services applet (Services.msc) we found that it was in “Starting” state. One reason could be that the service account is not properly set or could not be authenticated with domain controllers. When we tried to start SQL server using GMSA account, we found the SQL Server could not start due to timeout. In this post we would like to explain one of the interesting issues that we encountered where SQL Server uses a gMSA as its service account.

Consult the event log or other applicable error logs for details”. What is infuriating, is that until I restarted the server today, my workaround of restarting the service every 3 minutes actually worked, with no application downtime whatsoever.ĭoes anybody have any suggestions? I did try changing the registry key of ServicesPipeTimeout to 86400000 (24 hours!) in a bid to keep the service in the status of 'Starting' for longer.GMSA is used for SQL service and its failing to start with error “the request failed, or the service did not respond in a timely fashion. In this question, I am not trying to solve the problem, but rather find a workaround to try and keep this service in a status of 'Starting' the whole time. I did open a separate question whose aim was to actually solve the problem. I have intentionally not named the errant service. In additional it takes an additional 30 seconds or so for my application (which is dependent on this service) to start working. Therefore there is a gap of about 22 seconds from when the service fails until it starts up again. I have a windows scheduled task that runs every minute to restart the service if necessary. My web application works fine when the service is in the 'Starting' mode. Unfortunately, the windows service does not start properly, but remains in a status of 'Starting' for about 7 minutes and 38 seconds, and then fails. I have a critical windows service that I need for my web application.