These binding settings should be fine. What version of Indicium are you currently using? Indicium 2021.2.12.0
Our binding settings:The Hostname is a local DNS-entry (A-record)
yes it is:
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
Also remarkable is that the “Next run” every 3 minutes will be updated
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.
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.
Hi Mark, finaly was able to check.Now an error in the Indicum logging:[ERR] An exception was thrown while deserializing the token. (348bf365)Microsoft.AspNetCore.Antiforgery.AntiforgeryValidationException: The antiforgery token could not be decrypted. ---> System.Security.Cryptography.CryptographicException: The key {a1654860-6c47-4858-835b-a44fcf13f474} was not found in the key ring. at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.UnprotectCore(Byte[] protectedData, Boolean allowOperationsOnRevokedKeys, UnprotectStatus& status) at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.DangerousUnprotect(Byte[] protectedData, Boolean ignoreRevocationErrors, Boolean& requiresMigration, Boolean& wasRevoked) at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.Unprotect(Byte[] protectedData) at Microsoft.AspNetCore.Antiforgery.DefaultAntiforgeryTokenSerializer.Deserialize(String serialized
Hi @Mark Jongeling , thanks for this link.For some reasons I wasn't able to find it myself 😬Will try next week if we are able to make this work.One question already upfront: do we need to put in the password just as plain text ? Or can we MD5 it for example ?
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.