Re: An error occurred during decryption

The issue that I am seeing on my cluster is any linked servers using sql
authentication created on NodeA fail when I move over to NodeB. They work
fine when I fail back to NodeA. The error I get is:

An error occurred during decryption

That is really the only link between the cluster and linked server. This
error occured both during an upgrade of the server and a new server
installation. Before I regenerate the key, I just want to know how
destructive the regenerate could be. Anything that I may need to recreate, I
want to have scripted before my maintenance window starts.


"Laurentiu Cristofor [MSFT]" wrote:

It does look like an error with the service master key decryption. Have you
copied your master database from another instance or performed any changes
to your installation before starting to see this?

I wrote a post on this exact topic on my blog. See
http://blogs.msdn.com/lcris/archive/2006/04/10/572678.aspx.

Also, I am not clear of what you mean by linked servers and how do they
relate to your clustered installation and encryption. Can you elaborate on
your setup?

Thanks

--
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/

This posting is provided "AS IS" with no warranties, and confers no rights.

"Dave B" <DaveB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:123435F7-6631-4C05-B5CD-CA50884DCB64@xxxxxxxxxxxxxxxx
I read your blog on the Service Master Key (SMK). One other question I have
is what is encrypted by the SMK? If I regenerate the key and/or force the
regeneration of the key, what data am I at risk of losing? I would assume
SQL
login passwords and other database master keys. Anything else? I am just
wondering what I may need to recreate if I need to regenerate the key.

"Laurentiu Cristofor [MSFT]" wrote:

Could be. Can you post the error from the errorlog, including a few lines
before and after it, for context? You can remove sensitive information
like
IP addresses or account names - I just need to see the error number,
state,
and message.

Thanks

--
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/

This posting is provided "AS IS" with no warranties, and confers no
rights.

"Dave B" <DaveB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:535415A4-4727-4652-82DC-401A3FD74D00@xxxxxxxxxxxxxxxx
I have a 2 node cluster that I recently installed. During the
installation,
node 2 was active. After the installation of SQL 2005 and the SP1, I
added
some linked servers that use SQL authentication. When I fail over to
node
1,
I get the following error:

An error occurred during decryption.

On all of my linked servers. If I fail back, everything works great. I
have
these same linked servers on several other non-clustered machines and
they
work fine. Is this possible a service master key issue?








.

Relevant Pages

  • Re: Linked Server Access Problems
    ... > Under SQL Server's Linked Servers, ... >>database on a SQL 2K box. ...
    (microsoft.public.sqlserver.security)
  • Linked Servers Fail
    ... error to a modal messagebox that the client provider ... >configured 6 linked servers using OpenLink Database Proxy ... I have had to cycle the SQL ... >the failure to the interaction between SQL and the DSN ...
    (microsoft.public.sqlserver.server)
  • Delete from Oracle table based on IDs in a SQL table
    ... Unfortunately we cannot use linked servers as the Oracle tables contain ... Two seperate SQL Tasks. ... second task dynamically by looping through the global variable. ...
    (microsoft.public.sqlserver.dts)
  • Re: An error occurred during decryption
    ... Software Development Engineer ... SQL Server Engine ... On all of my linked servers. ... If I fail back, everything works great. ...
    (microsoft.public.sqlserver.security)
  • Re: An error occurred during decryption
    ... The ALTER SERVICE MASTER KEY REGENERATE command worked. ... Software Development Engineer ... I am not clear of what you mean by linked servers and how do they ...
    (microsoft.public.sqlserver.security)