If I specifiy a parameter in my report dataset like @.status to filter the
report based on a status selected by the user - I can't figure out how to
give them the "ALL" option - so that the report ignores the status and
displays all the records.
--
ArkayTry this
SELECT NULL AS StatusValue, '<All>' AS Status
UNION
SELECT StatusValue, Status
FROM Status_mstr
"Arkay" <Arkay@.discussions.microsoft.com> wrote in message
news:7E0C2DD8-A1E9-407C-BDDD-AD0B110C5775@.microsoft.com...
> If I specifiy a parameter in my report dataset like @.status to filter the
> report based on a status selected by the user - I can't figure out how to
> give them the "ALL" option - so that the report ignores the status and
> displays all the records.
>
> --
> Arkay
Showing posts with label status. Show all posts
Showing posts with label status. Show all posts
Friday, March 30, 2012
Monday, March 12, 2012
Report manager HTTP status 400: Bad Request
I am having trouble to access Report Manager on a fresh SQL Reporting Services install on Win 2003, SQL 2000 SP3a machine. /ReportServer works fine, I've created a Virtual Directory /OnlineReports to allow anomynous access but /Reports doesn't work. So I can't add IUSR to the folder I need anomymous access on. Can somebody please help?
Thanks in advance.
Is Report Manager configured correctly? Can you look in RSWebApplication.config and see what ReportServerUrl is set to?|||Yes, here's what it shows <ReportServerUrl>http://www.domain.com/ReportServer</ReportServerUrl>
www.domain.com/ReportServer works but www.domain.com/Reports doesn't.
Thank you.
|||Well, now I have a different error. It said The request failed with HTTP status 401: Unauthorized when I go to www.domain.com/Reports. I log in as Administrator and it still said I am unauthorized. Do I have to uninstall and reinstall to get this working?
Thank you.
|||Add a DWORD entry called DisableLoopbackCheck toHKLM\System\CurrentControlSet\Control\Lsa. Setting this key to a value of 1 fixed the issue.
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.
>
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.
>
Subscribe to:
Posts (Atom)