Veeam Backup Job service or Veeam Job Monitor service misconfigured - access denied

Last Modified

Thu Dec 20 16:09 GMT 2018

Description

The agent is failing to collect Veeam job information and the following error is seen when using Tools > Command prompt, or in the NALocalAssetDiscovery.log

get-vbrjob : Failed to connect to Veeam Backup & Replication server: Access denied.

::NALocalAssetDiscovery.log - shows access denied when querying.

[ReadStdErr] 2018-03-14 16:56:44,788 DEBUG com.nable.agent.framework.localAssetScanner Process StdError(file): Get-VBRJob : Failed to connect to Veeam Backup & Replication server:
[ReadStdErr] 2018-03-14 16:56:44,788 DEBUG com.nable.agent.framework.localAssetScanner Process StdError(file): Access denied.

::attempt to use the Veeam Powershell snapin, fails on access denied error, just as in the logs. This is not an N-able N-central Agent problem.
C:\Windows\system32>powershell
PS C:\Windows\system32> Add-PSSnapin VeeamPSSnapin
PS C:\Windows\system32> get-vbrjob

get-vbrjob : Failed to connect to Veeam Backup & Replication server:
Access denied.
At line:1 char:1
+ get-vbrjob
+ ~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-VBRJob], Exception
+ FullyQualifiedErrorId : System.Exception,Veeam.Backup.PowerShell.Command
.GetVBRJob

PS C:\Windows\system32> get-executionpolicy
Unrestricted

AMPBasedMonitoringModule.log
[Local RC Task] 2018-03-13 16:30:05,145 ERROR com.nable.agent.AMPBasedMonitoring.AMPBasedMonitoringModule  *** ERROR *** Failed in ExecuteAMPAndCollectData TaskID: 1725415268, Error Message: Message: Error Running the Job command - Full Error is:ERROR : No backup or Replication Job for the job name specified ; Please check the Job name - Full Error is: Error StackTrace: at

Environment

  • N-able N-central 10 or later

Solution


A workaround is to change the "Windows Agent Service" service to run under an Active Directory service account. Note that this could cause other N-able N-central monitoring services on the device to become misconfigured, or possibly cause issues with remote control.

Start > Run > Services.msc > locate "Windows Agent Service" > right click > properties > logon > pick a domain user with access.

Another workaround would be to provide access for the localsystem account to the Veeam services/snap-in.