Can't get Reporting Services working after reinstall

I had to make room on the system partition so I uninstalled SQL 2005 Ent. and reinstalled it in a different partition, which is mounted in c:\apps. Since doing this, although MSSQL works fine, RS does not respond. During the reinstall, Setup reported that RS was "installed but not configured". I ran the RS Configuration Mgr and went through the config sequence. However, on the Initialization page, which has a red 'x' in the left panel, the local server is not listed -- the grid is empty.

The RS service is running, using the same credentials as MSSQL, the admin account .\SQLExec. It logs a normal startup in the Event Log. However, on visiting http://localhost/Reports, I get a message saying that Reporting Services is not responding. SP2 installed OK on the system, and reported that all components were upgraded.

How can I debug this installation?

Check for any other information on windows event log.

Also check under the services whether thye have been started successfully.

|||MSSQL, SSRS, SQL Agent, and IIS are running. I did see some interesting messages in the Application Log:
__
EventID 18456: "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'." from MSSQL

EventID 107: "Report Server (MSSQLSERVER) cannot connect to the report server database." From Reporting Svcs.
__

I check in SQL Mgt. Studio: 'NT Authority\Network Service' is set up as a SQL login. The account is in the dbo and RSExecRole roles in the ReportServer database. In the RS Config Mgr, this account is shown as the ASP.NET Service account. The Report Server and Report Manager are both set to "Default Application Pool".

sp_who shows that the 'NT Authority\Network Service' login IS connected to the ReportServer database, along with two other connections to this db from the SQL Service account, .\SQLExec, which is used by all SQL-related services.

When I visit http://localhost/Reports, I now get the message: "Key not valid for use in specified state.

(Exception from HRESULT: 0x8009000B) (rsRPCError)". What does this mean?

One thing I recall seeing when I created the ReportServer database in the RS Configuration Mgr was a warning (yellow '!') saying it was "unable to access internal information" about the installation to verify the connection. Is this a clue?

Any advice how to proceed?|||Further searching revealed this may have to do with a crypto key left over from the prior installation, found under "C:\Documents and Settings\SQLExec\Application

Data\Microsoft\Crypto\RSA" in a file matching "1aedd7b5699f3d6a88e354100b596aae*" Advice was to delete this file and recreate it using the 'rsactivate' utility, which I cannot find. The discussion I found pertained to SSRS 2000 and not in 2005.

What's the correct way to fix this problem in Reporting Services 2005?|||Deleting the 1aedd* key file corrected the problem. I uninstalled SSRS, deleted the old RS databases, deleted the key file, reinstalled SSRS, reapplied SP2. After doing this, each step in the Reporting Svcs Config Mgr then worked correctly.

I would rate this as a serious problem with either SQL Setup or the RS Config Mgr if neither can diagnose nor correct the problem. If I hadn't stumbled across mention of the 1aedd* file on someone's blog I would not have been able to get Reporting Services to work following the reinstallation of MSSQL and its components.