I have an active/active cluster running under SQL Server 2005 64 bit sp2.
After upgrading to build 3239 the SQL Server Agent won't start anymore... The
error captured in the log file is:

SQLServer Error: 22022, CryptUnprotectData() returned error -2146893813,
'Key not valid for use in specified state.' [SQLSTATE 42000]

And the log captured in the even log is:

The description for Event ID ( 17052 ) in Source ( MSSQLSERVER ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be able
to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
SQLServerAgent Monitor failed to restart SQLServerAgent after SQLServerAgent
terminated unexpectedly (reason: SQLSCMControl() returned error 5040, 'The
cluster node already exists.')..

Does anyone know how to resolve this?

Here is the KB article outlining the problem and two work-arounds
http://support.microsoft.com/kb/943525

BTW, the log entry is being analyzed from a maching that did not initially
create it, possibly from a different cluster node. The missing event
information is not the underlying error, it is simply a description when the
event data comes from a different system and the local one does not have the
same component to decode the event.


--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP


"RQ" <RQ (AT) discussions (DOT) microsoft.com> wrote

Here is the KB article outlining the problem and two work-arounds
http://support.microsoft.com/kb/943525

BTW, the log entry is being analyzed from a maching that did not initially
create it, possibly from a different cluster node. The missing event
information is not the underlying error, it is simply a description when the
event data comes from a different system and the local one does not have the
same component to decode the event.


--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP


"RQ" <RQ (AT) discussions (DOT) microsoft.com> wrote

Here is the KB article outlining the problem and two work-arounds
http://support.microsoft.com/kb/943525

BTW, the log entry is being analyzed from a maching that did not initially
create it, possibly from a different cluster node. The missing event
information is not the underlying error, it is simply a description when the
event data comes from a different system and the local one does not have the
same component to decode the event.


--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP


"RQ" <RQ (AT) discussions (DOT) microsoft.com> wrote

Here is the KB article outlining the problem and two work-arounds
http://support.microsoft.com/kb/943525

BTW, the log entry is being analyzed from a maching that did not initially
create it, possibly from a different cluster node. The missing event
information is not the underlying error, it is simply a description when the
event data comes from a different system and the local one does not have the
same component to decode the event.


--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP


"RQ" <RQ (AT) discussions (DOT) microsoft.com> wrote

Here is the KB article outlining the problem and two work-arounds
http://support.microsoft.com/kb/943525

BTW, the log entry is being analyzed from a maching that did not initially
create it, possibly from a different cluster node. The missing event
information is not the underlying error, it is simply a description when the
event data comes from a different system and the local one does not have the
same component to decode the event.


--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP


"RQ" <RQ (AT) discussions (DOT) microsoft.com> wrote

Here is the KB article outlining the problem and two work-arounds
http://support.microsoft.com/kb/943525

BTW, the log entry is being analyzed from a maching that did not initially
create it, possibly from a different cluster node. The missing event
information is not the underlying error, it is simply a description when the
event data comes from a different system and the local one does not have the
same component to decode the event.


--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP


"RQ" <RQ (AT) discussions (DOT) microsoft.com> wrote

Here is the KB article outlining the problem and two work-arounds
http://support.microsoft.com/kb/943525

BTW, the log entry is being analyzed from a maching that did not initially
create it, possibly from a different cluster node. The missing event
information is not the underlying error, it is simply a description when the
event data comes from a different system and the local one does not have the
same component to decode the event.


--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP


"RQ" <RQ (AT) discussions (DOT) microsoft.com> wrote

Here is the KB article outlining the problem and two work-arounds
http://support.microsoft.com/kb/943525

BTW, the log entry is being analyzed from a maching that did not initially
create it, possibly from a different cluster node. The missing event
information is not the underlying error, it is simply a description when the
event data comes from a different system and the local one does not have the
same component to decode the event.


--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP


"RQ" <RQ (AT) discussions (DOT) microsoft.com> wrote

Here is the KB article outlining the problem and two work-arounds
http://support.microsoft.com/kb/943525

BTW, the log entry is being analyzed from a maching that did not initially
create it, possibly from a different cluster node. The missing event
information is not the underlying error, it is simply a description when the
event data comes from a different system and the local one does not have the
same component to decode the event.


--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP


"RQ" <RQ (AT) discussions (DOT) microsoft.com> wrote