RDCms Database Stuck in Recovery Pending Mode After Reboot

Ryan Custer 1

We have an RDS deployment with a connection broker / gateway server and two session hosts.

We are having the issue where the RDCms database goes into recovery pending mode after each reboot. We have to connect the database manually, take it offline and then bring it back on line to get it to work.

The errors in the WID log at the time are:

2022-01-02 00:17:43.07 spid51 Starting up database 'RDCms'.
2022-01-02 00:17:53.28 spid51 Failed to verify Authenticode signature on DLL 'C:\Windows\WID\Binn\DBVerify\rdcmsDbVerify.dll'.
2022-01-02 00:17:53.34 Logon Error: 18456, Severity: 14, State: 38.
2022-01-02 00:17:53.34 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database 'RdCms'. [CLIENT: <named pipe>]
2022-01-02 00:17:57.76 Logon Error: 18456, Severity: 14, State: 38.
2022-01-02 00:17:57.76 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database 'RdCms'. [CLIENT: <named pipe>]
2022-01-02 00:17:57.77 Logon Error: 18456, Severity: 14, State: 38.

I found this article: https://social.technet.microsoft.com/Forums/en-US/8f032597-9eff-4876-8239-fca71b8d118d/rds-broker-database-rdcms-status-quotrecovery-pendingquot-after-reboots?forum=winserverTS

But the RDCms.dbo.sysdiagrams table does not exist within the database in our environment.

This is getting cumbersome for our customer and any assistance would be greatly appreciated.

Thanks!

2 answers

Michael Henkes 1 Reputation point

2022-12-19T09:31:38.683+00:00

We have the same issue here.
WServer 2019 with RDS roles installed
After a WUpdate reboot, the server won't allow RDP sessions from users. Admins can still login.
The issue seems to come from this WID error so the connection broker doesn't work.

"Failed to verify Authenticode signature on DLL 'C:\Windows\WID\Binn\DBVerify\rdcmsDbVerify.dll'."

After a second manuel reboot, the issue is gone

No RDCms.dbo.sysdiagrams

Please fix this Microsoft
Please sign in to rate this answer.
TP 75,736 Reputation points

2022-12-19T10:26:32.277+00:00

Hi,

Does the problem still exist, or did it resolve itself after the second restart?

-TP

Michael Henkes 1 Reputation point

2022-12-19T11:08:01.12+00:00

After the second restart, the users can connect again.
But we had this issue a lot in the last weeks/month, probably after winupdate restarts.
The root cause of the issue is not solved

Our workaround is to schedule a second reboot via task but this can't be the final solution...

Ryan Custer 1 Reputation point

2022-12-19T13:51:33.657+00:00

This is still happening to us as well. It isn't every Windows update. Seems like it happens about every other month.

Mik Kirk 11 Reputation points

2022-12-20T00:00:07.593+00:00

Got this exact error happening on two separate RDS servers. Unable to find a solution online.

TP 75,736 Reputation points

2022-12-20T00:19:33.59+00:00

@Mik Kirk Are you seeing same symptoms in that the problem resolves itself after a second restart?

Mik Kirk 11 Reputation points

2022-12-20T00:22:11.657+00:00

Yes that is correct. I see the same errors in the log on both servers and a second manual reboot resolves the issue

Ryan Custer 1 Reputation point

2022-12-20T00:28:12.027+00:00

If it is not fixed with a second restart, there is another method I have used to fix it:

Install SQL Management Studio on the server..

Run SQL Management Studio as administrator.

Connect to this string: np:\.\pipe\MICROSOFT##WID\tsql\query

Expand databases

You will then see the database as RDMS (Recovery Pending)

Right click on the database and choose Tasks > Take Offline. Check the box to remove all connections and click ok.

Right click on the database again and choose Tasks > Bring Online.

TP 75,736 Reputation points

2022-12-20T00:47:23.747+00:00

@Ryan Custer When the problem isn't resolved with a 2nd restart, then it can be fixed following the troubleshooting steps I outlined in the old TechNet post you linked to above. The key thing is, it is more than just deleting the sysdiagrams table. That was just the one step of several that I walked the person through to resolve it.

The key takeaway is, there seems to be two issues: 1) a long-standing one where the RDCms database is modified in some way (tables added, table modified, procedure added, etc.) which causes the validation that occurs at startup to fail, leaving the database in Recovery Pending state. For this first one perhaps I need to write a new article with a utility/script to help correct it. 2) a more recent issue involving windows updates. For some reason the validation dll fails integrity check after first restart, causing database validation to fail, but issue is correct upon second restart after update.

Ryan Custer 1 Reputation point

2022-12-20T00:51:47.527+00:00

Thanks for the quick replies and further information! In my case it definitely seems like #2 is the case.

Grant Wilson 0 Reputation points

2024-03-28T15:43:44.8166667+00:00

Appreciate this is an old thread, but I was having the same issue after a patching reboot. The thing that fixed it for me was to add the TLS1.2 registry entries for 'DisabledByDefault' = 0 and 'Enabled' = 1, as detailed in the doc below.

https://learn.microsoft.com/en-us/dotnet/framework/network-programming/tls#configuring-schannel-protocols-in-the-windows-registry

Scroll down to the 'Configure Schannel protocols in the Windows Registry' heading.

Will require a reboot for these changes to take effect.

Hope this helps someone!
Sign in to comment
Michael Henkes 1 Reputation point

2023-03-12T19:33:13.73+00:00

The issue is still occuring, even after a random restart (no win-updates)

Please fix your shit Microsoft
Please sign in to rate this answer.
Ryan Custer 1 Reputation point

2023-03-13T12:30:43.0833333+00:00

Seriously. I don't think they care. When I did open a case, they never could end up figuring it out. Told me to rebuild the gateway / connection broker.
Sign in to comment