Assume that you have a database snapshot on a pull subscription database on a server that is running Microsoft SQL Server. When you apply a hotfix on the server, the script-level upgrade fails, and you receive an error message that resembles the following:
spid_number Performing replication job security meta-data upgrades...
date timespid_number Error: 3906, Severity: 16, State: 1.
date timespid_number Failed to update database "database_name" because the database is read-only.
date timespid_number Error: 912, Severity: 21, State: 2.
date timespid_number Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 3906, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
This problem is fixed in the following updates for SQL Server:
Cumulative Update 2 for SQL Server 2016 Service Pack 2
Cumulative Update 10 for SQL Server 2016 Service Pack 1
About SQL Server builds
Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology Microsoft uses to describe software updates.