Quantcast
Channel: Veeam Support Knowledge Base
Viewing all articles
Browse latest Browse all 4362

'Events data collection failure' Issue

$
0
0

'Events data collection failure' Issue

KB ID: 2266
Product: Veeam ONE | 11 | 12 | 12.1
Published: 2017-04-10
Last Modified: 2024-05-31

Challenge

Veeam ONE raises Events data collection failure against Veeam Backup & Replication or Hyper-V server.

Cause

Permissions, UAC configuration, and firewall settings need to be configured.

Solution

Troubleshooting Checks

  • Verify that the account used to connect to Veeam Backup & Replication or Hyper-V server in Veeam ONE has correct permissions.
    Changing Server Connection Settings
  • On the Veeam Backup & Replication or Hyper-V server, confirm that the connection account and the Veeam ONE service account, are added to the Event Log Readers Group and Administrators group within Local Users and Groups > Groups (compmgmt.msc)
  • Even if the Windows Firewall is off, activate the following firewall rules on the Veeam Backup & Replication or Hyper-V server:
    (See the More Information section for a PowerShell script to check the Firewall rule status and enable rules.)
    • Remote Event Log Management (NP-In)
    • Remote Event Log Management (RPC)
    • Remote Event Log Management (RPC-EPMAP)
    • COM+ Network Access (DCOM-In)
  • Check UAC settings.

Shared Server Troubleshooting

If the server from which Veeam ONE is failing to collect events (e.g., Veeam Backup & Replication or Hyper-V) is the same server on which Veeam ONE is installed, try one of the following solutions in addition to the steps mentioned above:

  1. Change the classification of all network connections from Public to Private using the following Powershell cmdlet:
$networkConnections = Get-NetConnectionProfile
foreach ($connection in $networkConnections)
{
Write-Output "Network Name: $($connection.Name), Network Category: $($connection.NetworkCategory)"
if ($connection.NetworkCategory -eq 'Public')
{
Set-NetConnectionProfile -InterfaceIndex $connection.InterfaceIndex -NetworkCategory Private
Write-Output " -> Network category changed to Private."
}
}
  1.  If changing the network type classification does not help, reconfigure Connection Settings for the Veeam Backup & Replication or Hyper-V server in question to use the Built-in Administrator (local Administrator) account.

More Information

If the issue persists, contact Veeam Support for further assistance.
To check if the Firewall rules are enabled, use the following PowerShell script:
Get-NetFireWallRule | Where {$_.Name -eq 'RemoteEventLogSvc-NP-In-TCP'}
Get-NetFireWallRule | Where {$_.Name -eq 'RemoteEventLogSvc-In-TCP'}
Get-NetFireWallRule | Where {$_.Name -eq 'RemoteEventLogSvc-RPCSS-In-TCP'}
Get-NetFireWallRule | Where {$_.Name -eq 'ComPlusNetworkAccess-DCOM-In'}
If one or more of the the rules are not enabled, enable them using the follow PowerShell commands:
Set-NetFirewallRule -Name 'RemoteEventLogSvc-NP-In-TCP' -Enabled True
Set-NetFirewallRule -Name 'RemoteEventLogSvc-In-TCP' -Enabled True
Set-NetFirewallRule -Name 'RemoteEventLogSvc-RPCSS-In-TCP' -Enabled True
Set-NetFirewallRule -Name 'ComPlusNetworkAccess-DCOM-In' -Enabled True
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Viewing all articles
Browse latest Browse all 4362

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>