Restore master from a full backup, repair it, or rebuild it. 09:40:26.60 spid6s Cannot recover the master database. Otherwise, restore from backup if the problem results in a failure during startup. If this error occurred during replication, re-create the publication. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). 09:40:26.46 spid6s The log scan number (1545:236:1) passed to log scan in database 'master' is not valid. 09:40:25.21 spid6s Starting up database 'master'. There are no backups of the master and the SQL instance will not boot without the master file. There are multiple clients with the same setup and data (minus the till number). An insert of the Error log is below and the full log is attached. The client side had power issues and not the Master File is corrupt. We have a PoS system that uses a local database to keep settings and points the data storage to the server. I can remove and recreate this SQL instance (will take a few minutes), but I would rather know how to fix this issue, should it happen again in the future. I have a learning opportunity and want to try learn something new.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |