Run the RECONFIGURE statement to install. 13:06:47.29 spid6s Configuration option 'Agent XPs' changed from 1 to 1. 13:06:47.29 spid6s Configuration option 'show advanced options' changed from 1 to 1. Here is the full error log of SQL Server. Now the new installed instance has the same problem. So I installed another instance of the same SQL SERVER 2017 and restored databases. 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.`Īfter some googling I found out I can run it with /T902 switch and try to fix the problem. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. This is a serious error condition which might interfere with regular operation and the database will be taken offline. Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 200, state 7, severity 25. When I checked event log I saw this error: When I wanted to run the service manually it showed 3417 error. 14 (X64) 07:47:45 Copyright (C) 2017 Microsoft Corporation Enterprise Edition (64-bit) on Windows 10 Enterprise 10.0 (Build 17134: )` I have SQL Server 2017 installed on my computer.
0 Comments
Leave a Reply. |