Home » BizTalk ServerRSS

403 error: The remote server returned an error: (403) Forbidden.

When I try to view the report, I got the error "The remote server returned an error: (403) Forbidden. ". And in the event log , I got the detaiil excception:


Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date:  2007-7-16
Time:  11:28:29
User:  N/A
Computer: WEIGUANG
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 2007-7-16 11:28:29
Event time (UTC): 2007-7-16 3:28:29
Event ID: 3c4daa414c89430786c106f3c9085b56
Event sequence: 10
Event occurrence: 1
Event detail code: 0

Application information:
    Application domain: /LM/W3SVC/1/Root/Reports-2-128290300818412520
    Trust level: RosettaMgr
    Application Virtual Path: /Reports
    Application Path: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\
    Machine name: WEIGUANG

Process information:
    Process ID: 4152
    Process name: w3wp.exe
    Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
    Exception type: WebException
    Exception message: The remote server returned an error: (403) Forbidden.

Request information:
    Request URL:
http://localhost/Reports/Reserved.ReportViewerWebControl.axd?OpType=StyleSheet&Version=2005.090.3042.00
    Request path: /Reports/Reserved.ReportViewerWebControl.axd
    User host address: 127.0.0.1
    User: ASIAPACIFIC\liweig
    Is authenticated: True
    Authentication Type: NTLM
    Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
    Thread ID: 5
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: True
    Stack trace:    at Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
   at Microsoft.Reporting.WebForms.ServerReport.GetStyleSheet(String styleSheetName)
   at Microsoft.Reporting.WebForms.ReportServerStyleSheetOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response)
   at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


Custom event details: For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I'm using reporting service 2005, does anybody know the reason?

Many thanks.

Kevin

 

30 Answers Found

 

Answer 1

I don't know what was the issue. My SSRS was working properly but after installing .NET 4.0 on the server I started getting 403 error.

 

This solution worked for me as well :) Thank you very much!!!! :)

 

 

Answer 2

Fixed it for me too. No idea what caused it.
 

Answer 3

we encounter the same problem. did you already resolved it? can you give us a hint?

thx in advance,
rainer
 

Answer 4

IIS permissions.

403?

You're not even touching the Report Server.

You need to get your IIS admin to allow your group/users permission to see the RS folders

 

Answer 5

well i am getting the following entry in the eventlog:

Event Type:    Warning
Event Source:    ASP.NET 2.0.50727.0
Event Category:    Web event  
Event ID:    1309
Date:        24.07.2007
Time:        12:37:38
User:        N/A
Computer:    HERAS75
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 24.07.2007 12:37:38
Event time (UTC): 24.07.2007 10:37:38
Event ID: f6730dc158f640c7924c590d73226477
Event sequence: 112
Event occurrence: 5
Event detail code: 0

Application information:
    Application domain: /LM/W3SVC/1/root/AdminReports-1-128297459440092913
    Trust level: RosettaMgr
    Application Virtual Path: /AdminReports
    Application Path: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\
    Machine name: HERAS75

Process information:
    Process ID: 5052
    Process name: w3wp.exe
    Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
    Exception type: WebException
    Exception message: The remote  server returned  an error: (403) Forbidden.

Request information:
    Request URL: http://heras75/AdminReports/Reserved.ReportViewerWebControl.axd?OpType=StyleSheet&Version=2005.090.3042.00
    Request path: /AdminReports/Reserved.ReportViewerWebControl.axd
    User host address: 10.101.7.26
    User: HER\admin_arnken
    Is authenticated: True
    Authentication Type: Negotiate
    Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
    Thread ID: 7
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: True
    Stack trace:    at Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
   at Microsoft.Reporting.WebForms.ServerReport.GetStyleSheet(String styleSheetName)
   at Microsoft.Reporting.WebForms.ReportServerStyleSheetOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response)
   at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


if am opening a report  page it starts rendering the page but then throws the following error  and no data is shown:
The remote server  returned an error: (403) Forbidden.can you point me into the right direction which group/users i have to set permissions? thank you very much for your replay

 

Answer 6

Admin tools -> IIS
directory security
edit
select 'integrated windows authentication'
ok


right click 'permissions'
from here you can see which groups/users have access

it is better to administer with groups as that way, when someone bothers you to see a report, you can tell them to go and see the helpdesk/whoever manages AD groups instead, and get them to add them to the group


 

Answer 7

I added the user I login as here for both the Reports and ReportServer folders and gave this user full permission. I'm still getting the 403  error when I try to open a report  from http://localhost/reports. It generates part of the report toolbar and just as it apperas the report wants to begin rendering, I get the error.

 

Answer 8

