Start a conversation

Error: 'Scan aborted on machine <Source Name> because Active Monitoring License is used and a server operating system was detected'

Overview


When EventsManager is trying to collect event logs, the following error is displayed under Job Activity for a specific source server:

Scan Aborted on Machine <Source Name> because Active Monitoring License is used and a server operating system was detected

In EventsManager, licensing is implemented based on the nodes for which activities are monitored and logs are retrieved. When using an Active Monitoring license on a Server, only the monitoring option can be enabled, which allows to ping the server, check its CPU usage, disk space, and perform other checks; collecting Windows Events and Text Logs are not allowed for Servers using Active Monitoring licenses. With the Complete license, you can use all features offered by EventsManager.

Here is a summary of functions available per license:

mceclip1.png


Solution

To stop receiving this error, you can either disable log collection or select Complete license for the affected server(s).


Disabling Log Collection For Server

If you don't want to gather logs from the affected server sources, follow the steps below:

    1. From Configuration > Event Sources section, right-click on the required server or group and select Properties.

      mceclip2.png

    2. Under the Window Event Log tab, remove all the entries from the Specify the logs to collect section.

      mceclip3.png

    3. Under the Text Logs tab, remove all the entries from the Specify the text logs files to collect from section.
    4. Under the Monitoring tab, ensure that the Enable GFI EventsManager monitoring and Monitoring Checks options are enabled.
    5. Click OK.

      mceclip4.png


Configuring Complete License For Server

If you want to enable event logging for the affected servers, follow the steps below:

    1. Make sure that your subscription includes a sufficient number of Complete licenses:
      1. Log in to the Accounts portal.
      2. Click More Details under your GFI EventsManager subscription.
      3. Check how many Complete Node licenses it includes.
        If you don't have enough Complete node licenses, reach out to your reseller or find a new one to add Complete node licenses to your subscription.

        mceclip0.png

    2. Configure license type as Complete License for the affected Server sources or for the group of Server sources.

Testing

Open the Status > Job Activity section; the reported error should not appear anymore in Operational History for the servers for which you enabled Complete license or disabled event logging.

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted
  3. Updated

Comments