Report Server not found at http://localhost/ReportServer

Hi,
I have installed Developer editio of reporting svcs on my webserver. Our SQL
server 2000 (developer edition) is on a separate database server. Now I have
created a simple report but when i try to deploy the report the report... i
get the error Report Server not found at http://localhost/ReportServer.. Is
it because my database is on a different server?
--
pmudpmud wrote:
> Hi,
> I have installed Developer editio of reporting svcs on my webserver.
> Our SQL server 2000 (developer edition) is on a separate database
> server. Now I have created a simple report but when i try to deploy
> the report the report... i get the error Report Server not found at
> http://localhost/ReportServer.. Is it because my database is on a
> different server?
Is your web server the same machine as your development machine? The
URL you gave would indicate that, but from your description it sounds
like the web server may be on a different box, NOT your development
machine.
In VStudio 2003, right-click on your report project in Solution
Explorer (usually at the top righthand corner of the dev environment).
Make sure that the TargetServerURL property points to your web server
where Reporting Services is. For example, if your web/reporting server
is named pmudweb, TargetServerURL should be http://pmudweb/ReportServer
.
So, it may be because your reporting server is on another machine, not
because the database server is on another machine.
hth
Highly Obscure|||Hi Highly Obscure,
I tried that and it works but i get a different error now i.e "The
underlying connection was closed.could not establish trust relationship with
remote server."
I think it is something related with SSL... I am reading a Microsoft article
right now at http://support.microsoft.com/?scid=kb;en-us;823177 . If you
have any inputs, please let me know.
Thanks
"Highly Obscure" wrote:
> pmud wrote:
> > Hi,
> >
> > I have installed Developer editio of reporting svcs on my webserver.
> > Our SQL server 2000 (developer edition) is on a separate database
> > server. Now I have created a simple report but when i try to deploy
> > the report the report... i get the error Report Server not found at
> > http://localhost/ReportServer.. Is it because my database is on a
> > different server?
> Is your web server the same machine as your development machine? The
> URL you gave would indicate that, but from your description it sounds
> like the web server may be on a different box, NOT your development
> machine.
> In VStudio 2003, right-click on your report project in Solution
> Explorer (usually at the top righthand corner of the dev environment).
> Make sure that the TargetServerURL property points to your web server
> where Reporting Services is. For example, if your web/reporting server
> is named pmudweb, TargetServerURL should be http://pmudweb/ReportServer
> ..
> So, it may be because your reporting server is on another machine, not
> because the database server is on another machine.
> hth
> Highly Obscure
>|||We got this behavior when we used a certificate that didn't chain up to
a "real" root certificate. In our case we installed Certificate
Services as enterprise root on a domain controller in a different
domain from the report server, then requested a certificate from this
CA and installed it on the report server. No matter what we tried (and
of course we installed the Web server certificate in Internet Explorer
on the client), we could not get SSL working reliably on the report
server, with various symptoms, one of which was the error you cite.
In the end, since this was in the development environment, we ended up
using SelfSSL, available from Microsoft at
http://www.microsoft.com/windowsserver2003/iis/downloads/default.mspx .
It's a lot better than makecert. You can also download an SSL
diagnostic utility from the link given above, very helpful.
now that's
Highly Obscure
pmud wrote:
> Hi Highly Obscure,
> I tried that and it works but i get a different error now i.e "The
> underlying connection was closed.could not establish trust
> relationship with remote server."
> I think it is something related with SSL... I am reading a Microsoft
> article right now at
> http://support.microsoft.com/?scid=kb;en-us;823177 . If you have any
> inputs, please let me know.
> Thanks
>|||Hi Highly Obscure,
I tried a couple of things since yesterday and my my real problem is as
follows. Please suggest that with the problem I have , will it be a good idea
to download the Self SSL as suugested by you.
PROBLEM::
I have installed Reporting Services and enabled SSL. The Reporting Svcss by
default was installed in the "Dealer.com" which was originally the Default
Website . Now we created another site with properties same as the Defult Web
site and called it Default Website and created virtual directories "Reports"
and "ReportServer" in this new Default Web site.
Now the problem is that when I deploy the reports , I get an error alert
message saying " A connection could not be made to the report server at
https://report.com/ReportServer . " When I close this message I get an error
in the Task List oh VS.Net as " The underlying connection was closed. Could
not establish trust relationship with the server."
I have already changed the 2 config files to use the URL
https://report.com/ReportServer and the project property of traget URL is
also set to the same. Also, the SSL Sercure Key Connection Value is set to 2.
I am able to browse from IE to https://report.com/ReportServer but not to
the report manager at https://report.com/reports .Also, MY MAIN PROBLEM IS
THAT I CANT DEPLOY THE REPORTS..
Also, our SQL database is on a different server and reporting services is on
the webserver.
Sjpuld I download the SelfSSl for this paroblem'
Thanks
"Highly Obscure" wrote:
> We got this behavior when we used a certificate that didn't chain up to
> a "real" root certificate. In our case we installed Certificate
> Services as enterprise root on a domain controller in a different
> domain from the report server, then requested a certificate from this
> CA and installed it on the report server. No matter what we tried (and
> of course we installed the Web server certificate in Internet Explorer
> on the client), we could not get SSL working reliably on the report
> server, with various symptoms, one of which was the error you cite.
> In the end, since this was in the development environment, we ended up
> using SelfSSL, available from Microsoft at
> http://www.microsoft.com/windowsserver2003/iis/downloads/default.mspx .
> It's a lot better than makecert. You can also download an SSL
> diagnostic utility from the link given above, very helpful.
> now that's
> Highly Obscure
> pmud wrote:
> > Hi Highly Obscure,
> >
> > I tried that and it works but i get a different error now i.e "The
> > underlying connection was closed.could not establish trust
> > relationship with remote server."
> >
> > I think it is something related with SSL... I am reading a Microsoft
> > article right now at
> > http://support.microsoft.com/?scid=kb;en-us;823177 . If you have any
> > inputs, please let me know.
> >
> > Thanks
> >
>