Forum Discussion
Windows Server 2022 Remote Desktop Services installation is failing
thanks a lot for ur reply. Tried the current evaluation version of windows server 2022 - also allowed to download the available updates before the installation. Also tried a newly bought Windows Server 2022 essentials edition. Always the same issue. Already checked the Event Logs. The reason for the errors seems to be the windows internal database service - at least the Event Logs tell me that. Already tried a work around and wasted 2 days searching for a solution. This is why I soley tried to install the windows internal database service. But the installation abortet, too. The error message is (trying to translate it correctly from German): the windows internal database service has been unexpectetly terminated. This is also the same error that occurs when I try to install the RDS - this exact error message also occurs during the installation of the Connection Broker. With Windows Server 2019 - the installation of the RDS Roles works perfectly.
Thanks again for ur response.
My apologies Werner, I missed the part in your original post where you indicated that it "couldn't be started". So it seems the installation process is fine, the problem is starting the service(s) afterwards.
As a quick test, I installed all the RDS components (including WID) into a blank updated 2022 RTM VM (US English) and it seems to all work there.
However, as you might know, the WID (Windows Internal Database) is just a SQL Server instance. Naturally, it has its own log files too, which you'll find in the C:\Windows\WID\Log folder as "error.log", "error1.log", etc. The naming of the log files is a bit deceptive, as even without errors, they're still the main log files. It's likely the problem will become more clear in these files.
If there are no log files in that folder, it means the WID service has never started. The service uses its own service account (NT SERVICE\MSSQL$MICROSOFT##WID) to start, but if it doesn't have the rights to start as a service, or some other problem, that may be where you should be looking. I stress this is likely not the solution to your problem, but I found an example of that on Server 2012 R2.
- Hello Jonathan, thanks a lot for ur reply. Sadly I‘m super busy with work right now - so I can test ur suggestions immediatly. But I‘m going to test! Thanks again for ur reply - I‘ll give feedback as soon as I have done some further testing. BTW I think that the WID serice could‘t start, cause its installation failed. Thanks again for ur great feedback.
