Viewing post 1 (of 1 total)
I have been running the same issue in 2016 Evaluation version on Hyper-V Machine. This is resolved by just restarting the SQL Services.
Regards
Baig
June 13, 2016 at 7:34 am
#1884645