Got an issue with my Windows Server 2016 Broker. Every time it boots the database goes in "Recovery Pending" and I need to flip it (take offline then online) to before starting the broker service again. As patch boots go at night I've got lots
of angry users every time I come to work in the morning after a patch night.
The Event Log spams: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database 'RdCms'. [CLIENT: <named pipe>]
"DBCC CHECKDB (RDCms, repair_allow_data_loss)" reports no errors
Adding NT AUTHORITY\NETWORK SERVICE to db_owner did not help.
As this is an internal database I've got no backup from before the issues started.
Anyone got a proper, permanent, solution?
K.
The Event Log spams: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database 'RdCms'. [CLIENT: <named pipe>]
"DBCC CHECKDB (RDCms, repair_allow_data_loss)" reports no errors
Adding NT AUTHORITY\NETWORK SERVICE to db_owner did not help.
As this is an internal database I've got no backup from before the issues started.
Anyone got a proper, permanent, solution?
K.