Master DB corrupted

Hi all,

Today Epicor stopped working all of a sudden. When we checked the SQL server, we noticed that some of the SQL services stopped and, when we tried to start them, we get an error (like SQL server cannot run on this local machine). When we checked the event viewer, we found several errors saying that ‘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.’
Can anybody assist with this, it the first time we’re seeing this.

5 Likes

Do you have SQL backups?

If you do, it’s a pretty easy fix. Just follow Microsoft’s procedure and you’ll be back up and running.

We do have backups for live, test, pilot but I’m not sure about the master DB. We’re currently trying to retrieve that.

If you find you don’t have a master backup you’re not out of luck. An alternative option is restoring master from the SQL setup media.

If you don’t have a master backup here’s the process using the setup media. Make sure you take backups of your other dbs before doing this.

This seems scary but it’s nothing that can’t be fixed. Just follow the Microsoft process and you’ll be back up and running. Just make sure you have a good backup of your dBs before you start the recovery.

Keep us posted!

Once you’re up and running toss the system dBs into a backup job.

3 Likes

Update - this was a Windows update issue. We noticed win update ‘SQL Server 2016 Service Pack 3 (KB5003279)’ failed and, after we uninstalled it, we could connect with no issues. Thank you Microsoft!

The issue I’m having now is I can’t print anything. I’m getting the same error below:

Program Ice.Services.Lib.RunTask raised an unexpected exception with the following message: RunTask:
System.InvalidOperationException: Client found response content type of ‘’, but expected ‘text/xml’..

2 Likes

Ooft. I would turn off automatic SQL updates. This has been a problem for several versions of SQL. Microsoft has a lot of update problems…

Season 2 Smh GIF by The Lonely Island

3 Likes

Found the issue for the print errors - the win update deleted the folder below from the SQL server. Recreating that folder fixed the issue. Thanks again Microsoft!

‘C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files’

2 Likes