Compliance calculation after Data Update Job

alexander_bu asked a question.

June 7, 2018 at 7:00 AM

Hi all, I am experiencing a strange behaviour: Whenever the automatic Data Update Job has finished the calculation for license compliance won't run correctly anymore in the first place. For instance, I have some Mindjet licenses. I measure the license need for primary users and have the license entitlements assigned to the root organisation. After the DUJ has finished license compliance looks like this: That is utterly wrong, obviously. Neither the inventory nor the available licenses are considered for calculation in any way. Manually running the calculation for compliance again produces the expected results (including downgrades and so on): Funny enough, I cannot reproduce the issue by manually starting the DUJ. I have already raised a ticket, but it might not hurt to check whether any of you experienced this behaviour before. Any ideas on that? Best, Alex

alexander_bu
8 years ago
Hi ‌ and ‌, thanks for your input! I will check the configuration and see if I can make a change. Best, Alex
Expand Post
- alexander_bu
  8 years ago
  Strangely enough, the issue sort of solved itself. Since Friday last week I did not experience any more calculation errors. I am still in contact with support, though, to find out what was the problem. ‌, your argument makes sense. Even if there would be changes in the license stock maintained in SLM one would manually trigger the calculation for compliance anyway. So thanks for the hint Best, Alex
  Expand Post
carolai
8 years ago
Hi Alex, As Sebastiano mentioned DUJ do not perform a compliance calculation. But it's interesting that you cannot reproduce this by a manually started DUJ. But I wanted to add following Since SLM 8 the compliance calculation tooks significantly more time than before and SLM is very slow during that calculation. So that was very annoying for us. As I talked to support because of this, he asked me, why I need this hourly calculation. DUJ is running only once per day in the night, so no new computers will appear and no requirement will change. And during that call I noticed, I don't need that automatic calculation, I only was used to have it from the former versions. When we add licenses or remove computers and then need a new calculation, then we anyway start the calculation manually. So during that support call I decided to start the automatic calculation only per day, directly after the DUJ. At the moment we are using only the below setting in C:\Program Files\Snow Software\Snow License Manager\Services\Licensing\SnowSoftware.LicenseManager.Licensing.Service.exe.config. <calculationSchedule> <task time="02:30" type="RequirementsAndCompliance" waitForDataUpdateJob="true" /> </calculationSchedule> When DUJ has not finished at that time, then the calculation waits and directly starts after DUJ. For us this is the best setting. And when we do some changes during the day and want to know the current compliance, then we start the calculation manually.
Expand Post
- Gert-Jan Kosterman
  8 years ago
  Hi Carola, good suggestion. Do I need to restart a service after modifying this .config file? And if so which service? I guess SnowLicensing? Thanks, Gert-Jan.
  Expand Post
  - Sebastiano Bonfiglio (Flexera Software)
    8 years ago
    Hi Gert-Jan, After the changes, please restart the "Snow Software Licensing Service". Best, Sebastiano
    Expand Post
Sebastiano Bonfiglio (Flexera Software)
8 years ago
Hi Alexander, Normally the full compliance is calculated at 06:00 in the morning only. During the rest of the day only the requirement is calculate every hour. The full run at 06:00 would normally wait until the DUJ finished, if this is still running at that time. It looks like it isn't executed in properly in the morning, especially if it works well after a manual recalculation of the compliance. Please check your setting in the "SnowSoftware.LicenseManager.Licensing.Service.exe.config" (C:\Program Files\Snow Software\Snow License Manager\Services\Licensing) to see if these match the schedule specified below and compare this to the time your scheduled DUJ finishes. If the DUJ is not able to finish before 06:00, you might change the schedule for full calculation to a later time. If this still doesn't fix the issue, I recommend to wait for support to help you out. <calculationSchedule> <task time="06:00" type="RequirementsAndCompliance" waitForDataUpdateJob="true" /> <task time="07:00" type="Requirements" /> <task time="08:00" type="Requirements" /> <task time="09:00" type="Requirements" /> <task time="10:00" type="Requirements" /> <task time="11:00" type="Requirements" /> <task time="12:00" type="Requirements" /> <task time="13:00" type="Requirements" /> <task time="14:00" type="Requirements" /> <task time="15:00" type="Requirements" /> <task time="16:00" type="Requirements" /> <task time="17:00" type="Requirements" /> <task time="18:00" type="Requirements" /> <task time="19:00" type="Requirements" /> </calculationSchedule> Best, Sebastiano
Expand Post