Trigger causes a 'Failed to communicate to NetVault services' error.
An SQL transaction log backup needed to be run every 15 minutes, but could not be completely setup in NetVault Backup, as the NetVault Scheduler can only be setup for every hour as a minimum.
Therefore a Windows scheduled task was setup to launch a script to run the backup jobs via a trigger (nvtrigger.exe).
Unfortunately the following error happens when the script was launched:
PS C:\Program Files (x86)\Quest Software\NetVault Backup\bin> .\nvtrigger.exe RemedyTranJob
Failed to communicate to NetVault services
All the trigger job setup information is in section 6.5.0 of the NetVault Backup 9.2 Administrators Guide on the following link:
In order to use NetVault you always have to be logged in as an Administrator or root, so make sure that the user that is using the script (as well as the script) has full Administrator rights.
Additionally when using the CMD terminal within Windows, make sure you right click the CMD icon and select "Run as administrator", as this may be causing the “Failed to communicate to NetVault services” error message.
If this isn’t resolving the issue, then you may have to change the NetVault Process Manager (within the Windows Services on the NetVault Server) > Logon tab, to use Domain or local Administrator login details in the “This account” field in the lower section, instead of using the “Local system account”.
In this instance the 'Failed to communicate to NetVault services' error message was resolved by making sure that the Windows Scheduler - scheduled task configuration - has the 'Run with highest privileges' box selected.
Note: An Enhancement Request to add “Minutes” to the Scheduled tab > Repeating section > Every section has been created and will be considered for a future version of NetVault Backup (Bug 3726).