If you see the above error when your “Veeam Agent Backup” jobs try to run, then you need to make a change to your Veeam database (on the Veeam server).
This is perfectly mentioned in this KB4421 – but if you are using Microsoft SQL (embedded with Veeam) and have no SQL management studio installed – here is a quick guide on how to fix the above problem – just using OSQL.exe (included with SQL embedded)
Locate the OSQL.EXE executable – I found it here: “C:\Program Files\Microsoft SQL Server\110\Tools\Binn”
Using command prompt (cmd.exe) run the executable with:
osql.exe -E -S <SERVERNAME>\<DATABASE>
Replace SERVERNAME and the database name (ex. “osql.exe -E -SVEEAMBACKUP\VEEAMSQL2012”). When OSQL prompt is ready for input type the following:
use VeeamBackup; go update dbo.[Backup.Model.EpHosts] set os_version='0.0' where os_version='' go exit
That should be it – try to run your “Veeam Agent Backups” again!
This error is seen when you open the Veeam Backup and Replication console “Failed to check certificate expiration date”
Its seems like there is a bug in Veeam Backup and Replication that hits you 11 month after you install or upgrade to 9.5 U3 – luckily Veeam is already aware of it and some helpful URLs has been revealed in Anton Gostev weekly newsletter that can assist in solving this error:
Ill like to highlight that after updating “Veeam Backup and Replication” to “version 9.5 update 3a” you might start to see warnings like this in your Veeam status reports:
Warning: [TDB]Unable to update SQL backupset for instance : Code = 0x80040e09 Code meaning = IDispatch error #3081 Source = Microsoft OLE DB Provider for SQL Server Description = The UPDATE permission was denied on the object ‘backupset’, database ‘msdb’, schema ‘dbo’.