1-800-691-1991 | 9am - 8pm ET

Failed Accessing Windows Event Log


SCOM reports a Warning: "Failed Accessing Windows Event Log...". and in the State Change Events description you can find:

"The Windows Event Log Provider was unable to open the nworksEventLog event log on computer 'node_xxx' for reading. The provider will retry opening the log every 30 seconds. Most recent error details: The specified channel could not be found. Check channel configuration. One or more workflows were affected by this. Workflow name: many Instance name: many Instance ID: many Management group: ClusterName "


This can happen if one or a few objects have been discovered impropelry: i.e. became managed not by the Agent, but by the RMS. In particular, this issue may result from VMguest to Agent relationship created incorrectly (please, refer to KB 1600 for more detail).


To fix this issue you can try rebuilding topology from nworks UI -> "Enterprise Manager" tab -> select "Enterprise Manager" node in the left pane -> Rebuild Full Topology.

If this does not help, contact Veeam Support for further troubleshooting.


More information

You might be asked to rename certain VMs and run "Remove-DisabledMonitoringObject" PowerShell command based on the results of research.
Veeam Management Pack for Microsoft System Center
Last Modified:
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.