You can get a trace of the commands that are being ran by turning on a debug flag within the SQL Backup Agent service. To do this, you need to start the service with the -sqbdebug flag.
Open the Windows Service Manager. Look for the SQL Backup Agent service. If no backups or restores are running, stop the service. On the 'Start parameters' value, enter '-sqbdebug' (without the quotes). Now click on 'Start'.
A log file is generated in the folder where the service is located, named SQBCoreService_log.txt. Run a backup that results in the warning. Now stop the service, close the properties page and start the service normally (without the sqbdebug parameter).
In the resulting log file, there should be a record of the command that caused the error. Let us know which is it.
SQL Backup Consultant Developer
Associate, Yohz SoftwareBeyond compression
- SQL Backup goodies under the hood, updated for version 8