Renaming a SQL2005 - Unable to connect to RS from Management Studi

We have several 2005 boxes that have been renamed. RS works fine from a
browser and I can deplopy reports to it and see it with the config manager.
What I can't do is reference it from Management Studio. On the one box that
I restarted after sp_drop and sp_add, a message box pops up referring to the
old name. on the other box, niether the old name no the new name are found.
Where does the Studio get these names?For anyone who cares, I had to chnge the rsreportserver.config file. It was
referencing the old server names in the ulrroot section. This also impacted
the SAC tool's ability to manage the rs instance.
"Jeff Ericson" wrote:
> We have several 2005 boxes that have been renamed. RS works fine from a
> browser and I can deplopy reports to it and see it with the config manager.
> What I can't do is reference it from Management Studio. On the one box that
> I restarted after sp_drop and sp_add, a message box pops up referring to the
> old name. on the other box, niether the old name no the new name are found.
> Where does the Studio get these names?

Renamed RS Server; unable to access site

Good evening. I just renamed the server that hosts both SQL Server and Reporting Services. I am now unable to access the report manager website (http://localhost/reports). I receive an error stating "The underlying connection was closed: The remote name could not be resolved." As suggested by previous posts, I ran the rsconfig.exe utility specifying the new server name along with the security information. I am now able to access the report server (http://localhost/reportserver) and I can successfully run reports. I am still receiving the same error when attempting to access the report manager website, however. I have searched the registry and replaced the only instance of the old server name in a key pertaining to Reporting Services and rebooted, but I still have the same problem.
Please provide any information that will resolve this problem. Thanks in advance,
KevinIn your Report Manager directory, look for a RSWebApplication.config file. Open that baby up and look for something like:
<ReportServerUrl>http://Youroldservername/ReportServer</ReportServerUrl>
You might spot your old server name there. I've been playing with that file today, which sparked the idea. Not a clue if it works or not!
Hope it helps!
- T
"Kevin" wrote:
> Good evening. I just renamed the server that hosts both SQL Server and Reporting Services. I am now unable to access the report manager website (http://localhost/reports). I receive an error stating "The underlying connection was closed: The remote name could not be resolved." As suggested by previous posts, I ran the rsconfig.exe utility specifying the new server name along with the security information. I am now able to access the report server (http://localhost/reportserver) and I can successfully run reports. I am still receiving the same error when attempting to access the report manager website, however. I have searched the registry and replaced the only instance of the old server name in a key pertaining to Reporting Services and rebooted, but I still have the same problem.
> Please provide any information that will resolve this problem. Thanks in advance,
> Kevin
>|||You need to update the server URL in the file rswebapplication.config
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Kevin" <Kevin@.discussions.microsoft.com> wrote in message
news:09D00359-881C-41F5-9D16-BE40D5A4023A@.microsoft.com...
> Good evening. I just renamed the server that hosts both SQL Server and
Reporting Services. I am now unable to access the report manager website
(http://localhost/reports). I receive an error stating "The underlying
connection was closed: The remote name could not be resolved." As suggested
by previous posts, I ran the rsconfig.exe utility specifying the new server
name along with the security information. I am now able to access the
report server (http://localhost/reportserver) and I can successfully run
reports. I am still receiving the same error when attempting to access the
report manager website, however. I have searched the registry and replaced
the only instance of the old server name in a key pertaining to Reporting
Services and rebooted, but I still have the same problem.
> Please provide any information that will resolve this problem. Thanks in
advance,
> Kevin
>|||That did the trick. Thanks for all of your help!
Kevin
"Brian Hartman [MSFT]" wrote:
> You need to update the server URL in the file rswebapplication.config
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Kevin" <Kevin@.discussions.microsoft.com> wrote in message
> news:09D00359-881C-41F5-9D16-BE40D5A4023A@.microsoft.com...
> > Good evening. I just renamed the server that hosts both SQL Server and
> Reporting Services. I am now unable to access the report manager website
> (http://localhost/reports). I receive an error stating "The underlying
> connection was closed: The remote name could not be resolved." As suggested
> by previous posts, I ran the rsconfig.exe utility specifying the new server
> name along with the security information. I am now able to access the
> report server (http://localhost/reportserver) and I can successfully run
> reports. I am still receiving the same error when attempting to access the
> report manager website, however. I have searched the registry and replaced
> the only instance of the old server name in a key pertaining to Reporting
> Services and rebooted, but I still have the same problem.
> >
> > Please provide any information that will resolve this problem. Thanks in
> advance,
> > Kevin
> >
>
>|||We completed an installation of SQL Server 2000 Reporting Services and
upon trying to visit the server to publish or view the normal menu we
get only the following error:
-2147467259 (0x80004005)
The local user on the IIS server has access to the Report Database , I
can create a UDL and get a Connection Successful from the IIS box. But
I can't seem to get my normal startup page from any PC.
Thanks,
Teros wrote On 7/27/2004 4:25 PM:
> In your Report Manager directory, look for a RSWebApplication.config file. Open that baby up and look for something like:
> <ReportServerUrl>http://Youroldservername/ReportServer</ReportServerUrl>
> You might spot your old server name there. I've been playing with that file today, which sparked the idea. Not a clue if it works or not!
> Hope it helps!
> - T
>
> "Kevin" wrote:
>
>>Good evening. I just renamed the server that hosts both SQL Server and Reporting Services. I am now unable to access the report manager website (http://localhost/reports). I receive an error stating "The underlying connection was closed: The remote name could not be resolved." As suggested by previous posts, I ran the rsconfig.exe utility specifying the new server name along with the security information. I am now able to access the report server (http://localhost/reportserver) and I can successfully run reports. I am still receiving the same error when attempting to access the report manager website, however. I have searched the registry and replaced the only instance of the old server name in a key pertaining to Reporting Services and rebooted, but I still have the same problem.
>>Please provide any information that will resolve this problem. Thanks in advance,
>>Kevin