- About LogicMonitor
- Cloud Monitoring
- Collector Overview
- Collector Installation
- Collector Management
- Collector Failover
- Collector Configurations
- Collector Troubleshooting
- Collector Groups
- Dashboards and Widgets
- Getting Started
- LM Service Insight
- Rest API Developers Guide
- RPC API Developers Guide - Deprecated
- Servicenow CMDB Integration
- Terminology and Syntax
We’ve compiled some helpful tips for troubleshooting common Windows Collector issues.
A common error encountered for Windows Collectors:
Error 1069: The service did not start due to a logon failure.
The account used to run the LogicMonitor Collector service on Windows must have “Log on as a service” rights on the host machine’s local security policy.
To update the local security policy:
1. Log on to the Collector host as a Local Administrator.
2. From CMD, PowerShell, or Run launch secpol.msc.
3. Expand “Local Policy” and click “User Rights Assignment”.
4. Right-click “Log on as a service” and select “Properties”.
5. Click “Add User or Group” to add the account which is to run the LogicMonitor Collector services.
6. In the “Select Users or Groups” dialog, find the user account and click “OK”.
7. In the “Log on as a service” properties window, click “OK” to save your changes.
If you are not able to make these changes (for example options may be greyed out or unavailable), you may need to look into what is enforcing the local security policy settings on the host–it may be the local or domain Group Policy settings or another configuration management tool.
Windows Monitoring Scenarios
Common monitoring scenarios on Windows use WMI and Perfmon. If you have issues related to monitoring WMI or Perfmon, refer to the following resources:
In this Article: