IIS Hosted Service Fails

If an IIS hosted service fails you may see any of the following symptoms:

• When browsing to a .svc file, the file is not recognized, the browser shows a blank page, or the text of the file is displayed instead of the service's help page as in the following example.
  
  
  Copy

  <%@ServiceHost language=c# Debug="true" Service="Microsoft.ServiceModel.Samples.CalculatorService" %>
  

• When attempting to access a Web-hosted service, you may encounter the following exception.
  
  
  Copy

  Unhandled Exception: System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (405) Method not allowed.
  

  This typically occurs if ASP.NET is not installed or the .svc file type is not mapped to the aspnet_isapi.dll.
  
  To correct this you must make sure that aspnet_isapi is enabled as a Web service extension for IIS. You can view and modify this setting using IIS Manager, or by running aspnet_regiis –i –enable from the .NET Framework installation directory. Once you have done so, verify that ASP.NET is running. To do so, place a test .aspx file in the \inetpub\wwwroot directory, and make sure it can be browsed with a browser.
  
  
• If you installed IIS after Windows Communication Foundation (WCF) was installed you must run the following command.
  
  
  Copy

  "%WINDIR%\Microsoft.Net\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe" -r
  

  This registers the required script maps in IIS.
  
  You must also make sure that the .svc file type is mapped to aspnet_isapi.dll.
  
  

1. From the Start menu, right-click Computer, then click Manage.

2. Expand Services and Applications, Internet Information Services.

3. Right-click Web Sites and select Properties.

4. On the Home Directory tab, click Configuration.

5. In the list of application mappings, verify that the .svc file is mapped to the aspnet_isapi.dll. If the file has not been mapped:

   1. Click Add.
      
      
   2. In the Add/Edit Application Extension Mapping dialog box, click Browse.
      
      
   3. Browse to the folder that contains the aspnet_isapi.dll, select the file, then click Open.
      
      
   4. Specify .svc as the extension.
      
      
   5. Make sure Check that file exists is unchecked.
      
      
   6. Click OK, and OK again to return to the Web Sites Properties dialog box.
      
      

      Caution:
      If the OK button is disabled, select the textbox where the selected filename is displayed and the OK button will be enabled.

6. Click OK to close the dialog box.

1. Open a command prompt window and type start inetmgr to open the Internet Information Services (IIS) MMC snap-in.

2. In the left pane, expand the node with the computer's name, then expand the Web Sites node, and then select the Default Web Site.

3. Double-click Handler mappings in the Features View.

4. In the list of application mappings, verify that the .svc file is mapped to the aspnet_isapi.dll. If the file has not been mapped:

   1. Click Add Managed Handler.
      
      
   2. Type *.svc into the Request path:.
      
      
   3. Type System.ServiceModel.Activation.HttpHandler, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 into the Type textbox.
      
      
   4. Type svc-Integrated into the Name: textbox.
      
      
   5. Click OK.
      
      
   6. Click Add Script Map.
      
      
   7. Type *.svc into the Request path:.
      
      
   8. Type %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll into the Executable: text box.
      
      
   9. Type svc-ISAPI-2.0 into the Name: text box.
      
      
   10. Using the Move Up/Move Down controls, ensure that the managed handler (svc-Integrated) appears before the aspnet_isapi (svc-ISAPI-2.0) handler in the list.
       
       
   11. Click OK.
       
       

See Also