|
|
You're in the
sql server reporting services
group:HTTP Error 403 on Report Server
sql server reporting services:
I have just installed Reporting Services (SQL Server 2000 Std, Windows 2000 SP4) and within Report Designer (VS 2003 Architect) I can develop and test my reports successfully, but when I deploy them they produce a HTTP Error 403. The data source seems to be setup correctly and I can view the configuration correctly, the logical folder on the report server displays correctly with the report beneath it, but I cannot find the report rdl file physically on the report server. If anyone has any ideas no what I am doing wrong it would be of great help. Cheers, --
Yes I have created users and one of them is the Everyone domain group so that
everyone can browse the reports. Reporting Services seems to work to the point that I want to open a report, I can traverse folders, setup users and see data sources and the properties, including parameters, of reports, but when I want to view the report I get the error message. This is starting to impact our decision to go in this direction as it should be very simple but we can't get anywhere. -- John - DBA [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> You will not find any rdl files on the server. They don't exist. During > deployment the rdl is stored in the database, it never exists as a file on > the server. You say you see the report. It sounds like it deployed. I am > thinking that you do not have security setup correctly. Have you setup any > users or any roles for the users? If you have not added any group or user to > a role then you have missed a step. > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "John" <John@discussions.microsoft.com> wrote in message > news:0AD4D374-28CF-4C0B-AC7A-DA315895EEA1@microsoft.com... > > Hi, > > I have just installed Reporting Services (SQL Server 2000 Std, Windows > > 2000 SP4) and within Report Designer (VS 2003 Architect) I can develop and > > test my reports successfully, but when I deploy them they produce a HTTP > > Error 403. The data source seems to be setup correctly and I can view the > > configuration correctly, the logical folder on the report server displays > > correctly with the report beneath it, but I cannot find the report rdl > > file > > physically on the report server. > > > > If anyone has any ideas no what I am doing wrong it would be of great > > help. > > > > Cheers, > > -- > > John - DBA > >
Yes the Everyone group has browse access.
I am in the local admin group of the server and when I run it under that account I receive the same error. I have not touched IIS permissions, I have left that to RS. RS created a second default web site for me, so I have moved it (and in fact I am re-doing it right now) with the exact same settings, to the original default web site. I am running RS on Windows 2000, so I had to select domain user (doco says its a requirement) and have used a local admin for the account. Hope that helps. -- John - DBA [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> So you gave the Everyone group setup in the browse role? > > Are you in the local admininstrator group of the server that has RS > installed? > > Can you log into the server machine as a user (local administrator will > work) in the administrators group? If so, try doing that and see if it works > for you when you are sitting in front of the server. > > Have you touch IIS permissions at all or have you let RS handle it? > > Did you let RS install in the default website or did you move it? > > Is there anything outside of accepting defaults when you installed? > > If you are on Windows 2003 Server and you are installing you are given a > choice between network account (something like that) and service account. I > had trouble when I picked the network account, I make sure to pick service > account. > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > > "John" <John@discussions.microsoft.com> wrote in message > news:F55377B2-D69B-4D1B-95B3-38DF22ADB6D9@microsoft.com... > > Yes I have created users and one of them is the Everyone domain group so > > that > > everyone can browse the reports. Reporting Services seems to work to the > > point that I want to open a report, I can traverse folders, setup users > > and > > see data sources and the properties, including parameters, of reports, but > > when I want to view the report I get the error message. > > > > This is starting to impact our decision to go in this direction as it > > should > > be very simple but we can't get anywhere. > > -- > > John - DBA > > > > > > "Bruce L-C [MVP]" wrote: > > > >> You will not find any rdl files on the server. They don't exist. During > >> deployment the rdl is stored in the database, it never exists as a file > >> on > >> the server. You say you see the report. It sounds like it deployed. I am > >> thinking that you do not have security setup correctly. Have you setup > >> any > >> users or any roles for the users? If you have not added any group or user > >> to > >> a role then you have missed a step. > >> > >> > >> -- > >> Bruce Loehle-Conger > >> MVP SQL Server Reporting Services > >> > >> "John" <John@discussions.microsoft.com> wrote in message > >> news:0AD4D374-28CF-4C0B-AC7A-DA315895EEA1@microsoft.com... > >> > Hi, > >> > I have just installed Reporting Services (SQL Server 2000 Std, > >> > Windows > >> > 2000 SP4) and within Report Designer (VS 2003 Architect) I can develop > >> > and > >> > test my reports successfully, but when I deploy them they produce a > >> > HTTP > >> > Error 403. The data source seems to be setup correctly and I can view > >> > the > >> > configuration correctly, the logical folder on the report server > >> > displays > >> > correctly with the report beneath it, but I cannot find the report rdl > >> > file > >> > physically on the report server. > >> > > >> > If anyone has any ideas no what I am doing wrong it would be of great > >> > help. > >> > > >> > Cheers, > >> > -- > >> > John - DBA > >> > >> > >> > >
You will not find any rdl files on the server. They don't exist. During
deployment the rdl is stored in the database, it never exists as a file on the server. You say you see the report. It sounds like it deployed. I am thinking that you do not have security setup correctly. Have you setup any users or any roles for the users? If you have not added any group or user to a role then you have missed a step. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "John" <John@discussions.microsoft.com> wrote in message news:0AD4D374-28CF-4C0B-AC7A-DA315895EEA1@microsoft.com... > Hi, > I have just installed Reporting Services (SQL Server 2000 Std, Windows > 2000 SP4) and within Report Designer (VS 2003 Architect) I can develop and > test my reports successfully, but when I deploy them they produce a HTTP > Error 403. The data source seems to be setup correctly and I can view the > configuration correctly, the logical folder on the report server displays > correctly with the report beneath it, but I cannot find the report rdl > file > physically on the report server. > > If anyone has any ideas no what I am doing wrong it would be of great > help. > > Cheers, > -- > John - DBA
So you gave the Everyone group setup in the browse role?
Are you in the local admininstrator group of the server that has RS installed? Can you log into the server machine as a user (local administrator will work) in the administrators group? If so, try doing that and see if it works for you when you are sitting in front of the server. Have you touch IIS permissions at all or have you let RS handle it? Did you let RS install in the default website or did you move it? Is there anything outside of accepting defaults when you installed? If you are on Windows 2003 Server and you are installing you are given a choice between network account (something like that) and service account. I had trouble when I picked the network account, I make sure to pick service account. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "John" <John@discussions.microsoft.com> wrote in message news:F55377B2-D69B-4D1B-95B3-38DF22ADB6D9@microsoft.com... > Yes I have created users and one of them is the Everyone domain group so > that > everyone can browse the reports. Reporting Services seems to work to the > point that I want to open a report, I can traverse folders, setup users > and > see data sources and the properties, including parameters, of reports, but > when I want to view the report I get the error message. > > This is starting to impact our decision to go in this direction as it > should > be very simple but we can't get anywhere. > -- > John - DBA > > > "Bruce L-C [MVP]" wrote: > >> You will not find any rdl files on the server. They don't exist. During >> deployment the rdl is stored in the database, it never exists as a file >> on >> the server. You say you see the report. It sounds like it deployed. I am >> thinking that you do not have security setup correctly. Have you setup >> any >> users or any roles for the users? If you have not added any group or user >> to >> a role then you have missed a step. >> >> >> -- >> Bruce Loehle-Conger >> MVP SQL Server Reporting Services >> >> "John" <John@discussions.microsoft.com> wrote in message >> news:0AD4D374-28CF-4C0B-AC7A-DA315895EEA1@microsoft.com... >> > Hi, >> > I have just installed Reporting Services (SQL Server 2000 Std, >> > Windows >> > 2000 SP4) and within Report Designer (VS 2003 Architect) I can develop >> > and >> > test my reports successfully, but when I deploy them they produce a >> > HTTP >> > Error 403. The data source seems to be setup correctly and I can view >> > the >> > configuration correctly, the logical folder on the report server >> > displays >> > correctly with the report beneath it, but I cannot find the report rdl >> > file >> > physically on the report server. >> > >> > If anyone has any ideas no what I am doing wrong it would be of great >> > help. >> > >> > Cheers, >> > -- >> > John - DBA >> >> >>
What is causing the problem is having moved the website. Although this is
possible there are some additional steps you have to take. I have never done this so I don't know exactly what you need to do but I am pretty confident that is the problem. The issue here is that this is not just a bunch of web pages (which is why there are not files present for the reports). It is two asp.net applications. The report manager is a portal that uses web services to reportserver (the second and the meat of the product). There is either some utility you run or something in one of the config files that need changing. Sorry I can't get specific but hopefully that points you in the right direction. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "John" <John@discussions.microsoft.com> wrote in message news:5D91A173-1564-4EDA-AA92-588F4D91232C@microsoft.com... > Yes the Everyone group has browse access. > > I am in the local admin group of the server and when I run it under that > account I receive the same error. > > I have not touched IIS permissions, I have left that to RS. > > RS created a second default web site for me, so I have moved it (and in > fact > I am re-doing it right now) with the exact same settings, to the original > default web site. > > I am running RS on Windows 2000, so I had to select domain user (doco says > its a requirement) and have used a local admin for the account. > > Hope that helps. > -- > John - DBA > > > "Bruce L-C [MVP]" wrote: > >> So you gave the Everyone group setup in the browse role? >> >> Are you in the local admininstrator group of the server that has RS >> installed? >> >> Can you log into the server machine as a user (local administrator will >> work) in the administrators group? If so, try doing that and see if it >> works >> for you when you are sitting in front of the server. >> >> Have you touch IIS permissions at all or have you let RS handle it? >> >> Did you let RS install in the default website or did you move it? >> >> Is there anything outside of accepting defaults when you installed? >> >> If you are on Windows 2003 Server and you are installing you are given a >> choice between network account (something like that) and service account. >> I >> had trouble when I picked the network account, I make sure to pick >> service >> account. >> >> >> -- >> Bruce Loehle-Conger >> MVP SQL Server Reporting Services >> >> >> "John" <John@discussions.microsoft.com> wrote in message >> news:F55377B2-D69B-4D1B-95B3-38DF22ADB6D9@microsoft.com... >> > Yes I have created users and one of them is the Everyone domain group >> > so >> > that >> > everyone can browse the reports. Reporting Services seems to work to >> > the >> > point that I want to open a report, I can traverse folders, setup users >> > and >> > see data sources and the properties, including parameters, of reports, >> > but >> > when I want to view the report I get the error message. >> > >> > This is starting to impact our decision to go in this direction as it >> > should >> > be very simple but we can't get anywhere. >> > -- >> > John - DBA >> > >> > >> > "Bruce L-C [MVP]" wrote: >> > >> >> You will not find any rdl files on the server. They don't exist. >> >> During >> >> deployment the rdl is stored in the database, it never exists as a >> >> file >> >> on >> >> the server. You say you see the report. It sounds like it deployed. I >> >> am >> >> thinking that you do not have security setup correctly. Have you setup >> >> any >> >> users or any roles for the users? If you have not added any group or >> >> user >> >> to >> >> a role then you have missed a step. >> >> >> >> >> >> -- >> >> Bruce Loehle-Conger >> >> MVP SQL Server Reporting Services >> >> >> >> "John" <John@discussions.microsoft.com> wrote in message >> >> news:0AD4D374-28CF-4C0B-AC7A-DA315895EEA1@microsoft.com... >> >> > Hi, >> >> > I have just installed Reporting Services (SQL Server 2000 Std, >> >> > Windows >> >> > 2000 SP4) and within Report Designer (VS 2003 Architect) I can >> >> > develop >> >> > and >> >> > test my reports successfully, but when I deploy them they produce a >> >> > HTTP >> >> > Error 403. The data source seems to be setup correctly and I can >> >> > view >> >> > the >> >> > configuration correctly, the logical folder on the report server >> >> > displays >> >> > correctly with the report beneath it, but I cannot find the report >> >> > rdl >> >> > file >> >> > physically on the report server. >> >> > >> >> > If anyone has any ideas no what I am doing wrong it would be of >> >> > great >> >> > help. >> >> > >> >> > Cheers, >> >> > -- >> >> > John - DBA >> >> >> >> >> >> >> >> >>
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |