An error occurred during decryption sql

Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Linked 0. Related 4. Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled. Accept all cookies Customize settings. This is probably the reason: blogs.

You should also test your prod environment for this issue. Thankfully we haven't yet set up linked servers in prod yet. So if I understand correctly, when I create the linked servers, their login info is encrypted using the current service master key. Then when the server is stopped and started again, something must be regenerating a different service master key. I guess the solution must be to somehow backup the service master key before taking down the instance, then restore it when the instance comes back online.

And I guess specifically in our case, SQL Server tries to decrypt the service master key using two different methods and both fail mattsql. I'd guess the local machine decryption fails because RDS isn't restoring to the same machine.

And the service account fails because it's not a domain user, which I'm not sure we can even change on RDS. Sounds almost like linked servers aren't usable on RDS. Add a comment. Active Oldest Votes. Update: July As of July , we now replicate the service master key after a host replacement.

Improve this answer. Saugat 3 3 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. The only thing I have done was to create an active directory user account called "sqlmanager" and gave Administrator, Domain Admin, and Domain User rights to him.

Next, I changed the sql service login to run using the new account sqlmanager which ran under "Local System" prior. Started the sql service and get the following errors within the error log. I have never seen this before.

In reading a number of post there was also a recommendation to disable VIA protocol, but it is not enabled. Whenever I switch the sql services to run under the "Local System" sql does start back up so I would say there is some sort of permissions error of some kind.

Any ideas would be helpful. This is an informational message only. No user action is required. To determine the cause, review the errors immediately preceding this one in the error log. Check the SQL Server error log and the Windows event logs for information about possible related problems. I am having the same issue. I have the feeling this may be due to the way the server OS was created. Bret Butler. You must be logged in to reply to this topic. Login to reply. Post reply. March 3, at am The problem that was encountered: I have a two node cluster; I will call the nodes - node1 and node2.

When SQL server starts up now, I receive the following message in the logs: