Print

This page contains the list of known issues associated with Sitecore CMS 6 when IIS is configured to work in Integrated Pipeline mode.

• When denying read access to the home item of the site and accessing it with a short URL, such as http://mysite.com, Sitecore may redirect to the "layout not found" page instead of the site's login page or the "no access" page.
  Workaround:
  Deny read access to the item that is specified by the "rootPath" attribute of the current site.

The following issues have been fixed in CMS 6.2 rev. 091012, but apply to the recommended release:

• Opening a Sitecore Desktop application, such as the Content Editor, causes Sitecore to display an unhandled exception message or redirect to the login page.  This may occur when the web.config “addAspxExtension” property is set to “false” in the <linkManager> settings.
  
  Workaround: Apply the “SitecoreIntegratedFix” mentioned below.
   
• The ASP.NET session state may be unavailable to Web page’s code depending on the URL used to access a Web site. This occurs with short URLs, such as http://mysite.com or http://mysite.com/products, while longer URLs, such as
  http://mysite.com/default.aspx or http://mysite.com/products.aspx, do not encounter the issue.
  
  Workaround: Download the SitecoreIntegratedFix.zip, compile it as a class library and place assembly to the bin folder of the solution. Add the following lines to the <modules> section of the <system.webserver> section:
  
  
        <add type="Sitecore.IntegratedSessionFix.Module, Sitecore.IntegratedSessionFix" name="Module" />     
        <remove name="Session" />
        <add name="Session" type="System.Web.SessionState.SessionStateModule" preCondition="" />
   
• A known issue in Microsoft IIS may cause Sitecore to restart during index rebuilding or package installation when Sitecore indexes are stored below the Sitecore web site root folder.
  
  Workaround: Moving the Sitecore indexes outside website root will resolve the issue.
  To configure this, add the following to the <settings> section of web.config file:
  
        <setting name="IndexFolder" value="C:\test\indexes" />
  
  Note: You must ensure that the application pool identity has full control over the chosen index folder. For more information about appropriate folder permissions, please refer to the Sitecore CMS 6 Installation Guide.
   
• Debug mode for the website cannot be started via Sitecore client.
  
  Workaround #1: After logging in to the Sitecore Client, start the Sitecore Debugger by typing the following URL in the browser’s address bar:
  
       http://mysite.com/sitecore/debug
  
  Workaround #2: Start the Debugger from the Desktop as usual. This will open a new window, but the Debugger doesn’t start. After the new window has opened, start the Debugger by changing the URL from
  
       http://mysite.com/?sc_debug=1&sc_prof=1&sc_trace=1&sc_ri=1
  to
  
       http://mysite.com/default.aspx?sc_debug=1&sc_prof=1&sc_trace=1&sc_ri=1