KSWMeterSvc.exe consuming loads of RAM
Is this a known thing? We did not all too long ago turn on metering on certain software and so far I've had 2 machines where KSWMeterSvc.exe consumes all available RAM on the machine.
Is there any fix to this? Other than disabling metering?
Community Chosen Answer
We have had this happen and resolved at first by simply disabling the service. We have noted by reviewing client side logs (KSWMeter.log) that the metering database is corrupted on devices where this happens and by removing the agent and redeploying it resolves the issue by creating a fresh database. The current thinking is that the database file suffers the corruption due to an anti-virus process scanning the directory and our next step is to whitelist the KACE directory on the local devices and stop the scanning process to see if that resolves the issue of corrupted metering db's. This is on 5.5 release.
It would appear that if the database is corrupted the service just continues to consume RAM until it has all gone. If the service is not running or indeed if running with a clean database it is fine - we have 1000's of unaffected clients running without issue and 3 or 4 exhibiting this specific behaviour that have exactly the same log errors. This is the error we see in the log of a machine consuming RAM and it is repeated in the log over and over again:
ProcessMeter::InitializeDB:caught CppSQLite3Exception with error SQLITE_CORRUPT: database disk imageis malformed