• 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