Documentation forServer Configuration Monitor

Explanations of error messages in SCM

You may encounter profile errors, element errors, or server configuration errors in SCM. The tables below provide explanations for these errors to help you understand next steps.

Server configuration errors

You may encounter server configuration errors when no agent is assigned to the SCM node, when the agent status indicates a problem, when an agent plugin is not deployed or indicates a problem, when automatic detections of file/registry changes does not work, or when the operating system or FIM version is not supported. Consult the following table for an explanation of these errors and then see Troubleshoot your SCM deployment for steps you can take.

Server Configuration error messages Potential Root causes
Agent missing One or more elements assigned to an SCM node require an agent, such as a file, parsed file, registry, or PowerShell, but no agent is deployed to the SCM node.
Agent issue There is an agent deployed to an SCM node, and it is needed by some of its elements, but the status of the agent is different from OK or RebootRequired. Go to Manage Agents for more details.
SCM plugin issue There is an agent deployed to an SCM node, and it is needed by some of its elements, but the status of the SCM agent plugin is different from Installed or NotApplicable.
SCM plugin not responding There is an agent deployed to an SCM node, and it is needed by some of its elements. The SCM agent plugin seems to be deployed, but is not responsive. Go to Manage Agents for more details, or restart the agent on the node.
SCM plugin not applicable There is an agent deployed to an SCM node, and it is needed by some of its elements. However, the operating system version is too old, and the SCM agent plugin cannot be deployed. For more information on operating system requirements for SCM, see SCM system requirements.
Asset inventory missing One or more profiles is assigned to the SCM node load data from asset inventory, but asset inventory is not enabled on the SCM node. Go to List Resources to enable asset inventory.
FIM not supported version One or more elements assigned to the SCM node use FIM, but the FIM version already installed on the target machine is not compatible with the current version of SCM and cannot be upgraded automatically. See also Troubleshoot FIM driver issues in SCM.
FIM version error One or more elements assigned to the SCM node use FIM, but the version of the FIM installed on the target machine cannot be detected. See also Troubleshoot FIM driver issues in SCM.
FIM install error One or more elements assigned to the SCM node use FIM, but the FIM installation on the target machine failed.

FIM load error

FIM initialization timeout

One or more elements assigned to the SCM node use FIM, but the FIM on the target machine could not be started or configured in a timely manner. See also Troubleshoot FIM driver issues in SCM.
Server configuration polling is disabled due to insufficient license A server configuration is not covered, or its parent node is not covered by a valid node license. Polling on that SCM node is stopped.

Errors assigning elements to incompatible platforms

You may encounter profile errors if you attempt to assign a profile to an incompatible node. Consult the guidelines in the following table for proper profile assignment.

Node Type

Assigned Element Type Compatible Assignment?

Windows server

File with Windows filepath Yes
File with Linux filepath No
Registry element Yes
Linux/UNIX script element No
PowerShell script element Yes
HW/SW inventory element Yes
SWIS (internal query) element Yes
Parsed file element Yes
Mixed Windows and Linux elements No
 

Linux Server

File with Windows filepath No
File with Linux filepath Yes
Registry element No
Linux/UNIX script element Yes
PowerShell script element No
HW/SW inventory element Yes
SWIS (internal query) element Yes
Parsed file element No
Mixed Windows and Linux elements No

Element errors

You may encounter element errors if SCM doesn't have sufficient permissions or if something blocks its permissions. Consult the following table for an explanation of these errors.

Element error messages Potential root causes

Unauthorized access

Access denied

Parsed file not found

Script execution timeout

Script execution error

Polling failed

SCM cannot access a configuration file, a folder referenced by a configuration element, or the monitored folder.
SCM cannot store a PowerShell query result or a SWIS query result in temporary files on an agent or poller.
SCM cannot read a monitored registry key on the agent or the modification time on an agent.
SCM cannot create a temporary copy of an exported registry file or a temporary copy of a monitored file on an agent.
SCM cannot move a temporary file on a poller.
SCM was unable to find a configuration file to be parsed (for example, applicationHost.config).
A PowerShell script execution failed, and error output was collected to describe the execution errors.
A PowerShell script or an exporting registry took too long to finish.
There is no connection to the database or credential, and polling failed.