Edit

Share via

SQL Server upgrade fails with error 5133 when executing update database scripts

  • Article

This article helps you troubleshoot and solve an issue where a cumulative update (CU) or service pack (SP) for SQL Server reports error 5133 when executing database upgrade scripts.

Symptoms

When you apply a CU or SP, the setup program may report the following error:

Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.

When you review the SQL Server error log, you may notice the following error messages:

Error: 5133, Severity: 16, State: 1
Directory lookup for the file "<path>\MSSQL10.<Instancename>\MSSQL\Data\temp_MS_AgentSigningCertificate_database.mdf" failed with the operating system error 3(The system cannot find the path specified.).
Error: 1802, Severity: 16, State: 1.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
Error: 912, Severity: 21, State: 2.
Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 598, state 1, severity 25.
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.
Error: 3417, Severity: 21, State: 3.
Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.

Cause

SQL Server reports error 5133 when it encounters an operating system error when trying to determine the directory of a file. SQL Server reports error 598 when it runs into an error while executing CREATE DATABASE or ALTER DATABASE statements.

Note

From Database Engine events and errors, you can see Error 598: An error occurred while executing CREATE/ALTER DB. Please look at the previous error for more information.
Entries prior to error 598 can provide more information about the cause of the failure. For example, in this article, the preceding error is 1802, which occurs because the upgrade script is unable to create a temporary database in the default data path. The temporary database is used by the setup program for various operations it runs during the update process. For more information about database upgrade scripts that are executed during CU or SP installation, see Troubleshooting upgrade script failures when applying an update.

Resolution

  1. Verify that the Data Path property is configured with a valid and correct value in SQL Server.

    • From SQL Server Configuration Manager:

      1. Open SQL Server Configuration Manager and select SQL Server Services.

      2. Right-click the SQL Server instance and select Properties.

      3. Select the Advanced tab and verify that the value of Data Path is correct and doesn't have any typos or extra characters. (To validate the value, you can copy it and try to access it with Windows Explorer.)

    • From Windows Registry Editor:

      1. In the Search box on the taskbar, type regedit to open Registry Editor.

      2. Navigate to the registry key for the default data path. Then, validate that the path is correct and has no extra spaces or characters. The registry key for the default data path is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.<Instance Name>\Setup\SQLDataRoot.

        If the registry key has the correct data path, and you continue to receive the error, follow these steps:

        1. Navigate to the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.<Instance Name>\MSSQLServer\Parameters.

        2. Review and change the value of Data Path to match the value in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.<Instance Name>\Setup\SQLDataRoot.

  2. Restart the SQL Server instance.

    Once the SQL Server instance starts, the upgrade script will be executed again.

    • If the SP or CU upgrade script completes successfully, you can check the SQL Server error log and bootstrap folder to verify.
    • If the upgrade script fails again, check the SQL Server error log for other errors and troubleshoot the new errors.