Normally this behavior occurs when you write the backups with a different user than the user that starts the local BESR console, e.g. you login as Administrator and start the BESR console, but the backups are written to a UNC path and the user used to access this location is access_admin. For this sitation the solution is to login as Administrator, map or access the UNC path first and then start the BESR console.
