Quantcast
Channel: Answers for "SQL Server 2012 Log"
Viewing all articles
Browse latest Browse all 6

Answer by Tim

$
0
0
I have only encountered this on a system when the DBA moved the location of the master database by stopping the service, changing the paths in the startup parameters and accidentally messed up the path for the log file location. There was either an extra slash or colon in the path. Once that was corrected everything was fine. I can only suggest double checking the exact path.

Viewing all articles
Browse latest Browse all 6

Trending Articles