Post by account_disabled on Jan 9, 2018 1:17:35 GMT -5
What I noticed did work is installing a new SQL server and instance, but trying to restore a db backup used in a different instance already installed on system, makes the restore process fail every time with an error saying it cannot find the instance location.
So you would literally have to make a new db and connect samba that way. But no one wants to redo everything they worked so hard on all over again. Thus as previously suggested by a member here
Allow system restore points, so at least you can restore to previous times in case something like this happens, otherwise you may end up having to reset entire PC on win 10
I didn't find the right solution from the Internet.
Post by thomasliddledba on Jan 9, 2018 7:58:43 GMT -5
account_disabled Reading through the thread what might be extremely helpful is the ERRORLOG for SQL Server to find out why it won't start. Typically you can find this in the Log directory in the C:\Program Files\Microsoft SQL Server\.... or search your system for ERRORLOG. You might see a couple ending in extensions .1......3. We would need to see all of them.
The error log on a clean running system and a system that fail(s) would be great.
There is not enough information in the thread to determine root cause.