Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Component Status: Not LicensedComponent status is Not Licensed

Component Status: Not LicensedComponent status is Not Licensed

Table of contents

Updated September 14 2018


This article details an error that involves SAM component licensing.

Component Status: Not LicensedComponent status is Not Licensed


All SAM versions except an ALX license


*Looks like this issue is popping up on environments that are not SAM 6.5 or later also


SAM is licensed based on a number of component licenses. When a template is applied to a node, it is then considered an application monitor within the template are a number of components. If you have a license type outside of the ALX license which is unlimited, you can surpass the allowed number of components.


Once this has been surpassed some items applied to the node will return the error:

Component Status: Not LicensedComponent status is Not Licensed.


-This will reflect an unknown status as well.

-To correct this, you have to upgrade your current license type or scale back on some templates applied to nodes

within your environment.


*For environments not on SAM 6.5 or later this issue has been popping up a bit.

If this issue occurs and is not due to actual license constraints it's likely due to a known SAM issue fixed in SAM 6.5 and later.


The permanent solution for this is to upgrade to SAM 6.5 or later.

Alternative solution is to run this query during maintenance window:

UPDATE APM_DynamicEvidenceColumnSchema SET IsThresholdOverridden = 1 WHERE ComponentTemplateID IS NULL AND [Type] = 1


You can do this by:

1. Rdping to your main polling engine.
2. Stopping all orion services using orion service manager.
3. Opening database manager -> add default server -> right click your bolded database instance -> new query -> paste query -> execute
4. Then restart all orion services using the orion service manager.


Last modified