Of late, I have been contacted by few clients who have been facing issues with SQL startup failure after applying patch to SQL Server instance. This blog is an outcome of one such assistance provided. Here is a blog post where I discuss script level upgrade for database master fails.
Once the patch was applied, SQL service was not able to start. So, I asked for SQL Server ERRORLOG SQL SERVER – Where is ERRORLOG? Various Ways to Find ERRORLOG Location
Here is the relevant information.
spid5s Cannot bulk load. The file “C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Install\SqlTraceCollect.dtsx” does not exist.
Whenever there is an upgrade failure, we always see “Cannot recover the master database. SQL Server is unable to run.” This is a side effect of upgrade failure.
From the first error message, it is clear that we are missing files SqlTraceCollect. dtsx from C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Install So there are two ways to fix it.
- Get the file from the server which has exactly the same build of SQL Server installed successfully.
This would be a quick fix, but we may have some more files missing which we can never figure out.
- The right thing to do at this point is to uninstall the patch which we last applied and then “Repair” the instance. Here is the option in setup installation center.
If it is repaired successfully, we should get the files back and then we can apply the patch again.
Have you ever seen any other errors in script upgrade mode?
Reference: Pinal Dave (https://blog.sqlauthority.com)