Compliance Calulation takes a long time...

May 7, 2018 at 7:00 AM

Hi, since Snow License Manager 8.3 Build 6674 our platform need a long time for the compliance calcuation. Every time we see only this: So but the Licensing Service Log say: 16:08:19,256 95 INFO BatchTaskDirector; Calculation cleanup took 00:00:14.0388477 16:08:19,272 95 INFO CalculationRequestTask; Finished request, duration 00:00:32.5312395 16:08:19,303 7 INFO CalculationRequestRunner; Calculation task has completed. Does anyone have the same problem? Lars

LarsReifegerste
8 years ago
Hi, after delete the both databases for EventStore Service and Software Enterprise Agreement Service the problem is solved. So i restart these services and after that a new password for this services was created.
Expand Post
PeteS
8 years ago
Hi, I don't have Snow on-prem, we have a managed service. Our compliance recalc does take a while and I have always understood this to the fact we have a lot of devices. Some months back I noticed that our recalc compliance appeared to be running continuously, so I reached out to our Service provider. The main issues was it was set to auto recalc compliance at 1000hrs and 1400hrs, in between that time if one of them hit recalc it affected my view to. SO I have since got them to switch of the auto Recalc during the day and the problem went away. Obviously, it still takes a while when I have to recalc, but no more continually running in the back ground. Regards
Expand Post
johann.ihnen
8 years ago
Hello Lars, the calculation didn't stop here since the 8.3 update. Thanks, your tip helped me a lot.
Expand Post
carolai
8 years ago
Hi, We are also on SLM 8.3, but we have no problem with the compliance calculation. The compliance calculation is scheduled to run automatically once per day after the DUJ and takes around 8 minutes. When we need to start a calculation manually during the day, this also works and required also around 8 minutes. In your log it looked like the calculation finished in 32 seconds, are there any errors in the log? In the past we had also problems, but then found errors in the log, regarding a special license.
Expand Post