Mappings for server-side include (SSI) directives do not work after you upgrade from IIS 6.0 to IIS 7.0

Article translations Article translations
Article ID: 954754 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario. You have a Windows Server 2003-based server that is running Internet Information Services (IIS) 6.0. You upgrade the operating system on this server to Windows Server 2008, and you upgrade the IIS installation to IIS 7.0. In this scenario, a file name extension that is mapped to the Ssinc.dll file does not work as expected.

CAUSE

This problem occurs because there is no Ssinc.dll file in IIS 7.0.

RESOLUTION

To resolve this issue, add a module mapping for the file name extension in IIS 7.0. To do this, follow these steps:
  1. Use one of the following methods to start IIS Manager:
    • Click Start, and then click Internet Information Services (IIS) Manager.
    • Click Start, click Run, type inetmgr.exe in the Open box, and then click OK.
  2. Expand the server that you want, and then click the Web site or application that you want to modify.
  3. Click Features View, and then double-click Handler Mappings.
  4. Right-click the handler mapping for the file name extension that existed in IIS 6.0, and then click Remove.
  5. Click Add Module Mapping.
  6. In the Requested path box, type the file name extension.
  7. In the Module box, click ServerSideIncludeModule.
  8. In the Name box, type the name that you want to use for the mapping.
  9. Click Request Restrictions. In the Request Restrictions dialog box, set the restrictions that you want.
  10. Click OK two times.

Properties

Article ID: 954754 - Last Review: July 1, 2008 - Revision: 1.0
APPLIES TO
  • Microsoft Internet Information Services 7.0
Keywords: 
kbexpertiseinter kbtshoot kbprb KB954754

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com