I have a brand-new Toshiba laptop, running Vista Business, that I installed SQL Express onto. Prior to installation, I was sure to install all the requisite IIS components so SSRS would install. The installation ran fine -- installed all components. The configuration ran fine. Everything that is supposed to be green shows green But, when I go to http://localhost/ReportServer, I get: Server Error in Application "Default Web Site/ReportServer" -------------------------------------------------------------------------------- HTTP Error 404.2 - Not FoundDescription: The page you are requesting cannot be served because of the ISAPI and CGI Restriction list settings on the Web server. Error Code: 0x800704ec Notification: ExecuteRequestHandler Module: IsapiModule Requested URL: http://localhost:80/ReportServer Physical Path: C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer Logon User: Anonymous Logon Method: Anonymous Handler: AboMapperCustom-34881 Most likely causes: No handler mapping for this request was found. A feature may have to be installed. The Web service extension for the requested resource is not enabled on the server. The mapping for the extension points to the incorrect location. The extension was misspelled in the browser or the Web server. What you can try: Install the feature that handles this request. For example, if you get this error for an .ASPX page, you may have to install ASP.NET via IIS setup. Verify that the Web service extension requested is enabled on the server. Open the IIS Manager and navigate to the server level. In the Features view, double-click ISAPI and CGI Restrictions to verify that the Web service extension is set to Allowed. If the extension is not in the list, click Add in the Actions pane. In the Add ISAPI and CGI Restrictions dialog box, type the path of the .dll or .exe file in the ISAPI or CGI Path box, or click Browse to navigate to the location of the file. In the Description box, type a brief description of the restriction. (Optional) Check "Allow extension path to execute" to allow the restriction to run automatically. If you do not check this option, the restriction status is Not Allowed, which is the default. You can allow the restriction later by selecting it and clicking Allow on the Actions pane. Click OK. NOTE: Make sure that this Web service extension or CGI is needed for your Web server before adding it to the list. Verify that the location of the extension is correct. Verify that the URL for the extension is spelled correctly both in the browser and the Web server. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here. More Information... This error occurs when the necessary Web service extension is not enabled, the location or the name of the extension are misspelled or incorrectly entered. --------------------------------------------------------------------------------Server Version Information: Internet Information Services 7.0. The only lead I could find when I googled this error was a reference to running appcmd to ensure that asp.net was enabled. It sure looks like it is: C:\Windows\System32\inetsrv>appcmd list config -section:isapiCgiRestriction<system.webServer> <security> <isapiCgiRestriction> <add path="%windir%\system32\inetsrv\asp.dll" allowed="true" groupId="ASP"description="Active Server Pages" /> <add path="%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" allowed="true" groupId="ASP.NET v2.0.50727" description="ASP.NET v2.0.50727" /> </isapiCgiRestriction> </security></system.webServer> C:\Windows\System32\inetsrv> Honestly... I'm out of ideas. I've been messing with this for 8 hours now, and I'm ready to fling the laptop out the window. I've completely UNinstalled SQL Server, IIS, reinstalled both, repeated the uninstall/reinstall after double-checking all files were deleted, and so on. Does *anyone* know how to resolve this error? I checked IIS.NET and although they have a few references to it (not within the Reporting Services context) there never seems to be a definitive answer as to what the solution is.

Did you follow this part of the message above? Open the IIS Manager and navigate to the server level. In the Features view, double-click ISAPI and CGI Restrictions to verify that the Web service extension is set to Allowed. If the extension is not in the list, click Add in the Actions pane. In the Add ISAPI and CGI Restrictions dialog box, type the path of the .dll or .exe file in the ISAPI or CGI Path box, or click Browse to navigate to the location of the file. In the Description box, type a brief description of the restriction. (Optional) Check "Allow extension path to execute" to allow the restriction to run automatically. If you do not check this option, the restriction status is Not Allowed, which is the default. You can allow the restriction later by selecting it and clicking Allow on the Actions pane. Click OK.

Thank you for the reply. Unfortunately, this really doesn't help me. Looking at that tab in IIS Manager, I see the same thing that I get thru the APPCMD command -- that is, both ASP and ASP.NET isapi filters are allowed to execute. What other dll or exe is supposed to be present in this list? And, more importantly, why wouldn't the SSRS setup place it there automatically during installation? I had a buddy attempt the installation on his Vista machine, with identical results -- it doesn't work.

There seems to be a lot of google results for "reporting services vista problem" Have you checked them? I empathise with your problem, I have install problems with Reporting Services a number of times myself although they were all related to not having IIS and ASP.Net 2.0 registered together i.e. iis was installed AFTER asp.net 2.0 was installed. http://www.jameskovacs.com/blog/ReportingServicesOnWindowsVista.aspx http://aspadvice.com/blogs/ssmith/archive/2007/02/05/Reporting-Services-Plus-Vista-Equals-Pain.aspx

