Monday, March 12, 2012
report manager is not working--urgent
I was working on reporting services and when i opening the report
manager in the browser, it is giving me error
the error is
the request failed with HTTP status 404: Not Found
and the reportserver it working fine.
I have seen the rswebapplication.config and the 2 virtual directories
also but i could trace out the problem. So please any one could help me
in finding the solution.
Thanks and Regards
JaganTry this : http://<servername>/Reports/Pages/Folder.aspx
And also : http://<servername>
On the other hand, when you do this : http://<servername>/reports/Pages,
error 404, it's normal.
However that may be, the server can't access the folder or the page...
Hope this can help|||I am also having same problem where in suddenly I have started getting:
The request failed with HTTP status 404: Not Found.
I have tried qualifying the server name and checked rswebapplication.config
file too but cant fix the problem.
Any other pointers will be highly appreciated!!
--
Thanks
"Doume" wrote:
> Try this : http://<servername>/Reports/Pages/Folder.aspx
> And also : http://<servername>
> On the other hand, when you do this : http://<servername>/reports/Pages,
> error 404, it's normal.
> However that may be, the server can't access the folder or the page...
> Hope this can help
>|||Hi What do we need to check in the rswebapplication.config file?
I have the same issue
"Doume" wrote:
> Try this : http://<servername>/Reports/Pages/Folder.aspx
> And also : http://<servername>
> On the other hand, when you do this : http://<servername>/reports/Pages,
> error 404, it's normal.
> However that may be, the server can't access the folder or the page...
> Hope this can help
>|||Check to see if you have removed the Virtual Directory 'Reportserver' in IIS
if so add back - it should point to "C:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportServer" or there's abouts.
"tiwanap" wrote:
> I am also having same problem where in suddenly I have started getting:
> The request failed with HTTP status 404: Not Found.
> I have tried qualifying the server name and checked rswebapplication.config
> file too but cant fix the problem.
> Any other pointers will be highly appreciated!!
> --
> Thanks
>
> "Doume" wrote:
> > Try this : http://<servername>/Reports/Pages/Folder.aspx
> >
> > And also : http://<servername>
> > On the other hand, when you do this : http://<servername>/reports/Pages,
> > error 404, it's normal.
> >
> > However that may be, the server can't access the folder or the page...
> >
> > Hope this can help
> >
> >
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
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.
>
Tuesday, February 21, 2012
Report generation is consuming 100% of CPU client side.
Hi,
I have a problem while rendering a report which returns around 5000 rows. At first the server is busy to process the request, when the server is done the rendering client side takes 100% of CPU and never displays the result ("IE is not responding"). It seems that the ReportViewer has trouble to handle the server response.
Do you have any idea why ?
Sbastien.
It appeared that the problem is a paging issue. The report contains groups and by default the top level is collapsed, when we try to expand a level that contains many rows thoses rows are all displayed on a single page. That's why IE is consuming 100% of the CPU to display all the rows.
How can I change that the paging is working for the sub groups displayed ?
|||I found the answer in BOL:
"The HTML and Excel rendering extensions are not oriented to physical pages. Furthermore, the HTML rendering extension is interactive, meaning that user actions in a report can trigger additional processing that causes a report to expand horizontally or vertically to accommodate additional content. You cannot precisely control how reports viewed through these rendering extensions will paginate if the report contains interactive features."
Report generation is consuming 100% of CPU client side.
Hi,
I have a problem while rendering a report which returns around 5000 rows. At first the server is busy to process the request, when the server is done the rendering client side takes 100% of CPU and never displays the result ("IE is not responding"). It seems that the ReportViewer has trouble to handle the server response.
Do you have any idea why ?
Sbastien.
It appeared that the problem is a paging issue. The report contains groups and by default the top level is collapsed, when we try to expand a level that contains many rows thoses rows are all displayed on a single page. That's why IE is consuming 100% of the CPU to display all the rows.
How can I change that the paging is working for the sub groups displayed ?
|||I found the answer in BOL:
"The HTML and Excel rendering extensions are not oriented to physical pages. Furthermore, the HTML rendering extension is interactive, meaning that user actions in a report can trigger additional processing that causes a report to expand horizontally or vertically to accommodate additional content. You cannot precisely control how reports viewed through these rendering extensions will paginate if the report contains interactive features."