Hello, this is problem with Backup Exec 9.1. We have 3 WIN2003 machines with stand-alone tape dirves. Veritas services are running logged as: Local System, Logon Account is: System Logon Account - domain administrator (backup server is Domain Controller). When we try to run backup - we have Failed notice: 'Final error: 0xa000fe29 - Authentication failed on connection to the server' and 'Access is denied to Remote Agent. Check the login account for the specified device.' Please answer. -- BR., Blaze RE: Backup fails - no connection to server (TechnicalUser) 9 Nov 04 10:14. Re: Symantec Backup Exec 2012 problems It is certainly a big change from previous versions, but a worthwhile one once you get used to it. Moving from a job centric view to a server centric one is a bit like moving from imperial to metric. In Backup Exec 2010 R3 and earlier versions, the Logon Accounts can be managed from Network Menu -> Logon Accounts. For Backup Exec 2012 and later, logon account management window is available in Configuration and Settings -> Logon Accounts -> Manage logon Accounts. Description: An alert that Backup Exec failed due to a Failure Occurred Accessing the Object List. This usually happens due to an issue accessing files for the System State. Run the debugging tool that is pre-installed with Symantec. Backup Exec 2012/2014. Open the Logon Account Manager. Windows Server 2012 server with RD Web and RD gateway roles. Remote Windows 7 client trying to login to a workstation via RD Web website User can successfully login to the RD Web (Work Resources) website. Hi there, It sounds to me like you have a problem with the user account that is being used to do the backup. I'm not saying this is the answer but I'd recomend that you check check which user account the job is defined to use. This is found from inside the jobs properties - in the device credentials or something. Backup Exec 2012 Download LinkThen you should probably check the priviladges that this account has - it must have full backup priviladges (must be part of the backup users group I think) and I'm not sure if it needs full administrative rights as well. And it's probably safest to check these actually from the computer that you are trying to backup not from the domain controller cause they can look differant. Access vba update sql table from another sql table. I myself got this wrong and spent days trying to go through all the differant combinations with the services and then realised it wasn't that at all it was the job's access rights. Let us know how you get on M RE: Backup fails - no connection to server (TechnicalUser). Hi i had the same problem after i had changed the admin password on the server you need to change the default login account password in backup exec all i did was click on job setup then double click a job and i got a message saying the password was wrong and then the next screen was the default login account screen where i put in the new admin password after that everything worked ok i thought all you needed to do was change the services credentials user account / password but obviously not! Cheers neil RE: Backup fails - no connection to server (TechnicalUser) 19 Nov 04 09:17. Moh spearhead patch 2.15. For further assistance feel free to post your queries in Microsoft forums.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |