May 31, 2019 at 7:05 pm
I might be wrong.. but wouldn't restoring the master database clear this up? if you have a recent backup and you havent done anything else with that database since.. seems like a pretty quick solution.. though I would only do this if everything else on that instance was unencrypted and keys dropped first.. just in case.
June 3, 2019 at 1:31 pm
Hrmmm. Maybe it would, but restoring master is kind of drastic and labor-intensive. If I'm going to go that far, I might as well uninstall and reinstall the entire instance. Both of which I'm trying to avoid.
Surely there's another way to deal with this error? Something I could repeat (if necessary) on an instance where there are user databases.
I'm sort of the corporate guinea pig for this. We're building a document for all others to use. It would be nice to write up a "how to back out if something screws up" doc for all other users and they might not have the luxury of restoring master or reinstalling the instance.
June 11, 2019 at 7:06 am
Honestly, I'd open a support ticket with the provider. The way that third party key management solutions work with credentials can be tricky. They aren't well documented and I've struggled at times with ensuring that a login/user from SQL can properly access the keys on the device.
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply