High CPU on SQL Server and failed config deployments in Management Console

Version 1

    Verified Product Versions

    AppSense Management Center 8.7AppSense Management Center 8.6AppSense Management Center 8.5AppSense Management Center 8.4AppSense Management Center 8.3AppSense Management Center 8.2AppSense Management Center 8.1AppSense Management Center 8.0AppSense Management Center 10.0

    Introduction

    When EM, AM or PM configurations are edited and saved back into the Management Center, the old config version is kept in case you need to revert to it at a later date. Making large numbers of edits to the configurations can result in lots of old versions existing in the database. Large numbers of these (several hundred) can cause high CPU usage on the SQL Server where the database is located, and can also prevent configurations from being deployed to endpoints - the Deployment Status of these will be less than 100%.

    Detail

    This issue can be resolved by removing the unneeded old Package versions. You can do this from the Packages section in the Management Center console - simply Shift and click .to select multiple versions then click the Remove link in the menu on the right hand side. It may take a few minutes to delete all the versions if you have a large number.

    If a timeout error is received when trying to remove old verisons, please view the following article : http://www.appsense.com/kb/160901080608030

    If you still cannot remove them from the console, please contact AppSense Support for assistance.