Solved

Problem Automatic license renewal 2021.1

  • 16 April 2021
  • 8 replies
  • 135 views
M
Rank
Userlevel 2
Badge +6

The license is not automatically renewed.
The registration has been successful.
Starting the IIS application manually also works fine; when i start it as administrator as well when i start it as de pool-user.
Automatically it does not work.

I'm working with the installation 2021.1

I have checked the problemsolving: idle-time is set to 0 and startmodus is AlwaysRunning. The authorization on the wwwroot-map is set correctly.

So beats me. What can i do? Who has any ideas?

icon

Best answer by Vincent Doppenberg 19 April 2021, 20:15

View original

8 replies

Mark Jongeling
Rank
Userlevel 7
Badge +23

Hi Marco,

Did you enable the Preload option as described in the documentation? 
Indicium Service Tier · Thinkwise Docs (thinkwisesoftware.com)

"Wake me up before you low-code"
M
Rank
Userlevel 2
Badge +6

Yes, that's done too

Arjan Sollie
Rank
Userlevel 4
Badge +13

Hey Marco,

Has your environment been registered yet? Or is this the part that is failing?

If this is failing, what is the error you are receiving after executing the task “Register environment” from IAM?

M
Rank
Userlevel 2
Badge +6

No all the projects are registered. I really haven't any clue what is going wrong or what i'm doing wrong.

V
Rank
Userlevel 6
Badge +4

Hello Marco,

Can you confirm the following.

You have the Application Initialization module installed. This is necessary in order for the Start Mode configuration on an Application Pool to work.

 


The Application Pool’s Start Mode configuration is set to Always Running. This setting will cause the Application Initialization module to ensure that the Application Pool is always running.


Your site has an http binding, not just https. 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.


The first ​rewrite rule in the web.config of your Indicium application is the following. If you use rewrite rules to route http traffic to https, then an exception must be made for the requests made by the Application Initialization module. The rewrite rule below is included in Indicium by default, but it is important that it is turned on and placed at the top of the list of rewrite rules.

 

I hope this helps.

M
Rank
Userlevel 2
Badge +6

Hello Vincent,

The module was not implemented. After implementing the automatic licence renewal is working.

I think you helped me a lot. Thank you very much and that 1000 times.

Harm Horstman
Rank
Userlevel 5
Badge +20

Hi @Vincent Doppenberg ,

Could you please add a text version of the rewrite rule, to this conversation, so that it can be copied to the clipboard?

Or a link to a place in the documentation where it can be found.

V
Rank
Userlevel 6
Badge +4

Hello Harm,
 

I’ll paste it here but I would like to stress that this topic should not be the source for this rewrite rule. There should be no need to ever copy this rewrite rule because it is included in Indicium’s web.config by default and has been for many months now.

If the rewrite rule is missing from your web.config then one of the following things has gone wrong:

  • Indicium is not being updated often enough.
  • When updating Indicium, the web.config file is not being overwritten.

If you have made changes to the web.config yourself, then these must be merged into the web.config file of a new Indicium release. We also make changes to the web.config and we depend on these changes being there. Just a few weeks ago we have released a startup retry mechanism that included a very important change to the web.config file.

Here is the rewrite rule that you asked for, but I would recommend merging your web.config with that of the Indicium release that you are using.

<rule name="No redirect on warmup request (request from localhost with warmup user agent)" enabled="true" patternSyntax="ECMAScript" stopProcessing="true">
  <match url=".*" />
  <conditions logicalGrouping="MatchAll">
    <add input="{HTTP_HOST}" pattern="localhost" />
    <add input="{HTTP_USER_AGENT}" pattern="Initialization" />
  </conditions>
  <action type="None" />
</rule>

I hope this helps.

Reply


Terms & ConditionsCookie settings