If the actual DB and the Report server  is deployed in 2 different machines and for the shared data source, if "integrated security" is used then your windows domain must use "keberos". By using this security the credentails can be passed to any number of servers in the network.

See the following article on how to set up computer to be trusted for delegation

http://technet2.microsoft.com/WindowsServer/en/library/b207ee9c-a055-43f7-b9be-20599b694a311033.mspx?mfr=true

 

Answer 9

Both the report server  and the actual DB are on the same server.

 

Answer 10

Only other thing I would think of is the database permissions. Does the user has the correct permissions?
 

Answer 11

Here is the error.

http://i55.photobucket.com/albums/g121/Farsight38/Error.jpg

I'm trying to grant all permissions imaginable in both IIS and SQL. I guess I'm just not flipping the right switch.

The user I log  into windows as has full control over the Report server  and Reports directories in IIS.

Here is the event  log:

Event code: 3005

Event message: An unhandled exception has occurred.

Event time: 11/2/2007 1:44:52 PM

Event time (UTC): 11/2/2007 6:44:52 PM

Event ID: a2b6d0edb6be470faf6557f860fcf00e

Event sequence: 646

Event occurrence: 25

Event detail code: 0

Application information:

Application domain: /LM/W3SVC/1/root/Reports-1-128384985826483918

Trust level: RosettaMgr

Application Virtual Path: /Reports

Application Path: C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportManager\

Machine name: DHS3GL01

Process information:

Process ID: 756

Process name: w3wp.exe

Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:

Exception type: WebException

Exception message: The remote  server returned  an error: (403) Forbidden.

Request information:

Request URL: http://localhost/Reports/Reserved.ReportViewerWebControl.axd?OpType=StyleSheet&Version=2005.090.3042.00

Request path: /Reports/Reserved.ReportViewerWebControl.axd

User host address: 127.0.0.1

User: MN-DHS3\Quantum

Is authenticated: True

Authentication Type: Negotiate

Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:

Thread ID: 20

Thread account name: NT AUTHORITY\NETWORK SERVICE

Is impersonating: True

Stack trace: at Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)

at Microsoft.Reporting.WebForms.ServerReport.GetStyleSheet(String styleSheetName)

at Microsoft.Reporting.WebForms.ReportServerStyleSheetOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response)

at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context)

at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 
 

Answer 13

Assign it write access where? When I try to add NT AUTHORITY\NETWORK SERVICE to Reports and Report Server permissions, it says that that account doesn't exist.

 
 
 

Answer 16

Also, when I try to even open http://localhost/reportserver I get the 403  error.

 

Answer 17

It's fixed. All I did was apply default settings to the report server  virtual directory in reporting services configuration manager. It's strange because all of the components in configuration manager had green check marks.

 

Answer 18

Thank you for the information.It helped me a lot.

 

Answer 19

You're welcome. Glad we could help.

 

Answer 20

I've been working on this problem for 4 days or so... Your solution solved it.... Thanks a Million!
 

Answer 21

Excellent. Once again, glad to help.

 

Answer 22

Wow - "All I did was apply default settings to the report server  virtual directory in reporting services configuration manager. It's strange because all of the components in configuration manager had green check marks."

That fixed it for me as well ... after a day of fighting thats all that was needed ... bizarre ...
 

Answer 23

Fixed my problem too.... kind of.  There are two Virtual Directories that you can "Apply default settings" against..  Mine happened to be Report Manager Virtual Directory rather than Report Server Virtual Directory, but it was still the same fix, and your post is what pointed me in that direction.  The odd property of the whole story is that for no apparent reason, SQL Reporting Services woke up one day and decided not to  service any more requests and would just give the 403  (Forbidden) Response page to anyone who tried to access it from any computer, including localhost.  Once I applied this fix...viola!
Thanks much!

 

Answer 24

You fix my problem too!!

Thank's !!!!
 

Answer 25

I had the same issue, and your answer saved me valuable time.
I would about to reinstall the whole reporting services.

Thanks
 

Answer 26

Thank you! This fixed my issue as well (and saved some, but not all, of my hair ;)
 

Answer 27

Great. I got the same issue and got resolved by applying default settings.Thanks.
 

Answer 28

Thanks, It's works for me also.,  I just uninstalled  all  .net Framework  and  renitalled  .net Framework  2.0  SP2  and  applied default settings to the report server  virtual directory in reporting services configuration manager.
 

Answer 29

Thx. I had problems with just displaying any reports at all in the report  list (and I was logged on as admin). Applying default settings solved it for me.

 

Answer 30

Guess what... Worked for me too, what a silly solution!  Logic doesn't tell you to try that, a typical MS issue!  Thanks all.
 
 
 

<< Previous      Next >>


Microsoft   |   Windows   |   Visual Studio   |   Follow us on Twitter