Reporting Services affected by a server name change?

We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
operating system. We had Reporting Services installed and configured but we
did not use it. A couple of weeks ago the server name was changed. I ran
sp_dropserver and then sp_addserver.
Since then our client want to utilize Reporting Services. Although
configured it is not working. I cannot even access Reporting Services
through SQL Server Management Studio. Could this be the result of the server
name change? What should be done with Reporting Services in the event of a
server name change?
Go to RS Config Manager (Start Menu\Programs\Microsoft SQL Server
2005\Configuration Tools)
-Database Setup:
-Change the name in the "Server Name" field to your server's new name
-Click on "Connect"
-Click on "Apply"
-Encryption keys
-Click on "Delete" and Ok (deleting this can give you problems on an
active production server)
-Open the file C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\rsreportserver.config
and change the line
<UrlRoot>http://OldServerName/reportserver</UrlRoot>
to
<UrlRoot>http://NewServerName/reportserver</UrlRoot>
-In MSIE, check the following addresses:
http://localhost/reports
http://localhost/reportserver
-Try to connect to Reporting Services through Management Studio
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Loren Z" <anonymous@.discussions.microsoft.com> wrote in message
news:e$M4P4ThIHA.2268@.TK2MSFTNGP02.phx.gbl...
> We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
> operating system. We had Reporting Services installed and configured but
> we did not use it. A couple of weeks ago the server name was changed. I
> ran sp_dropserver and then sp_addserver.
> Since then our client want to utilize Reporting Services. Although
> configured it is not working. I cannot even access Reporting Services
> through SQL Server Management Studio. Could this be the result of the
> server name change? What should be done with Reporting Services in the
> event of a server name change?
>