Key not valid for use in specified state

Hi!
On thursday last week one of our clients Reporting Services installation
stopped working and reports "Key not valid for use in specified state" error
message in the log files.
This is strange as we have not done any changes to the server. It is running
Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
Anyone got similar problems or know what could cause this behaviour?
I have tried reinstalling the encryption keys and finally removing and
reinstalling the complete Reporting Services but the same error is logged
and the service doesn't work.
Best regards,
Per SalmiI am getting exactly the same problem, also in Win2k3, and have also done a
complete uninstall and reinstall of RS, to no avail.
Surely someone in Microsoft can resolve this'? I have had to abandon work
because of this error.
brian smith
"Per Salmi" <per.salmi@.nospam.nospam> wrote in message
news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> Hi!
> On thursday last week one of our clients Reporting Services installation
> stopped working and reports "Key not valid for use in specified state"
error
> message in the log files.
> This is strange as we have not done any changes to the server. It is
running
> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
> Anyone got similar problems or know what could cause this behaviour?
> I have tried reinstalling the encryption keys and finally removing and
> reinstalling the complete Reporting Services but the same error is logged
> and the service doesn't work.
> Best regards,
> Per Salmi
>|||I have found one thing that differs between two servers we have one where RS
works perfectly and the one mentioned with the "key problem". The difference
is that the server that doesn't work has an SQL instance that was upgraded
from SQL7 but the one that works is running on a clean installed SQL2K
instance.
The OS is W2K3 on both servers.
On the one that now suffers from the problem I also had problems where the
Report Manager web application would not install/configure correctly during
install. Never got the manager to work so I used another machine for the web
application.
/Per Salmi
"Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
>I am getting exactly the same problem, also in Win2k3, and have also done a
> complete uninstall and reinstall of RS, to no avail.
> Surely someone in Microsoft can resolve this'? I have had to abandon
> work
> because of this error.
> brian smith
> "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
>> Hi!
>> On thursday last week one of our clients Reporting Services installation
>> stopped working and reports "Key not valid for use in specified state"
> error
>> message in the log files.
>> This is strange as we have not done any changes to the server. It is
> running
>> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
>> Anyone got similar problems or know what could cause this behaviour?
>> I have tried reinstalling the encryption keys and finally removing and
>> reinstalling the complete Reporting Services but the same error is logged
>> and the service doesn't work.
>> Best regards,
>> Per Salmi
>>
>|||I don't think the SQL7 upgrade is relevant - my server was a clean install
with SQL 2000. I have followed 2 possible causes on my system:
1 - the .Net Framework 1.1 SP1 update (although RS did continue for a week
or so)
2 - the fact that I originally installed the 120 day trial version of RS,
before updating it a few weeks later.
After a clean removal, including the databases, and reinstall, plus RS SP1
I'm no better off. This looks like a bug, which worries me greatly as I have
customers dependant on the product and I fear this error will suddenly occur
on their system too.
Brian
"Per Salmi" <per.salmi@.nospam.nospam> wrote in message
news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
> I have found one thing that differs between two servers we have one where
RS
> works perfectly and the one mentioned with the "key problem". The
difference
> is that the server that doesn't work has an SQL instance that was upgraded
> from SQL7 but the one that works is running on a clean installed SQL2K
> instance.
> The OS is W2K3 on both servers.
> On the one that now suffers from the problem I also had problems where the
> Report Manager web application would not install/configure correctly
during
> install. Never got the manager to work so I used another machine for the
web
> application.
> /Per Salmi
> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
> >I am getting exactly the same problem, also in Win2k3, and have also done
a
> > complete uninstall and reinstall of RS, to no avail.
> > Surely someone in Microsoft can resolve this'? I have had to abandon
> > work
> > because of this error.
> >
> > brian smith
> >
> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> >> Hi!
> >>
> >> On thursday last week one of our clients Reporting Services
installation
> >> stopped working and reports "Key not valid for use in specified state"
> > error
> >> message in the log files.
> >>
> >> This is strange as we have not done any changes to the server. It is
> > running
> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
> >>
> >> Anyone got similar problems or know what could cause this behaviour?
> >>
> >> I have tried reinstalling the encryption keys and finally removing and
> >> reinstalling the complete Reporting Services but the same error is
logged
> >> and the service doesn't work.
> >>
> >> Best regards,
> >> Per Salmi
> >>
> >>
> >
> >
>|||To follow on from my earlier messaege - the error appears to relate to
something to do with encryption. I know nothing about encryption, or why it
is involved in RS, but I assume it involves licensing.
These are lines in the RS log:
aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Initializing crypto as
user: DRAKE\ASPNET
aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Exporting public key
aspnet_wp!webserver!cfc!09/24/2004-13:08:28:: e ERROR: Internal error:
System.Runtime.InteropServices.COMException (0x8009000B): Key not valid for
use in specified state.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
errorCode, IntPtr errorInfo)
at RSManagedCrypto.RSCrypto.ExportPublicKey()
at
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
Brian
"Per Salmi" <per.salmi@.nospam.nospam> wrote in message
news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
> I have found one thing that differs between two servers we have one where
RS
> works perfectly and the one mentioned with the "key problem". The
difference
> is that the server that doesn't work has an SQL instance that was upgraded
> from SQL7 but the one that works is running on a clean installed SQL2K
> instance.
> The OS is W2K3 on both servers.
> On the one that now suffers from the problem I also had problems where the
> Report Manager web application would not install/configure correctly
during
> install. Never got the manager to work so I used another machine for the
web
> application.
> /Per Salmi
> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
> >I am getting exactly the same problem, also in Win2k3, and have also done
a
> > complete uninstall and reinstall of RS, to no avail.
> > Surely someone in Microsoft can resolve this'? I have had to abandon
> > work
> > because of this error.
> >
> > brian smith
> >
> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> >> Hi!
> >>
> >> On thursday last week one of our clients Reporting Services
installation
> >> stopped working and reports "Key not valid for use in specified state"
> > error
> >> message in the log files.
> >>
> >> This is strange as we have not done any changes to the server. It is
> > running
> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
> >>
> >> Anyone got similar problems or know what could cause this behaviour?
> >>
> >> I have tried reinstalling the encryption keys and finally removing and
> >> reinstalling the complete Reporting Services but the same error is
logged
> >> and the service doesn't work.
> >>
> >> Best regards,
> >> Per Salmi
> >>
> >>
> >
> >
>|||Ok, I did never install any evaluation version of RS on this server. This
actually happened on aserver used in full production. But I moved the
reporting stuff to the other server. I am afraid that it will break on that
server too.
/Per Salmi
"Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
news:%237KuxYjoEHA.2912@.TK2MSFTNGP10.phx.gbl...
>I don't think the SQL7 upgrade is relevant - my server was a clean install
> with SQL 2000. I have followed 2 possible causes on my system:
> 1 - the .Net Framework 1.1 SP1 update (although RS did continue for a week
> or so)
> 2 - the fact that I originally installed the 120 day trial version of RS,
> before updating it a few weeks later.
> After a clean removal, including the databases, and reinstall, plus RS SP1
> I'm no better off. This looks like a bug, which worries me greatly as I
> have
> customers dependant on the product and I fear this error will suddenly
> occur
> on their system too.
> Brian
> "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
>> I have found one thing that differs between two servers we have one where
> RS
>> works perfectly and the one mentioned with the "key problem". The
> difference
>> is that the server that doesn't work has an SQL instance that was
>> upgraded
>> from SQL7 but the one that works is running on a clean installed SQL2K
>> instance.
>> The OS is W2K3 on both servers.
>> On the one that now suffers from the problem I also had problems where
>> the
>> Report Manager web application would not install/configure correctly
> during
>> install. Never got the manager to work so I used another machine for the
> web
>> application.
>> /Per Salmi
>> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
>> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
>> >I am getting exactly the same problem, also in Win2k3, and have also
>> >done
> a
>> > complete uninstall and reinstall of RS, to no avail.
>> > Surely someone in Microsoft can resolve this'? I have had to abandon
>> > work
>> > because of this error.
>> >
>> > brian smith
>> >
>> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
>> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
>> >> Hi!
>> >>
>> >> On thursday last week one of our clients Reporting Services
> installation
>> >> stopped working and reports "Key not valid for use in specified state"
>> > error
>> >> message in the log files.
>> >>
>> >> This is strange as we have not done any changes to the server. It is
>> > running
>> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
>> >>
>> >> Anyone got similar problems or know what could cause this behaviour?
>> >>
>> >> I have tried reinstalling the encryption keys and finally removing and
>> >> reinstalling the complete Reporting Services but the same error is
> logged
>> >> and the service doesn't work.
>> >>
>> >> Best regards,
>> >> Per Salmi
>> >>
>> >>
>> >
>> >
>>
>|||Seems like exactly the same error I get.
/Per Salmi
"Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
news:eIYFOhjoEHA.3424@.TK2MSFTNGP12.phx.gbl...
> To follow on from my earlier messaege - the error appears to relate to
> something to do with encryption. I know nothing about encryption, or why
> it
> is involved in RS, but I assume it involves licensing.
> These are lines in the RS log:
> aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Initializing crypto as
> user: DRAKE\ASPNET
> aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Exporting public key
> aspnet_wp!webserver!cfc!09/24/2004-13:08:28:: e ERROR: Internal error:
> System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> for
> use in specified state.
> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> errorCode, IntPtr errorInfo)
> at RSManagedCrypto.RSCrypto.ExportPublicKey()
> at
> Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
>
> Brian
> "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
>> I have found one thing that differs between two servers we have one where
> RS
>> works perfectly and the one mentioned with the "key problem". The
> difference
>> is that the server that doesn't work has an SQL instance that was
>> upgraded
>> from SQL7 but the one that works is running on a clean installed SQL2K
>> instance.
>> The OS is W2K3 on both servers.
>> On the one that now suffers from the problem I also had problems where
>> the
>> Report Manager web application would not install/configure correctly
> during
>> install. Never got the manager to work so I used another machine for the
> web
>> application.
>> /Per Salmi
>> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
>> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
>> >I am getting exactly the same problem, also in Win2k3, and have also
>> >done
> a
>> > complete uninstall and reinstall of RS, to no avail.
>> > Surely someone in Microsoft can resolve this'? I have had to abandon
>> > work
>> > because of this error.
>> >
>> > brian smith
>> >
>> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
>> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
>> >> Hi!
>> >>
>> >> On thursday last week one of our clients Reporting Services
> installation
>> >> stopped working and reports "Key not valid for use in specified state"
>> > error
>> >> message in the log files.
>> >>
>> >> This is strange as we have not done any changes to the server. It is
>> > running
>> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
>> >>
>> >> Anyone got similar problems or know what could cause this behaviour?
>> >>
>> >> I have tried reinstalling the encryption keys and finally removing and
>> >> reinstalling the complete Reporting Services but the same error is
> logged
>> >> and the service doesn't work.
>> >>
>> >> Best regards,
>> >> Per Salmi
>> >>
>> >>
>> >
>> >
>>
>|||Actually I find that the .NET FW 1.1 SP1 is not installed on the server
where RS continues to work...
/Per Salmi
"Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
news:%237KuxYjoEHA.2912@.TK2MSFTNGP10.phx.gbl...
>I don't think the SQL7 upgrade is relevant - my server was a clean install
> with SQL 2000. I have followed 2 possible causes on my system:
> 1 - the .Net Framework 1.1 SP1 update (although RS did continue for a week
> or so)
> 2 - the fact that I originally installed the 120 day trial version of RS,
> before updating it a few weeks later.
> After a clean removal, including the databases, and reinstall, plus RS SP1
> I'm no better off. This looks like a bug, which worries me greatly as I
> have
> customers dependant on the product and I fear this error will suddenly
> occur
> on their system too.
> Brian
> "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
>> I have found one thing that differs between two servers we have one where
> RS
>> works perfectly and the one mentioned with the "key problem". The
> difference
>> is that the server that doesn't work has an SQL instance that was
>> upgraded
>> from SQL7 but the one that works is running on a clean installed SQL2K
>> instance.
>> The OS is W2K3 on both servers.
>> On the one that now suffers from the problem I also had problems where
>> the
>> Report Manager web application would not install/configure correctly
> during
>> install. Never got the manager to work so I used another machine for the
> web
>> application.
>> /Per Salmi
>> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
>> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
>> >I am getting exactly the same problem, also in Win2k3, and have also
>> >done
> a
>> > complete uninstall and reinstall of RS, to no avail.
>> > Surely someone in Microsoft can resolve this'? I have had to abandon
>> > work
>> > because of this error.
>> >
>> > brian smith
>> >
>> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
>> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
>> >> Hi!
>> >>
>> >> On thursday last week one of our clients Reporting Services
> installation
>> >> stopped working and reports "Key not valid for use in specified state"
>> > error
>> >> message in the log files.
>> >>
>> >> This is strange as we have not done any changes to the server. It is
>> > running
>> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
>> >>
>> >> Anyone got similar problems or know what could cause this behaviour?
>> >>
>> >> I have tried reinstalling the encryption keys and finally removing and
>> >> reinstalling the complete Reporting Services but the same error is
> logged
>> >> and the service doesn't work.
>> >>
>> >> Best regards,
>> >> Per Salmi
>> >>
>> >>
>> >
>> >
>>
>|||Has anyone found the actual cause of this error? I do not want to
have to re-install RServices on a regular basis.
"Per Salmi" <per.salmi@.nospam.nospam> wrote in message news:<eU5aTJkoEHA.1664@.tk2msftngp13.phx.gbl>...
> Seems like exactly the same error I get.
> /Per Salmi
> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
> news:eIYFOhjoEHA.3424@.TK2MSFTNGP12.phx.gbl...
> > To follow on from my earlier messaege - the error appears to relate to
> > something to do with encryption. I know nothing about encryption, or why
> > it
> > is involved in RS, but I assume it involves licensing.
> >
> > These are lines in the RS log:
> > aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Initializing crypto as
> > user: DRAKE\ASPNET
> > aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Exporting public key
> > aspnet_wp!webserver!cfc!09/24/2004-13:08:28:: e ERROR: Internal error:
> > System.Runtime.InteropServices.COMException (0x8009000B): Key not valid
> > for
> > use in specified state.
> > at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> > errorCode, IntPtr errorInfo)
> > at RSManagedCrypto.RSCrypto.ExportPublicKey()
> > at
> > Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> >
> >
> > Brian
> >
> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> > news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
> >> I have found one thing that differs between two servers we have one where
> RS
> >> works perfectly and the one mentioned with the "key problem". The
> difference
> >> is that the server that doesn't work has an SQL instance that was
> >> upgraded
> >> from SQL7 but the one that works is running on a clean installed SQL2K
> >> instance.
> >>
> >> The OS is W2K3 on both servers.
> >>
> >> On the one that now suffers from the problem I also had problems where
> >> the
> >> Report Manager web application would not install/configure correctly
> during
> >> install. Never got the manager to work so I used another machine for the
> web
> >> application.
> >>
> >> /Per Salmi
> >>
> >> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
> >> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
> >> >I am getting exactly the same problem, also in Win2k3, and have also
> >> >done
> a
> >> > complete uninstall and reinstall of RS, to no avail.
> >> > Surely someone in Microsoft can resolve this'? I have had to abandon
> >> > work
> >> > because of this error.
> >> >
> >> > brian smith
> >> >
> >> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> >> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> >> >> Hi!
> >> >>
> >> >> On thursday last week one of our clients Reporting Services
> installation
> >> >> stopped working and reports "Key not valid for use in specified state"
> error
> >> >> message in the log files.
> >> >>
> >> >> This is strange as we have not done any changes to the server. It is
> running
> >> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
> >> >>
> >> >> Anyone got similar problems or know what could cause this behaviour?
> >> >>
> >> >> I have tried reinstalling the encryption keys and finally removing and
> >> >> reinstalling the complete Reporting Services but the same error is
> logged
> >> >> and the service doesn't work.
> >> >>
> >> >> Best regards,
> >> >> Per Salmi
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >|||I have an ongoing (paid) support case with MS, but so far despite all the
suggestions, my RS still does not work. When (and if) they fix it, I'll post
an update.
brian
"Austin S" <austinswope@.gmail.com> wrote in message
news:b68c96f7.0410180951.57c3121e@.posting.google.com...
> Has anyone found the actual cause of this error? I do not want to
> have to re-install RServices on a regular basis.
>
> "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
news:<eU5aTJkoEHA.1664@.tk2msftngp13.phx.gbl>...
> > Seems like exactly the same error I get.
> >
> > /Per Salmi
> >
> > "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
> > news:eIYFOhjoEHA.3424@.TK2MSFTNGP12.phx.gbl...
> > > To follow on from my earlier messaege - the error appears to relate to
> > > something to do with encryption. I know nothing about encryption, or
why
> > > it
> > > is involved in RS, but I assume it involves licensing.
> > >
> > > These are lines in the RS log:
> > > aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Initializing crypto
as
> > > user: DRAKE\ASPNET
> > > aspnet_wp!crypto!cfc!09/24/2004-13:08:27:: i INFO: Exporting public
key
> > > aspnet_wp!webserver!cfc!09/24/2004-13:08:28:: e ERROR: Internal error:
> > > System.Runtime.InteropServices.COMException (0x8009000B): Key not
valid
> > > for
> > > use in specified state.
> > > at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> > > errorCode, IntPtr errorInfo)
> > > at RSManagedCrypto.RSCrypto.ExportPublicKey()
> > > at
> > >
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> > >
> > >
> > > Brian
> > >
> > > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> > > news:eDXedHjoEHA.2380@.TK2MSFTNGP14.phx.gbl...
> > >> I have found one thing that differs between two servers we have one
where
> > RS
> > >> works perfectly and the one mentioned with the "key problem". The
> > difference
> > >> is that the server that doesn't work has an SQL instance that was
> > >> upgraded
> > >> from SQL7 but the one that works is running on a clean installed
SQL2K
> > >> instance.
> > >>
> > >> The OS is W2K3 on both servers.
> > >>
> > >> On the one that now suffers from the problem I also had problems
where
> > >> the
> > >> Report Manager web application would not install/configure correctly
> > during
> > >> install. Never got the manager to work so I used another machine for
the
> > web
> > >> application.
> > >>
> > >> /Per Salmi
> > >>
> > >> "Brian Smith" <bsmith@.no_spam.schemiotics.co.uk> skrev i meddelandet
> > >> news:ezlcI$ioEHA.1300@.TK2MSFTNGP12.phx.gbl...
> > >> >I am getting exactly the same problem, also in Win2k3, and have also
> > >> >done
> > a
> > >> > complete uninstall and reinstall of RS, to no avail.
> > >> > Surely someone in Microsoft can resolve this'? I have had to
abandon
> > >> > work
> > >> > because of this error.
> > >> >
> > >> > brian smith
> > >> >
> > >> > "Per Salmi" <per.salmi@.nospam.nospam> wrote in message
> > >> > news:OOi$DPhoEHA.1800@.TK2MSFTNGP15.phx.gbl...
> > >> >> Hi!
> > >> >>
> > >> >> On thursday last week one of our clients Reporting Services
> > installation
> > >> >> stopped working and reports "Key not valid for use in specified
state"
> > error
> > >> >> message in the log files.
> > >> >>
> > >> >> This is strange as we have not done any changes to the server. It
is
> > running
> > >> >> Windows Server 2003 Standard Editon with SQL Server 2000 Std Ed...
> > >> >>
> > >> >> Anyone got similar problems or know what could cause this
behaviour?
> > >> >>
> > >> >> I have tried reinstalling the encryption keys and finally removing
and
> > >> >> reinstalling the complete Reporting Services but the same error is
> > logged
> > >> >> and the service doesn't work.
> > >> >>
> > >> >> Best regards,
> > >> >> Per Salmi
> > >> >>
> > >> >>
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >|||I'd love to hear the solution too - I just ran into this exact error after
.Net Framework 1.1 SP1 was installed over the weekend.
I've tried the other solutions in these threads, but nothing has worked.
Dave
"Brian Smith" wrote:
> I have an ongoing (paid) support case with MS, but so far despite all the
> suggestions, my RS still does not work. When (and if) they fix it, I'll post
> an update.
> brian
>