Reserved.ReportViewerWebControl.axd not found

Ran into this issue the other day at work. We were developing some reporting services reports for a client and viewing them through a report viewer control in the intranet site we were developing.

The reports ran fine in the development environment but as soon as it was published to testing the reports behaved strangely. The test box was a Windows 2008 Server Standard Edition with IIS installed and .NET 3.5 SP1.

The reports page was reporting a 404 on the following resource “Reserved.ReportViewerWebControl.axd”

This handler was definitely present in the web.config file:

I did the following to resolve this issue.

1. Install Report Viewer 2008 Redist + SP1
2. In IIS 7 | Handler Mappings

1. Under Actions | Add Managed Handler…

   

   1. Request path: Reserved.ReportViewerWebControl.axd
   2. Type: Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
   3. Name: Reserved-ReportViewerWebControl-axd

      

2. Click OK

Now the reports load up fine.

Comments

[Michael K. Campbell]

Thanks a million Eric.

I assumed it was something JUST like this - so you totally saved me some valuable time in troubleshooting!

[Jeffrey]

Thanks for your valuable information, it solved my problem and I posted my tips on blog with a reference to your great post. (http://blog.darkthread.net/blogs/darkthreadtw/archive/2009/02/02/reportviewer-2008-on-iis7.aspx)

After testing, I found "2.Type: Microsoft.Reporting.Microsoft.Reporting.WebForms.HttpHandler, ...." should be Microsoft.Reporting.WebForms.HttpHandler, there is redundant "Microsoft.Reporting.Microsoft.Reporting" in your post.

[Milton]

Thank You Mr. Eric,

This has save a lot of my time

[wolly]

谢谢帮我我解决大问题！

[Jacques Amar]

Please know that your sharing is greatly appreciated. The mindless hours spent trying to figure this out ...

Thanks

[elkami]

nice :D

thank you very much i solve my problem

[Geoffo]

Cheers dude - that was just what I needed!

[Enriue]

This solved my problem as well. I really appreciate the resolution.

[BobM]

Just thought I'd chime in and remind you that you are THE MAN. This was my issue exactly.

[Maulik Dhorajia]

Thanks a lot. This have been really helpfull.

[Anonymous]

You have a typo in your page:

Microsoft.Reporting.Microsoft.Reporting.WebForms.HttpHandle

Should be:
Microsoft.Reporting.WebForms.HttpHandle

[Eric Phan]

Thanks, fixed the typo

[Matt]

Eric ROCKS.

Saved me and my co-worker ton's of frustration and hyffage.

[Sean]

Thanks so much! I just wonder why this is not automatic and why it doesn't work from the Web.config like it is supposed to according to the documentation.

[Carl]

Great Thanks!

[Thomas]

THANK YOU!!! Dang, I started to tear up after the reports finally showed up. I wish I were a millionaire and you would have some of the wealth.

[Richard]

It seems to me a change you make like that in IIS Manager should also be doable in Web.config. I wonder if the handler you have in your Web.config is in the right place for IIS 7?
If you're deploying to IIS 7, then instead of having handlers in <configuration><system.web><httpHandlers>, you should instead place them (with an additional name attribute) in <configuration><system.webServer><handlers>.
If you want your application to be deployable to either IIS 6 or 7, you can leave the handler declarations in both places.

[Dan]

The solution posted by Richard (adding it to system.webServer) did the trick for me. Thanks!

[suresh]

Thank you! it worked like a charm!

[Jhonny]

Thanks man, it was just what I needed

[Larry]

Thanks! Worked like a charm!!

[Carl]

Thank you very much. I'd just come across this issue in a recent project, and this fixed it wonderfully. Thank you!

[Alan]

Thank you so much, I have been struggling for days and your post sorted in minutes. Thanks - keep posting

[Bryan Bernardo PH]

life saver.

[Grum]

After seeing millions of solution that dont solve my problem, when I was nearly crying You Master save my mental health :)

[Scott McGlothlin]

That was the issue on the new 2008 R2 server. Found the error...but this post pointed me in the right direction for the fix. Thanks for the help.

[Nitin]

Thank you.
Your Post really helped me.

[Luis Conde]

Thank you Eric, I can keep my job now