We recently upgraded our SQL Server installation to SQL Server 2005.  After
the upgrade we could not publish to Reporting Services, reconfiguring did
not help and ultimately it stopped responding.  It appeared that we had
multiple SSRS databases created when we tried to get it to work by
reconfiguring it, so we deleted the extraneous ones, at that point it
stopped working at all (reporting services database not found).

I reinstalled SSRS and carefully used the same database we used with SSRS
2000, the installation seemed to go well but SSRS still would not respond.
Initially after the reinstall I got a message that the reporting services
database was the wrong version, after some research I found where someone
had solved this problem by updating the reporting services database and did
that.  The error changed, but still SSRS is not working.

If I try to open 'Reports' (http://ServerName/Reports), I get this message
"The report server is not initialized (rsReportServer not activated)
(rsRPCError)".

If I try to open report manager (http://ServerName/ReportManager), I get
"page not found".  Looking at the web pages through IIS manager I see there
is a website called 'ReportServer', going to that page gives me the same
error as above; "The report server is not initialized (rsReportServer not
activated) (rsRPCError)".

When configuring SSRS with the configuration tool, everything has worked
(has the green icon) except for Sharepoint integration and Encryption keys
which has the blue icon indicating they are optional, and initialization
which is grayed out and cannot be selected.

Our environment;
Server is Windows Server 2003 SP2, clients are XP with Visual Studio 2005 as
the development environment, although in trying to get this to work I've
been using IE on the Server to try and get to Reporting services to
eliminate any possible network/permissions issues.  SQL Server uses
integrated security, SSRS identities are a domain user account which is a
local administrator on the server, except for the web service identity which
is "NT Authority\NetworkService".  The domain user account is the same one
SQL Server and Agent use.  The server is for internal use and we are behind
a firewall.  The database is on the same server as IIS/SSRS and is live so I
want to avoid impacting users unless I am sure I'm on the right track.  I
cannot find (and believe me I've looked) this information either on MSDN or
through google.  Usually what I find is other posts with similar problems
and no answers.

Questions;
Research indicates that I should reinstall SQL Server 05 SP2 after the
reinstall of SSRS, is this correct and could it be the cause of not being
able to initialize the server?

Since the previous install had SP2 and still did not work, what is the
likely cause of not being able to initialize the server, given that all
other steps have been gone through successfully (except for the two optional
steps indicated above)?

Any insight it welcome, since this has been the most problematic part of the
SQL Server 05 upgrade and is the only outstanding issue at this point - all
was working before the upgrade, we have some reports set up and could
publish from our workstations.

Thanks in advance,

David Craig.