Have you ever encountered the error message “Script level upgrade for database ‘master’ failed because upgrade step ‘sqlagent100_msdb_upgrade.sql’ encountered error 598, state 1, severity 25”? If so, you’re not alone. This error can be caused by multiple reasons and can be quite frustrating to troubleshoot. In this blog post, we will explore the possible causes of this error and discuss how to resolve it.

First, let’s take a closer look at the error message itself. The error message indicates that there was a failure during the upgrade process for the ‘master’ database. This upgrade step, specifically the ‘sqlagent100_msdb_upgrade.sql’ script, encountered an error (error 598) which prevented the upgrade from completing successfully. As a result, the entire SQL Server instance may be taken offline.

One possible cause of this error is a configuration issue related to the failover cluster manager. In the example provided, the error was resolved by adding the missing dependency for the F drive in the SQL Server resource properties. This dependency was necessary for the upgrade script to run successfully and bring the SQL resource online.

It’s important to note that this error is not a real corruption of the master database, but rather a side effect of earlier errors. In some cases, restoring the master database from a full backup or repairing/rebuilding it may be necessary to resolve the issue.

When encountering this error, it’s crucial to examine the previous errorlog entries for any related errors and take appropriate corrective actions. This may involve checking the failover cluster manager, verifying dependencies, and ensuring that all necessary resources are properly configured.

While this particular error may be more related to clustering and configuration problems, it serves as a reminder that troubleshooting SQL Server issues can sometimes be complex and require a thorough understanding of the underlying system.

In conclusion, SQL Server error 15559 can be caused by various factors, including configuration issues with the failover cluster manager. By carefully examining the error message and taking appropriate corrective actions, you can resolve this error and ensure the smooth operation of your SQL Server instance.