Hi, did you check the Indicium (Universal) log to see if any errors were returned by Indicium? System flows might stop working due to an error in the model. Indicium will write the error to the log.

Hi Mark,

No errors in Indicium related to the schedule. Last error was from 13:46 (UTC) and was related to some error we made in the data when calculating a value in Universal.

But….on the server where our TEST-environment is running, also we have an DEV and ACC environment running on the same server. Only PROD is running on a separate server.

What I noticed is that also the Scheduler for DEV (15:00 UTC) and ACC (14:57 UTC) stopped.
They have their own IAM DB and also own Indicium Universal/Basic running. So wondering if it's related to the server somewhere.

Will do a reboot of it now and see what will happen.

also a reboot and installing the latest Windows updates didn't solve it.
Wondering if  some IIS issue is causing this problem.
 

==

Just restarted the Application Pool of the Indicium (Universal) and noticing the following erros in IIS-Configuration Administrative event log:

Unable to find schema for config section 'system.serviceModel/extensions'. This section will be ignored.
Unable to find schema for config section 'system.serviceModel/client'. This section will be ignored.
Unable to find schema for config section 'system.serviceModel/tracking'. This section will be ignored.
Unable to find schema for config section 'system.serviceModel/serviceHostingEnvironment'. This section will be ignored.
Unable to find schema for config section 'system.xaml.hosting/httpHandlers'. This section will be ignored.

Also remarkable is that the “Next run” every 3 minutes will be updated

Indicium will try to run the system flow each 3 minutes. If it is not able to run for whatever reason it will try again so the next run time will be updated but the last run will stay the same. Does the indicium log mention it's skipping the schedule?

Are you sure the system flows works, was something changed to the flow or the data? Is there a step where you could add some logging to a table in the database? 
 

Found the issue!

We restarted the Application Pool of the Indicium Universal, but that doesn't make the scheduler active yet.

After I also opened the Universal login screen (without logging in yet), the scheduler was running again.

Checked the IIS settings for the application pool, and noticed the Start Mode = "AlwaysRunnning”.

So it seems that this IIS setting is not sufficient for starting the Indicium Universal again after an Application Pool restart (recycle I don't know)

So is this a bug or expected behavior ?

btw, running Indicium 2021.2.1.2.0

Can you check if you have application initialization activated in IIS? https://docs.thinkwisesoftware.com/docs/deployment/iis.html#application-initialization

yes it is:

The Application Initialization module fires the startup requests to web applications over http. These requests need to arrive in order for Indicium to be started automatically after downtime. Can you check the site bindings in IIS?

For what its worth we currently experiencing the same issue - got that one adressed in ticket #2030S - status is ‘being assessed’ - Also app-init installed, preload set to true - but to no avail.

Our binding settings:

The Hostname is a local DNS-entry (A-record)

These binding settings should be fine. What version of Indicium are you currently using? 

Indicium 2021.2.12.0

You mentioned you use both indicium basic and indicium. Do they have their own application Pool or are you sharing 1 app pool?

They have their own application pool as also the Basic needs the .NET CLR configured and the Indicium not.

Is preload enabled set to true for the indicium site? 

 

no, this is set to false:

So this was missed during initial setup I guess ?
And if I enable it this will solve the issue ?

I tested it locally and without this feature enabled the warmup does not work. Could you enable this and try to recycle the app pool?