Yup, all those things are inapplicable in my case, I either did them already prior to installation, or subsequently tried them after. For example, the first time I attempted to install reporting services, the option to install RS didn't even appear in the products list, because the requisite IIS components weren't installed. I did finally -- after another 8 hours of dicking around with it yesterday -- manage to get it to work. Here's what I had to do. 1. I completely uninstalled SQL Server, *ALL* IIS components, *AND* finallyall WIndows Process Activation components off my Vista box. Reboot. 2. Manually deleted any leftover files in \program files from previous SQL server installation. Also, deleted the .config files in c:\windows\system32\inetsrv\config 3. Reinstalled IIS, making sure to select ONLY the components needed for RS, and nothing else. This in turn automatically reinstalled WPA. Reboot. 4. Install SQL Server, all components. Unclicked "hide advanced options".Installation asked if it should install default configuration for RS. I accepted all default answers. Installation ran fine. 5. attempted to go to http://localhost/Reports and //localhost/reportserver. Received odd messages about not being able to read ReportServerxxxxx.config files from those directories. Checked permissions. The Install-createdReportingServices groups already had read permission. Used SysInternals Process monitor to see what was attempting to read and getting an access denied in c:\program files\microsoft sql server. Determined it was a w3wp.exe task (web server?) Rather than attempting to investigate further, I simply granted "Everyone" read permission to the directory and propagated the rights down the filesystem chain. Might be one or two other minor things in there i had to tweak, honestly, i forget. I may have received the classic message telling me to run appcmd, but i forget. its a blur now. However, I've repeated the process on several machines, and all are able to run RS now. Major pain in the ***. Clearly another example how how Vista is not yet ready for Prime-Time.

Open the IIS Manager and navigate to the ReportServer application (Sites/Default Web Site/ReportServer). In the Features view double click Handler Mappings and then double click the mapping with the name from the error message (e.g. Handler: AboMapperCustom-34881) to verify the executable path. Select the appropriate aspnet_isapi.dll (e.g. C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll) or simply remove the unnecessary backslash (v2.0.50727\\aspnet_isapi.dll). After that, click OK an then click Yes to allow this extension.

I installed VIsta Business over Vista Home Premium (refused to upgrade) on Toshiba 17" laptop. I checkmarked all possible options in IIS. I installed SQL Server 2005 Dev Edition including SSRS. Everything is working, including DEPLOY. You could see the deployed reports in Management Studio. I did the same on an Acer 15" laptop. All working. Some items do look different from Windows XP or Windoes server 2003.

Wow - talk about obscure. Deleting the double slash worked for me! I did not have to reinstall anything! Yeah!

Michael R. THANK YOU!! It was the extra backslash in the handler mapping. I stayed away from changing any permissions or doing anything rash and balling up the registry first thing. Reinstalled Reporting Services 3 or 4 times. I did make a change in the RSwebapplication.config file in c:\program files\Microsoft SQL Server\MSSQL.3\Reporting Services\Report Manager The element <reportservervirtualdirectory></reportservervirtualdirectory> was empty as shown and I added the value ReportServer to it. I had found other installs had the config file set this way. However, this was my first Vista and it's Ultimate x64 and using SQL 2005 x64Dev Editionas well. CHEERS!!!! I wish i could click your post was helpful a hundred times! I've been at this all week in the evenings and was almost ready to scrap the whole project

But why do you have to do this esoteric sequence?

Great Jerry! But why this happen?

removing unnecessary backslash works for me aslo :-)

Thank you so much! It is very helpfull for me too. I was in the panic before that I found your post!!! Thank you again! Simona

My Vista laptop, I have given up on for RS dev until I rebuild it. I also did the whole uninstall reinstall thing but my original mistake (no, not buying Vista to begin with, the other original mistake) was installing VS 2005 before SQL 2005 because the 'crippled' copy of SQL included in VS 2005 is really SQL but it has been jacked up to not show things like the Configuration screens (and more)and there is no going back once the damage is done(as far as I can see). But I really dolike being able to choose one of those five little animated wall clocks in my sidebar ... oh boy!

Thanks

Dude! You rock. I am so happy I found your post. I owe you one. This worked like a charm for me, avoiding '10 hours of ***'. Thank you! Brian

Hi All, Just for future reference its worth pointing out that there are numerous levels where the handler mappings can be changed, in my case it was the actual Virtual Directory / Application for the ReportServer created by the Reporting Services Configuration program, for some reason it had a strange subset compared to the web site and server levels, clicking "Revert to Inherited" in the right hand frame resolved the issue and made the reports accessable via the Report Manager.Thanks to the other posters above, without their assistance I would probably have been looking for the solution for hours.Martin

SQLUSA,Sorry I did not reply back at the time this happened, but I have no idea why the handler mapping for the ABOmapperCustom-xxxxxx had an invalid path attached to it.I was just excited to get SSRS working and needed to jump into that and get up to speed fast for work related. I have Windows 7 Professional x64 now, and am having a nightmare once again installing SQL 2005 x64 Reporting services. It won't take the required SP3 needed to be compatible on Windows 7. All other components will take it, but SSRS will not. I downloaded the x64 SP install file and run it manually. Taht way you see all of the components it's applying to patch to. If you use Windows update you just see that it keeps failing w/o any information to tell you why it failed.

removing the extra backslash worked for me too, without reinstalling anything :)