Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 12111717
KB4340837 - FIX: Error 3906 when a hotfix is applied on a server that has a SQL Server database snapshot on a pull subscription database - Microsoft Support
Last update date:
6/21/2022
Affected products:
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
SQL Server 2017 Developer on Windows
SQL Server 2017 Enterprise on Windows
SQL Server 2017 Enterprise Core on Windows
SQL Server 2017 Standard on Windows
SQL Server 2014 Service Pack 2 - duplicate (do not use)
SQL Server 2014 Developer - duplicate (do not use)
SQL Server 2014 Enterprise - duplicate (do not use)
SQL Server 2014 Enterprise Core - duplicate (do not use)
Affected releases:
build lower than 14.0.3030.27
Fixed releases:
14.0.3030.27
Description:
Symptoms
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: date time 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.
Resolution
This problem is fixed in the following updates for SQL Server: Cumulative Update 9 for SQL Server 2017 Cumulative Update 2 for SQL Server 2016 Service Pack 2 Cumulative Update 10 for SQL Server 2016 Service Pack 1 Cumulative Update 13 for SQL Server 2014 SP2
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: Latest cumulative update for SQL Server 2017 The latest build for SQL Server 2016 Latest cumulative update for SQL Server 2014
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology Microsoft uses to describe software updates.
