Friday, March 9, 2012

Report Manager and The request failed with HTTP status 400

I have installed Reporting services on a win2k3 on a completely different
irtual Directory than Default Directory .My Report Server is working fine
but I can't get my reporting manager working it give me this error:
The request failed with HTTP status 400:bad request,
Is there somebody who can help me.
ThnaksI think I got the answert ,,
I'm using a DNS for the new virtual directory that I have installed report
server and report manager on it and I forogt to update <ReportServerUrl> in
the RSWebApplication.config file of "Report Manager"
in the following address:
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager
It was pointing to the wrong address http://localhost/reportsver where as it
should be http://MyDNS/reportsver.
HTH,
ALI-R
"ALI-R" <newbie@.microsoft.com> wrote in message
news:%23s41$7MBFHA.3528@.tk2msftngp13.phx.gbl...
> I have installed Reporting services on a win2k3 on a completely different
> irtual Directory than Default Directory .My Report Server is working fine
> but I can't get my reporting manager working it give me this error:
> The request failed with HTTP status 400:bad request,
> Is there somebody who can help me.
> Thnaks
>|||Hi all,
we're still in trouble as our ReportManager webapp still won't work.
I verified the RSWebApplication.config files of both Report Manager and
Report Server to contain
<ReportServerUrl>http://localhost/ReportServer</ReportServerUrl>
and
<UrlRoot>http://localhost/ReportServer</UrlRoot>
respectively.
I already verified all permissions and even changed both above URLs to read
http://<servername> instead of localhost. This does not make any noticable
difference.
This is real trouble, MS, I'd hate to have to resort to reïnstalling
everything from scratch, as there's no telling how if, or how long, this will
work...
Please help? :o(
Ramses.
Still, the ReportServer works just fine on both
http://localhost/ReportServer and http://severname/ReportServer, wheras the
ReportManager simply refuses to work. It keeps yielding the dreaded
The request failed with HTTP status 400: Bad Request.
"ALI-R" wrote:
> I think I got the answert ,,
> I'm using a DNS for the new virtual directory that I have installed report
> server and report manager on it and I forogt to update <ReportServerUrl> in
> the RSWebApplication.config file of "Report Manager"
> in the following address:
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager
> It was pointing to the wrong address http://localhost/reportsver where as it
> should be http://MyDNS/reportsver.
> HTH,
> ALI-R
> "ALI-R" <newbie@.microsoft.com> wrote in message
> news:%23s41$7MBFHA.3528@.tk2msftngp13.phx.gbl...
> > I have installed Reporting services on a win2k3 on a completely different
> > irtual Directory than Default Directory .My Report Server is working fine
> > but I can't get my reporting manager working it give me this error:
> >
> > The request failed with HTTP status 400:bad request,
> >
> > Is there somebody who can help me.
> >
> > Thnaks
> >
> >
>
>|||Hi all,
we're still in trouble as our ReportManager webapp still won't work.
I verified the RSWebApplication.config files of both Report Manager and
Report Server to contain
<ReportServerUrl>http://localhost/ReportServer</ReportServerUrl>
and
<UrlRoot>http://localhost/ReportServer</UrlRoot>
respectively.
I already verified all permissions and even changed both above URLs to read
http://<servername> instead of localhost. This does not make any noticable
difference.
This is real trouble, MS, I'd hate to have to resort to reïnstalling
everything from scratch, as there's no telling how if, or how long, this will
work...
Please help? :o(
Ramses.
"ALI-R" wrote:
> I think I got the answert ,,
> I'm using a DNS for the new virtual directory that I have installed report
> server and report manager on it and I forogt to update <ReportServerUrl> in
> the RSWebApplication.config file of "Report Manager"
> in the following address:
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager
> It was pointing to the wrong address http://localhost/reportsver where as it
> should be http://MyDNS/reportsver.
> HTH,
> ALI-R
> "ALI-R" <newbie@.microsoft.com> wrote in message
> news:%23s41$7MBFHA.3528@.tk2msftngp13.phx.gbl...
> > I have installed Reporting services on a win2k3 on a completely different
> > irtual Directory than Default Directory .My Report Server is working fine
> > but I can't get my reporting manager working it give me this error:
> >
> > The request failed with HTTP status 400:bad request,
> >
> > Is there somebody who can help me.
> >
> > Thnaks
> >
> >
>
>|||I would check the host header in IIS. I have been having a problem
where I can't view the report properties, export a report, or schedule
a report (viewing is fine, though).
I was messing with the host headers in IIS and got that message if I
had things configured incorrectly. For working locally, you should
probably not have anything in the host header value for the site.|||I have no Host-headers set for the default website - checked this numerous
times. The default website is bound to both 127.0.0.1 and the LAN IP address
of the server. Note that my http://<servername>/Reports tests wouldn't have
worked otherwise.
Still at a loss. :o(
"cybermud" wrote:
> I would check the host header in IIS. I have been having a problem
> where I can't view the report properties, export a report, or schedule
> a report (viewing is fine, though).
> I was messing with the host headers in IIS and got that message if I
> had things configured incorrectly. For working locally, you should
> probably not have anything in the host header value for the site.
>

No comments:

Post a Comment