Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,244 questions
Can't start "Windows Internal Database" service
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 85%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
Maksim Maksim
31
Reputation points
Hello!
Have RDS host with some Virtual desktop, until blue screen what got today at night everything was working fine, but now can't start 3 services
- VDH-MAIN Remote Desktop Management RDMS Stopped Automatic (Delayed Start)
- VDH-MAIN RemoteApp and Desktop Connection Management TScPubRPC Stopped Automatic
- VDH-MAIN Remote Desktop Connection Broker Tssdis Stopped Automatic
Using windows server 2019.
When I tried to start manually Remote Desktop connection Broker. getting 3 errors on System logs:
- The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.
Service: MSSQL$MICROSOFT##WID
Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID
This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.
2. The Windows Internal Database service failed to start due to the following error:
The service did not start due to a logon failure.
3. The Remote Desktop Connection Broker service depends on the Windows Internal Database service which failed to start because of the following error:
The service did not start due to a logon failure.
As I have understood problem is with Service "Windows Internal Database" and user MSSQL$MICROSOFT##WID
What is that for the user, and do I need to add him to any specific group?
Thanks.
At moment I have started Windows Internal Database service with a domain administrator account, after that, I was able to start all services.