Wednesday, March 19, 2008

Reporting Services - Unable to Connect to Remote Server Error

After a restart reporting services, you may come up with Unable to Connect to Remote Server Error when navigating to the web access. Typically an issue like this occurs in the RSWebApplication.config. This file is located in the ReportManager Folder (Example: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager) I checked the <reportserverurl> and <reportservervirtualdirectory> tags were the same as before.

<ReportServerUrl></ReportServerUrl>
<ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>


After changing the ReportServerUrl tag to contain both the server URL and the virtual directory, it could then connect to the remote server.

<ReportServerUrl>http://Server/ReportServer/</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>

No IP addresses were added or was any IIS settings that I could tell. Leaving the ReportServerUrl tag blank should allow for it to find the server locally.

6 comments:

Anonymous said...

Thank you ever so much!

I've been searching Microsoft's forums and other resources and had not been able to get this working right until I found your blog on a google search.

Anonymous said...

Hello there,

I am having the SAME issue when deploying a .rdl and .rds to http://localhost/reportserver, it showed the error: Unable to connect to Remote server".

I am using Win 2003 Standard with sp2, SQL Server 2008 with sp1 and VS 2008.

Please kindly provide your suggestion on this site so that I could come back to view.

Many thanks!

Have a happy New Year of 2010!

Anonymous said...

Hello there,

I am having the SAME issue when deploying a .rdl and .rds to http://localhost/reportserver, it showed the error: Unable to connect to Remote server".

I am using Win 2003 Standard with sp2, SQL Server 2008 with sp1 and VS 2008.

Please kindly provide your suggestion on this site so that I could come back to view.

Many thanks!

Have a happy New Year of 2010!

Anonymous said...

I fixed it as:

change the SecureConnectionLevel to 0 and it works.

Anonymous said...

Thank you, your save my life :D

Naat said...

Aftеr lооkіng аt а numbеr оf thе аrtісlеѕ оn уоur blоg, I rеаllу lіkе уоur wау оf wrіtіng а blоg. I ѕаvеd іt tо mу bооkmаrk ѕіtе lіѕt аnd wіll bе сhесkіng bасk ѕооn. Plеаѕе vіѕіt mу wеbѕіtе аѕ wеll аnd tеll mе whаt уоu thіnk.