CODEWITHSUNDEEP
asp.net-mvciisiis-8.5
Laurence Frost
Laurence Frost

Reputation: 2993

IIS 8.5 - Application initialization not working

I have installed Application Initialization, set the website's application pool Start Mode to "Always Running", and set Preload Enabled = "True" in the advanced settings of the website.

However, if I recycle the application pool manually and wait 10 seconds, when I then reload the website, I still have to wait another 10 seconds for the website to warm up. This indicates that the website is not starting.

Looking at task manager, I can see that the application pool is running the whole time - even after a recycle. However, the memory usage is very low until I make my own request to the website.

One thing I have noticed is that I do not have a "Start Automatically" setting in the advanced settings of my website as per this link: https://blogs.msdn.microsoft.com/vijaysk/2012/10/11/iis-8-whats-new-website-settings/

How can I get my application to auto-start?

Upvotes: 14

Views: 21500

Answers (5)

Gerard Sexton
Gerard Sexton

Reputation: 3200

There are multiple .config locations where these settings can be set.

  1. Machine applicationHost.config (c:\windows\system32\inetsrv\Config)
  2. Website web.config (c:\inetpub\wwwroot for Default Web Site)
  3. Application web.config

I tried all but was only successful in configuring 3, the application web.config. My specific use case was calling a GET method on a WCF service.

The steps for application initialization are found in the other answers too. Here is one that was most helpful. IIS 8.0 Application Initialization

  1. Install the Windows feature Application Initialization (Web-AppInit)
  2. Set the IIS app pool Start mode = AlwaysRunning
  3. Set the IIS application Preload Enabled = true

  4. Add to the application web.config

    <system.webServer>     
    <applicationInitialization doAppInitAfterRestart="true" skipManagedModules="true">
        <add initializationPage="/Service.svc/Method/Parameter" />
    </applicationInitialization>
</system.webServer>

  5. Recycle app pool

  6. Check that the app initialized.

The thing I would like to point out is that the initialization page is relative to the application NOT to the root of the website/domain so if my absolute path is

domain.com/path1/path2/Service.svc

I would not include /path1/path2 in the initializationPage parameter.

Upvotes: 7

George
George

Reputation: 301

If anyone's wondering what to do in MVC when you have multiple areas to initialise, you need to put the area at the start, all within the root web.config file. I was stuck for a while trying to put it in the area's web.config. Also it's perfectly compatible with hybrid applications.

<add initializationPage="/NotMVC.aspx" />
<add initializationPage="/Area1/Controller/Action" />
<add initializationPage="/Area2/Controller/Action" />

Upvotes: 5

jlo-gmail
jlo-gmail

Reputation: 5038

These articles are very good:

Use IIS Application Initialization for keeping ASP.NET Apps alive

IIS 8.0 Application Initialization

However in my case there was a problem with installing the Application Initialization Role.

Check your IIS App's Modules listing. Ensure ApplicationInitializationModule is present.

enter image description here

I needed to uninstall/re-install this module.

I have no idea what happened as this appeared to work at first, then weeks later during development it stopped. No amount of tinkering/rework fixed it and I started to suspect I never actually saw this working.

Issue resolved upon uninstall/re-install Applicaion Initialization Module role.

Upvotes: 8

Laurence Frost
Laurence Frost

Reputation: 2993

It turned out to be a whole load of settings which all had to be correct. You go through all of the steps to install the relevant components and make the various config changes as per this link: http://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-application-initialization

The key part which was missing for me was an instruction in the Web.config as below. I had it going to just "/Login" which is a valid route, but as soon as I switched it to "/[Controller]/[Action]" it worked.

The advantage of this route is that you can create a custom action which will also hit the database (initialising Entity Framework), and perform any other slow initialisation you wish. For me, I just read a record out of a DB table, so I get ASP.NET auto-starting, and also save the few seconds it takes to warm up EF too :)

<system.webServer>
  <applicationInitialization doAppInitAfterRestart="true" skipManagedModules="false">
      <add initializationPage="/Login/WarmUp" />
    </applicationInitialization>
</system.webServer>

Upvotes: 27

Guru_07
Guru_07

Reputation: 392

Try Application Initialization setup:

I had similar issues and tried very hard with IIS 8.5 Windows Server 2012 R2. Everything in the IIS was set correctly after referring to so many sites however had missed the Application Initialization setup. Refer to the below link, Setup section.

enter image description here

https://www.iis.net/configreference/system.webserver/applicationinitialization

Upvotes: 10

Related Questions