SQL -- Can't Restore Master. Wrong Version.

John Jakob 26 Reputation points
2021-11-26T18:32:32.91+00:00

Hi. Our production SQL Server crashed. Need to restore the master database from backup.

Tried executing the following in single-user mode:

restore database master from disk = 'X:\MSSQL\BAKS\master\master_BACKUP_20211124_120013.BAK' with replace;

Got the following error:

Msg 3168, Level 16, State 1, Line 3
The backup of the system database on the device X:\MSSQL\BAKS\master\master_BACKUP_20211124_120013.BAK cannot be restored
because it was created by a different version of the server (14.00.3411) than this server (14.00.3421).
Msg 3013, Level 16, State 1, Line 3
RESTORE DATABASE is terminating abnormally.

The problem is, we don't have the install binaries for SQL Server 14.00.3411 (CU 26) and cannot download version 14.00.3411 [what it says is needed]. Websites won't allow us to download that version. When we try, we can only see the details. And they keep pushing us to the latest CU update -- version 14.00.3421 (CU 27) instead.

Is there any location we can download the 14.00.3411 (CU 26) from? Thoughts?

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,251 questions
0 comments No comments
{count} votes

Accepted answer
  1. Erland Sommarskog 98,731 Reputation points
    2021-11-26T21:58:39.11+00:00

    If you look at the KB article for CU26, it includes this passage:

    After future cumulative updates are released for SQL Server 2017, this and all previous CUs can be downloaded from the Microsoft Update Catalog. However, we recommend that you always install the latest cumulative update that is available.

    I went to that link and entered SQL Server 2017 in the search box, and CU26 was close to the top.

    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. John Jakob 26 Reputation points
    2021-11-26T23:09:09.91+00:00

    Thanks. Finally managed to download the patch. The download options in the Microsoft Update Catalog perform a little unpredictably -- not what one usually expects. Can close this case.

    0 comments No comments

  2. Ronen Ariely 15,081 Reputation points
    2021-11-26T23:46:43.1+00:00

    Hi,

    because it was created by a different version of the server (14.00.3411) than this server (14.00.3421).

    According to the message your current version of the server is Cumulative Update 27 and your last backup was done before the update. In order to use that the old backup you will need an instance of that version and probably rebuild all the system databases to that version.

    The problem is, we don't have the install binaries for SQL Server 14.00.3411 (CU 26) and cannot download version 14.00.3411 [what it says is needed].

    What should have been done if you managed the server in the right way is to have a backup after your upgraded the server. Well... this is for next time :-)

    I will describe what I would probably do (at least start to do and think as I go), but anything you do is on your responsibility as this is only the basic information and it is best to do it with an expert near you.

    First of all, I would backup all the user database!!!

    If we can login the server and use the BACKUP command then create full backup of all the databases (system and user).

    If the server is not available then stop the service and backup the files (all of them)

    Remember to check the backups before moving forward! A backup which was not tested is not a backup which we can count on.

    Next there are two approaches

    Option one: start from new and upgrade to CU26

    if you have backups of all your other system database from the older version and you are OK with losing any information between these backup and now, then we can install new instance -> update to CU26 (Erland gave you the link) and restore all the system databases using the backups -> next we can bring the user databases.

    This is complex and long...

    Option two: simply uninstall the latest CU and downgrade to CU26

    I have no idea what is corrupted in your databases but in theory this is a simple solution, which does not require any old file of CU26.

    It is well documented in the document of CU 27 just like in most CU upgrade document you have information about how to go back:

    https://support.microsoft.com/en-us/topic/kb5006944-cumulative-update-27-for-sql-server-2017-79117c8f-9d54-42f8-9727-5870fe475187

    Scroll down to the title: How to uninstall this update on Windows

    152974-image.png

    Note! MAKE SURE THAT YOU DO NOT UNINSTALL THE BASE INSTALLATION OF THE SERVER BUT ONLY THE LAST CU. If you select a wrong file then you might uninstall the entire server, which mean that next you go back to option one.

    0 comments No comments

  3. John Jakob 26 Reputation points
    2021-11-27T01:46:18.01+00:00

    > why do you need the file and re-install new instance and upgrade to CU26 if you can simply downgrade to CU26 with no file?

    Well, we were installing SQL 2017 from a DVD or disk image that was somewhat older. I uninstalled the latest CU (27) under "Control Panel / Programs and Features / Installed Updates" as you described -- but that brought us back to an old version of SQL 2017 (whatever the DVD/image had) prior to CU 26. Needed the patch file to get to CU 26 so we could then be at the right version.