Problem Viewing reports in Report Manager

I have successfully installed the sql server reporting services on a windows
2003 server. I have been able to deploy several reports to the report
server. I have even been able to schedule a report to execute and send out
via email every morning of the week.
Here's the problem. When I try to view a report using the report manager I
get a
The page cannot be found
HTTP 404 - File not found
Internet Explorer
error. I just don't get it. I can perform every other function using the
report manager except view the report online. Which of course is a problem
because I want to send my customers to the site to be able to view and run
reports.
Thanks for any help.
--
Jon Clayton
Regions Financial CorporationSounds like a security issue or a malformed URL. It's very difficult (from
here) to determine how you access report manager differently than the online
version, but could you post a URL that worked, and a URL that failed?
Dwayne|||Thanks for your help.
Here is a link that works
http://Servername/Reports/Pages/Folder.aspx
This link of course brings up the default folders page
Click on a folder and go to the following url, which work
http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
Click on a report in that folder to view the report using the following url
fail
http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
The failure only occurs within the frame below. The header frame is still
displayed, therefore I am able to:
Click on the properties tab with the failed page displayed is successful
using the following ur
http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
I have given full access permissions to the ASPNET account on the local
machine to the two RS folders.
I am convinced that it is a permissions issue. As a matter of fact I had an
instance installed in my test invironment which is Windows 2000 which worked
fine. But ever since the latest security updates that machine is having the
same issue.
Thanks again for your help.
--
Jon Clayton
Regions Financial Corporation
"Dwayne J. Baldwin" wrote:
> Sounds like a security issue or a malformed URL. It's very difficult (from
> here) to determine how you access report manager differently than the online
> version, but could you post a URL that worked, and a URL that failed?
> Dwayne
>
>|||"Jon" wrote:
> Thanks for your help.
> Here is a link that works
> http://Servername/Reports/Pages/Folder.aspx
> This link of course brings up the default folders page
> Click on a folder and go to the following url, which works
> http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
> Click on a report in that folder to view the report using the following url
> fails
> http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
> The failure only occurs within the frame below. The header frame is still
> displayed, therefore I am able to:
> Click on the properties tab with the failed page displayed is successful
> using the following url
> http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
> I have given full access permissions to the ASPNET account on the local
> machine to the two RS folders.
> I am convinced that it is a permissions issue. As a matter of fact I had an
> instance installed in my test invironment which is Windows 2000 which worked
> fine. But ever since the latest security updates that machine is having the
> same issue.
> Thanks again for your help.
> --
> Jon Clayton
> Regions Financial Corporation
>
> "Dwayne J. Baldwin" wrote:
> > Sounds like a security issue or a malformed URL. It's very difficult (from
> > here) to determine how you access report manager differently than the online
> > version, but could you post a URL that worked, and a URL that failed?
> >
> > Dwayne
> >
> >
> >
> > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.|||It appears that the entries in the config files are correct. Thanks for the
tip.
--
Jon Clayton
Regions Financial Corporation
"DLM" wrote:
>
> "Jon" wrote:
> > Thanks for your help.
> >
> > Here is a link that works
> > http://Servername/Reports/Pages/Folder.aspx
> > This link of course brings up the default folders page
> >
> > Click on a folder and go to the following url, which works
> > http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
> >
> > Click on a report in that folder to view the report using the following url
> > fails
> > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
> > The failure only occurs within the frame below. The header frame is still
> > displayed, therefore I am able to:
> >
> > Click on the properties tab with the failed page displayed is successful
> > using the following url
> > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
> >
> > I have given full access permissions to the ASPNET account on the local
> > machine to the two RS folders.
> >
> > I am convinced that it is a permissions issue. As a matter of fact I had an
> > instance installed in my test invironment which is Windows 2000 which worked
> > fine. But ever since the latest security updates that machine is having the
> > same issue.
> >
> > Thanks again for your help.
> >
> > --
> > Jon Clayton
> > Regions Financial Corporation
> >
> >
> > "Dwayne J. Baldwin" wrote:
> >
> > > Sounds like a security issue or a malformed URL. It's very difficult (from
> > > here) to determine how you access report manager differently than the online
> > > version, but could you post a URL that worked, and a URL that failed?
> > >
> > > Dwayne
> > >
> > >
> > >
> > > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.|||Hi Jon,
I have exactly the same problem. Please advise what I need to check/do?
Thanks very much
Khat.
"Jon" wrote:
> It appears that the entries in the config files are correct. Thanks for the
> tip.
> --
> Jon Clayton
> Regions Financial Corporation
>
> "DLM" wrote:
> >
> >
> > "Jon" wrote:
> >
> > > Thanks for your help.
> > >
> > > Here is a link that works
> > > http://Servername/Reports/Pages/Folder.aspx
> > > This link of course brings up the default folders page
> > >
> > > Click on a folder and go to the following url, which works
> > > http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
> > >
> > > Click on a report in that folder to view the report using the following url
> > > fails
> > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
> > > The failure only occurs within the frame below. The header frame is still
> > > displayed, therefore I am able to:
> > >
> > > Click on the properties tab with the failed page displayed is successful
> > > using the following url
> > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
> > >
> > > I have given full access permissions to the ASPNET account on the local
> > > machine to the two RS folders.
> > >
> > > I am convinced that it is a permissions issue. As a matter of fact I had an
> > > instance installed in my test invironment which is Windows 2000 which worked
> > > fine. But ever since the latest security updates that machine is having the
> > > same issue.
> > >
> > > Thanks again for your help.
> > >
> > > --
> > > Jon Clayton
> > > Regions Financial Corporation
> > >
> > >
> > > "Dwayne J. Baldwin" wrote:
> > >
> > > > Sounds like a security issue or a malformed URL. It's very difficult (from
> > > > here) to determine how you access report manager differently than the online
> > > > version, but could you post a URL that worked, and a URL that failed?
> > > >
> > > > Dwayne
> > > >
> > > >
> > > >
> > > > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.|||I am also having this same exact problem. I can run everything without issue
on our test server but production server is exhibiting this exact behavior?
I can do everything but view the report. I can even run the report on the
production server through code and through http://server/reportserver.
Navigate to the folder/report and viola. I can enter parameters and run it.
But not in the report manager gui' I get a 404 when I press the view
report button. If I press it a second time I then get an error in the lower
left hand corner of IE. If I open it up it states that on Line 50 permission
denied and url = http://server/reportserver...blah...blah...blah
Kevin
"Khat Liko" wrote:
> Hi Jon,
> I have exactly the same problem. Please advise what I need to check/do?
> Thanks very much
> Khat.
> "Jon" wrote:
> > It appears that the entries in the config files are correct. Thanks for the
> > tip.
> > --
> > Jon Clayton
> > Regions Financial Corporation
> >
> >
> > "DLM" wrote:
> >
> > >
> > >
> > > "Jon" wrote:
> > >
> > > > Thanks for your help.
> > > >
> > > > Here is a link that works
> > > > http://Servername/Reports/Pages/Folder.aspx
> > > > This link of course brings up the default folders page
> > > >
> > > > Click on a folder and go to the following url, which works
> > > > http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
> > > >
> > > > Click on a report in that folder to view the report using the following url
> > > > fails
> > > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
> > > > The failure only occurs within the frame below. The header frame is still
> > > > displayed, therefore I am able to:
> > > >
> > > > Click on the properties tab with the failed page displayed is successful
> > > > using the following url
> > > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
> > > >
> > > > I have given full access permissions to the ASPNET account on the local
> > > > machine to the two RS folders.
> > > >
> > > > I am convinced that it is a permissions issue. As a matter of fact I had an
> > > > instance installed in my test invironment which is Windows 2000 which worked
> > > > fine. But ever since the latest security updates that machine is having the
> > > > same issue.
> > > >
> > > > Thanks again for your help.
> > > >
> > > > --
> > > > Jon Clayton
> > > > Regions Financial Corporation
> > > >
> > > >
> > > > "Dwayne J. Baldwin" wrote:
> > > >
> > > > > Sounds like a security issue or a malformed URL. It's very difficult (from
> > > > > here) to determine how you access report manager differently than the online
> > > > > version, but could you post a URL that worked, and a URL that failed?
> > > > >
> > > > > Dwayne
> > > > >
> > > > >
> > > > >
> > > > > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.