Adding a database to an availability group can fail with the message that the database is encrypted by database master key, even when TDE is off. This post finds the key, checks what depends on it and lists three ways to continue. A demo database shows the checks and the error that protects a key still in use.
Failed to Create New NBT Interface, Status 1450: Listener Not Coming Online
Status 1450 showed up in the cluster log when a listener’s IP Address resource would not come online. The error read failed to create new NBT interface. Disabling Enable NetBIOS for this address on the IP resource fixed it.
Always On Listener Creation Failure: Enabling Object Failed With Error 5
A listener creation failure with error 5 means access was denied, and the cluster log shows who was denied. Here the cluster computer object could not enable the listener object. A domain admin gave it Full Control, and the listener came online.
Provisioning Computer Object Failed With Error 5: Always On Listener Failure
Provisioning computer object failed with error 5 is a cause of Always On listener creation failure. The cluster log showed the cluster computer object being denied access while changing the listener’s password. Giving the CNO Full Control over the listener object fixes it.
Error 15141: Upgrade Fails Because a Login Owns an Availability Group
Error 15141 means the server principal owns one or more availability groups and cannot be dropped. The msdb110_upgrade.sql script failed on a DROP LOGIN, and the script level upgrade for master failed with it. Changing the group owner to sa let the upgrade finish.
Error 35296: Log Backup on Secondary Replica Fails in a Distributed Availability Group
Log backup on secondary replica fails with error 35296 when the replica sits in the secondary availability group of a distributed availability group. A client hit it on the fourth node of their topology. It is by design, so the backup has to run on a replica that talks to the global primary.
Logical Name Mismatch: master_files vs database_files
A logical name mismatch means sys.master_files and sys.database_files disagree about a file name. A tested demo shows both views on one server, and a script checks every database. The post explains the secondary replica case and its fix.