The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database

Question

Hi All,

I have Windows Server 2016 Datacenter with Remote Desktop Session Host, Remote Desktop Connection Broker and Remote Desktop Web Access roles installed.
It started to happen a while ago sporadically and now happens all the time.
Under Server Manager - Remote Desktop Services I cannot see Collections.
Instead I'm getting the error below.

I checked Event Viewer and there are numerous errors.
"The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.

Pooled virtual desktop collection name: NULL
Error: Logon to the database failed."

Does anybody know what is it so and how to fix it?

Answer 1

Hi,
1.If this problem occurred during RDS deployment, you could refer to RDMS log according to below KB for more clues.
Useful log files for troubleshooting RDS issues
https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/log-files-to-troubleshoot-rds-issues

2.Per searching, here is a useful thread where users shared their resolutions like:
https://social.technet.microsoft.com/Forums/en-US/aef50c99-0f0e-4da2-bc4c-d5435692cb8b/server-2012-rds-remote-desktop-connection-broker-client-failed-to-redirect-the-user?forum=winserver8gen

• Manually add your Remote Desktop server into the MEMBER OF tab of “Windows Authorization Access Group” via Active Directory Users and Computers. (work for the situation that there is an old DC or upgraded one)
• • Change the Windows Internal Database service to Log on as Network Service account.
• • Open server manager - RD Services - Collections and create a new one (add your server to the collection)

It is worthy to test the mentioned resolutions discussed in the thread since a number of users have tested and resolved their problems.

---

Hope this helps and please help to accept as Answer if the response is useful.

Thanks,
Jenny

Answer 2

This is what helped me.

Run cmd as administrator.
Run winrm e winrm/config/listener command.

C:\Users\Administrator>winrm e winrm/config/listener
WSManFault
Message = The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".
Error number: -2144108526 0x80338012
The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".

Run winrm quickconfig command.

C:\Users\Administrator>winrm quickconfig
WinRM is not set up to receive requests on this machine.
The following changes must be made:
Start the WinRM service.
Set the WinRM service type to auto start.
Make these changes [y/n]? y
WinRM has been updated to receive requests.
WinRM service type changed successfully.
WinRM service started.
WinRM is already set up for remote management on this computer.

Run again winrm e winrm/config/listener command.

*C:\Users\Administrator>winrm e winrm/config/listener
Listener
Address = *
Transport = HTTP
Port = 5985
Hostname
Enabled = true
URLPrefix = wsman
CertificateThumbprint
ListeningOn = 127.0.0.1, 172.30.0.8, ::1, fe80::4ded:172.30.0.8%05, fe80::18d1:b85b:1e75:ea7z%23*

Answer 3

Just wondering, what was the fix for you @Cloud_Geek_82 ?