waspsoft.com


Home > Backup Exec > Backup Exec Error Connecting To The Remote Registry

Backup Exec Error Connecting To The Remote Registry

Contents

MS System Center Data Protection Manager 2007 I'm using it and really like it. 0 Thai Pepper OP Trivious Mar 29, 2010 at 6:02 UTC  Interesting Limey. Help Desk » Inventory » Monitor » Community » Registrieren Hilfe Angemeldet bleiben? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL Go to Solution. http://waspsoft.com/backup-exec/backup-exec-remote-agent-error-connecting-to-the-remote-registry.html

I could walk in, change the tape or LTO and walk out. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Problem installing Remote Agent for Windows Server... This leads me to ask the next question... Veritas does not guarantee the accuracy regarding the completeness of the translation.

Backup Exec Error Connecting To The Remote Server

Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Error connecting to the remote computer. This is my theory anyway. 0 Kudos Reply Thanks for your input... Onthe mediaservers this account has local admin priviledges and is also listed as user in Backup Exec If Iwantto updatetheagentson theservers, I getthe error:Errorconnectingtotheremoteregistryofservers.Ensurethatthecurrentloggedinaccountisnotblockedfromaccessingtheremoteregistryandthattheremoteregistryisavailablebeforetryingagain. Nick 0 Kudos Reply Contact Privacy Policy Terms & Conditions Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016

  • Join our community for more solutions or to ask questions.
  • When I moved from the SBS, now they want a load more money to make backups work too!
  • Serves run with local system account.

Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Agent Update: Error connecting to the remote regis... But Exec is very terribly slow. Nick_Elmer Level 6 Employee ‎09-14-2011 07:32 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Thank you for your feedback Backup Exec Error 1603 When Installing A Remote Agent No other firewall program is running.

Even specifying the domain admin credentials through the wizard for the RAWS installation account I was receiving the remote registry error. Backup Exec 2010 R2 - Remote Agent Install Error Code 1603 [fa icon="long-arrow-left"] Back to all posts [fa icon="pencil'] Posted by Lewan Solutions [fa icon="calendar"] September 28, 2010 Tweet While onsite RAWS does not need a service account, as it runs as local system. This would also seem logical as far as when I will not have a window to set the user credentials for the remote computer.

They might have a different security set up inherited from SQL or Exchange. 0 Thai Pepper OP Trivious Mar 26, 2010 at 9:53 UTC I had also enabled "Single Ensure That The Computer Is Available Has Wmi Enabled And Is Not Blocked By A Firewall 67 Thanks! 0 Kudos Reply Update Agents/Install Agents via push Nick_Elmer Level 6 Employee ‎07-18-2011 08:21 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Note: Avoid changing NDMP port on media server, if media server have many other working Remote Agents on port 10000 then all will drop the connection immediately after the NDMP port on media server I've checked all that you say but the issue keep appearing, and if I install the agent locally it arrows this error "Backup Exec cannot connect to the remote agent because

Error Connecting To The Remote Registry Backup Exec 2010

But, the Exec show me the size0 Kb ofmy DB! Good to know about Acronis, though thanks. Backup Exec Error Connecting To The Remote Server AndEvent ID 4672 for my "backup-user": SeCreateTokenPrivilege SeSecurityPrivilege SeBackupPrivilege SeRestorePrivilege SeTakeOwnershipPrivilege SeDebugPrivilege SeSystemEnvironmentPrivilege SeLoadDriverPrivilege SeImpersonatePrivilege 0 Kudos Reply I installedRAWS64(Local). Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available Thank you for your feedback!

if i install thebe5204R180429_x64bit.exe 0 Kudos Reply ...if that patch hasn't been CraigV Moderator Partner Trusted Advisor Accredited ‎04-30-2013 01:30 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed http://waspsoft.com/backup-exec/backup-exec-2010-r2-error-connecting-to-remote-registry.html I suspect there is a bug when the remote hosts are verifying the installation to check if you haves RAWS installed and what version you are running. During the install, we will attempt to read/write to the remote systems registry. By creating an account, you're agreeing to our Terms of Use and our Privacy Policy Not a member? Backup Exec Cannot Connect To Remote Computer

Its running now where it wouldn't before, so I am doing better already. 0 Thai Pepper OP Trivious Mar 26, 2010 at 9:54 UTC I was unaware of Domain account with full administrator rights. It made me miss the good ole days of simple backups. 0 Thai Pepper OP Trivious Mar 26, 2010 at 10:20 UTC I know the feeling, but I Check This Out http://www.symantec.com/business/support/index?page=content&id=TECH180429 will it work?

Labels: 10.x and Earlier Agent for Microsoft Exchange Server Agents Backup and Recovery Backup Exec Troubleshooting Windows Server (2003-2008) 1 Kudo Reply 10 Replies Hi, Check out the TN CraigV Bug FIx: View Templates Folder in Azure Resource Manager Premium Storage Error Fix: "The App-V server addresses must be valid URLs" in XenApp/XenDesktop 7.9 About Us We manage your printing and I can start and stop the service, reinstall the agent, reboot backup exec server, nothing works.

WTH?

Go to Solution 6 Comments LVL 23 Overall: Level 23 Storage Software 12 Windows Server 2003 8 Message Expert Comment by:bhanukir72008-06-01 Hi i think there might some restrictions for the Good to know about Acronis, though thanks. 0 Datil OP Kimberlin Mar 26, 2010 at 10:00 UTC i think backup companies are trying to hard to get the Agent has been installed very good on the other server. Try to install Backup Exec agent again after rebooting the remote server.

I entered the correct remote computer credentials in this window: The account that I use is definitely a localadmin on all servers. I had the problem with the R2, too. When we bought that house, it had an unfinished basement and an unfinished attic room, making the cabling process very simple. this contact form Seems a little slow for fiber . . . 570Mb a minute rate though and it IS RD1000 after all. 0 Datil OP Kimberlin Mar 26, 2010 at

Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603." It seems like this is the likely problem, mentioned in the below Symantec technote: http://www.symantec.com/business/support/index?page=content&id=TECH128062 Add the remote server under user-defined selections, right-click on the server & choose Establish Trust Relationship. 0 Kudos Reply Accepted Solution! Yep, I finally get solve the seguridadallus Level 2 ‎04-16-2013 07:30 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Thanks in advance.

To be honest, I haven't had an issue updating my agents (on the servers I have migrated to R3 so far), but have seen the option to trust them (I haven't...haven't Microsoft to end Windows 7 PC sales, Firefox tackles weak encryption Spiceworks Originals A daily dose of today's top tech news, in brief. © Copyright 2006-2016 Spiceworks Inc.