Datto RMM: A component is not running as expected



This article discusses troubleshooting Datto RMM components that are not running as expected.


  • Datto RMM


If a component does not run as expected, follow the steps below to troubleshoot. If the issue continues, contact Datto RMM Support. 

Verify if the component works on other devices

This helps determine if the issue occurs on a single device, certain device types, or the component in general.

Determine if it is a custom component or Comstore component

Datto RMM Support cannot debug custom components; they must be debugged by the developer or vendor of the script.

Verify if the script works outside of Datto RMM 

This helps determine if the script is failing or if Endpoint Management is failing to run the script. If the script cannot run natively, it may be an environmental issue. For custom components, verify they work outside of Datto RMM before further troubleshooting. You must do this as a local system user. 

Make sure the agent is up-to-date

Out-of-date agents can cause problems when communicating to an updated platform. Additionally, we cannot test for bugs outside of the most up-to-date version.

Verify component is up to date (if Comstore component)

We cannot test for bugs outside of the most up-to-date version

Gather information for further troubleshooting with Datto RMM Support

If the component issue continues, gather as much of the following information as possible before contacting Datto Technical Support:

  • .NET version
  • Datto RMM service and Process log files
  • Component Name
  • Export of component (if custom)

Was this article helpful?

0 out of 1 found this helpful

You must sign in before voting on this article.

Want to talk about it? Have a feature request?

Head on over to our Datto Community Forum or the Datto Community Online.

For more Business Management resources, see the Datto RMM Online Help and the Autotask PSA Online Help .

Still have questions? Get live help.

Datto Homepage