Quantcast
Channel: Application Initialization Module
Viewing all articles
Browse latest Browse all 109

SharePoint 2010 and Application Initialization configuration

$
0
0

I have read the documentation of the Application Initilization and tried the steps with a SharePoint 2010 web application. However I don't get any error nor any loading splash page.

These are my <applicationPools> settings in the applicationHost.config (bolded are the changes due to app init):

             <add name="SharePoint - 80" autoStart="true" startMode="AlwaysRunning" managedPipelineMode="Integrated">
                <processModel identityType="SpecificUser" userName="..." password="..." loadUserProfile="true" idleTimeout="00:00:00" pingingEnabled="false" />
                <recycling logEventOnRecycle="Time, Requests, Schedule, Memory, IsapiUnhealthy, OnDemand, ConfigChange, PrivateMemory">
                    <periodicRestart time="00:00:00">
                        <schedule>
                            <clear />
                            <add value="02:36:00" />
                        </schedule>
                    </periodicRestart>
                </recycling>
                <failure rapidFailProtectionMaxCrashes="10" />
            </add>

 and the <site> section:

            <site name="SharePoint - 80" id="244320120" serverAutoStart="true">
                <application path="/" preloadEnabled="true" applicationPool="SharePoint - 80">
                    <virtualDirectory path="/" physicalPath="C:\inetpub\wwwroot\wss\VirtualDirectories\extranet.dev80" />
                    <virtualDirectory path="/_vti_bin" physicalPath="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\isapi" />
                    <virtualDirectory path="/_vti_bin/anonsvc" physicalPath="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\isapi\anonsvc" />
                    <virtualDirectory path="/_layouts" physicalPath="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\template\layouts" />
                    <virtualDirectory path="/_layouts/images" physicalPath="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\template\images" />
                    <virtualDirectory path="/_layouts/inc" physicalPath="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\template\layouts\inc" />
                    <virtualDirectory path="/_layouts/styles" physicalPath="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\template\layouts\styles" />
                    <virtualDirectory path="/_wpresources" physicalPath="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\wpresources" />
                    <virtualDirectory path="/_controltemplates" physicalPath="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\template\controltemplates" />
                    <virtualDirectory path="/_layouts/ClientBin" physicalPath="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\template\layouts\clientbin" />
                    <virtualDirectory path="/_layouts/1033" physicalPath="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\template\layouts\1033" />
                </application>
                <application path="/_vti_bin/sts" applicationPool="SecurityTokenServiceApplicationPool">
                    <virtualDirectory path="/" physicalPath="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\isapi\sts" />
                </application>
                <bindings>
                    <binding protocol="http" bindingInformation=":80:extranet.dev" />
                </bindings>
                <logFile logFormat="W3C" />
            </site>

 

and finally under <system.webserver> in the web apps web.config:

    <applicationInitialization remapManagedRequestsTo="init.html" skipManagedModules="true">
        <add initializationPage="/" />
    </applicationInitialization>

I put a sample init.html into the  web applications directory: C:\inetpub\wwwroot\wss\VirtualDirectories\80.

The problem is that SharePoint just loads normally, there is not splash page shown. I am assuming this has to do with SharePoint modifying the IIS Pipeline and having its own virtual path provider?

Steve Schofield writes that the application initilization is perfect for Sharepoint, yet I can't get it to work.

Could someone point me in the right direction and give me the correct settings to have my init.html displayed?


Viewing all articles
Browse latest Browse all 109

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>