"key not valid for use in the specified state"

I upgraded to Windows 2003 SP1, and now I keep getting the message: "Key not
valid for use in the specified state" on any page of the Report Manager that
I try to access.
I've tried deleting and recreating the keys with no success. The search that
I've done in the MS Site have all pointed me to EFS errors. Anybody have any
ideas where I should go next?
Thanks.
DerrickI had that problem 6 months ago. After opening a support call with MS
and after many attempts to fix it, in the end the only process that
worked was to completely erase all traces of RS from the system and then
do a fresh install. Below is a list of the steps to take (note
especially step 5 - this was the deciding factor for me on the reinstall
fixing the problem)
1. Backup your existing solution files, such as .sln, .rdl, .rds files.
2. If the machine is a domain controller, do not install Reporting
Service on it. Use another machine instead.
3. Run Setup.exe of the SQL Server 2000 Reporting Services to launch the
Setup window.
4. Click "Remove Microsoft SQL Server 2000 Reporting Service" button in
the Setup window.
5. From Explorer, navigate to x:\Documents and Settings\<service
account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20 and delete all
files located in this folder.
6. Delete all Reporting services related files under this folder
"x:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services" if present
7. Delete all Reporting Services Virtual Directories (ReportServer and
Reports) from IIS Manager if present.
8. Delete all Reporting Services Databases (ReportServer and
ReportServerTempDB) from SQL Server Enterprise Manager if present.
9. Re-boot the machine and log on using an Administrators group account.
10. Reinstall SQL Server 2000 Reporting Service on the machine.
brian smith
Derrick Powell wrote:
> I upgraded to Windows 2003 SP1, and now I keep getting the message: "Key not
> valid for use in the specified state" on any page of the Report Manager that
> I try to access.
> I've tried deleting and recreating the keys with no success. The search that
> I've done in the MS Site have all pointed me to EFS errors. Anybody have any
> ideas where I should go next?
> Thanks.
> Derrick
>

"downgrading" 2005 to 2000

Hello:
It's a long story, as to why we ask this. But, here it goes.
About a week ago, we upgraded a Windows Server 2003 box from SQL 2000 to SQL
2005 service pack 2. Is it possible to go back to SQL 2000? Restoring a
backup is not an option.
We conducted this upgrade by installing a new instance of SQL 2005 and
re-attaching the 2000 databases. We did not conduct this install through th
e
"regular" means of putting the CD in and saying "Next, Next..."
Thanks!
childofthe1980s"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:23DAD4E3-2D4D-4CD3-90B3-176744F0777D@.microsoft.com...
> Hello:
> It's a long story, as to why we ask this. But, here it goes.
> About a week ago, we upgraded a Windows Server 2003 box from SQL 2000 to
> SQL
> 2005 service pack 2. Is it possible to go back to SQL 2000? Restoring a
> backup is not an option.
> We conducted this upgrade by installing a new instance of SQL 2005 and
> re-attaching the 2000 databases. We did not conduct this install through
> the
> "regular" means of putting the CD in and saying "Next, Next..."
> Thanks!
> childofthe1980s
You can't downgrade a database. You could script/recreate the 2000 database
and then populate it from the 2005 version (using BCP, DTS or INSERT
statements for example).
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

"downgrading" 2005 to 2000

Hello:
It's a long story, as to why we ask this. But, here it goes.
About a week ago, we upgraded a Windows Server 2003 box from SQL 2000 to SQL
2005 service pack 2. Is it possible to go back to SQL 2000? Restoring a
backup is not an option.
We conducted this upgrade by installing a new instance of SQL 2005 and
re-attaching the 2000 databases. We did not conduct this install through the
"regular" means of putting the CD in and saying "Next, Next..."
Thanks!
childofthe1980s"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:23DAD4E3-2D4D-4CD3-90B3-176744F0777D@.microsoft.com...
> Hello:
> It's a long story, as to why we ask this. But, here it goes.
> About a week ago, we upgraded a Windows Server 2003 box from SQL 2000 to
> SQL
> 2005 service pack 2. Is it possible to go back to SQL 2000? Restoring a
> backup is not an option.
> We conducted this upgrade by installing a new instance of SQL 2005 and
> re-attaching the 2000 databases. We did not conduct this install through
> the
> "regular" means of putting the CD in and saying "Next, Next..."
> Thanks!
> childofthe1980s
You can't downgrade a database. You could script/recreate the 2000 database
and then populate it from the 2005 version (using BCP, DTS or INSERT
statements for example).
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--