waspsoft.com


Home > Backup Exec > Backup Exec Error Connecting To The Remote Computer 24

Backup Exec Error Connecting To The Remote Computer 24

Contents

No Yes How can we make this article more helpful? Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. 24   Cause WMI Remote execution requires the following:   "Adjust Memory Quotas for Process Go to Solution. One of the servers I am attempting has never been backed up before, so currently had no agent installed. 0 Kudos Reply try do a local HAMZAOUI_Omar Level 5 Partner Accredited have a peek here

copy the source in the client server from BE server in c:\programfiles\symantec\backupexec\Agents\Rawsx86 or x64. It is recommended that a complete backup of the registry and workstation be made prior tomaking any registry changes.Goto the following registry key: HKEY_CLASSES_ROOT\CLSID\ Locate the 'AppID' String Value key and CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Typically, a local install requires a reboot though.

Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available

Ensure that the server is available, has WMI enabled, and is not blocked by a firewall.24" To fix this problem try the following on the remote computer: Run Group Policy Editor Any ideas? Create/Manage Case QUESTIONS? Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

Add the User 'LOCAL SERVICE' to the Group or user names list and give Allow access for these permissions:   Local Launch Remote Launch Local Activation Remote Activation   Fig 7 Click Agent has been installed very good on the other server. Veritas does not guarantee the accuracy regarding the completeness of the translation. Error Connecting To The Remote Registry Backup Exec If Amanda_Jayne Level 4 ‎11-20-2014 09:30 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Which, I believe, it does.

No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities AndEvent ID 4672 for my "backup-user": SeCreateTokenPrivilege SeSecurityPrivilege SeBackupPrivilege SeRestorePrivilege SeTakeOwnershipPrivilege SeDebugPrivilege SeSystemEnvironmentPrivilege SeLoadDriverPrivilege SeImpersonatePrivilege 0 Kudos Reply I installedRAWS64(Local). a few servers on a separate domain I'm currently unable to communicate with the servers from within backup exec. But now: Microsoft Exchange 2010 database backup fails with V-79-57344-913 database was not found error.

files\symantec\backup exec\agents\RAWS32 and MSXML) 2 : On the Remote server, open command prompt and navigate to the RAWS32 folder and run setupaa.cmd Example : D:\BEAGENT\RAWS32\>setupaa.cmd 3 : Go to Start-->All Prog-->Symantec-->Remote Error Connecting To The Remote Registry Backup Exec 2010 RTFM Sysadmin Jobs Official Subreddit IRC Channel - #reddit-sysadmin on irc.freenode.net Posts of pictures are not permitted. Please try establishing a trust manually and then have the Backup Exec services restarted. 0 Kudos Reply Perhaps I was a bit vague Amanda_Jayne Level 4 ‎11-21-2014 04:47 AM Options Mark DenisFrolov Level 3 ‎04-30-2013 01:04 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I installedRAWS64(Local).

  1. Serves run with local system account.
  2. Go to Solution 6 Comments LVL 23 Overall: Level 23 Storage Software 20 Message Active 3 days ago Expert Comment by:Iamthecreator2013-01-23 Is there a number at the end of the
  3. Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Backup Exec 2014 trial - Error connecting to
  4. Make sure that the computer is available, WMI is enabled and not blocked Windows Firewall.14 Firewall is turned off, antivirus is empty, the WMI service is enabled.
  5. Select the Security tab.

Backup Exec Cannot Connect To Remote Computer

Join Now For immediate help use Live now! Technical Notes My Technical Notes Blog Archive May (1) April (1) March (2) February (2) January (7) November (1) October (1) August (3) July (4) June (4) May (3) April (2) Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available Learned this many,many years ago. 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. The Backup Exec Server Could Not Connect To The Remote Computer I've been asked to change this so that we push the agent out to it from another newer symantec install (backup exec 2010 r3) on an sbs2008 box.

Veritas does not guarantee the accuracy regarding the completeness of the translation. navigate here Join the community of 500,000 technology professionals and ask your questions. I tried instal with local administrator account and gave all sorts of rights, but to no avail. A Windows Security Alert pop-up will appear, click Unblock. 5. Backup Exec Cannot Connect To The Remote Computer Because A Trust Was Not Established

Labels: 2014 Agents Backup and Recovery Backup Exec Basics Not Applicable 1 Kudo Reply 18 Replies ...make sure that no AV is CraigV Moderator Partner Trusted Advisor Accredited ‎11-20-2014 06:05 AM Ensure that the computer is available, has WMI enabled and is not blocked by a firewall" Article:000015581 Publish: Article URL:http://www.veritas.com/docs/000015581 Support / Article Sign In Remember me Forgot Password? Don't have Great care should be taken when making changes to a Windows registry. http://waspsoft.com/backup-exec/backup-exec-error-connecting-remote-computer.html Make sure that the computer is available, WMI is enabled and not blocked Windows Firewall.14 DenisFrolov Level 3 ‎04-29-2013 06:57 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed

No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Ensure That The Computer Is Available Has Wmi Enabled And Is Not Blocked By A Firewall 67 This is becoming a sticking point, and will prevent us from upgrading, which is a shame. 0 Kudos Reply « Previous 1 2 Next » Contact Privacy Policy Terms & Conditions Solution Solution 1: Manually install the remote agent Copy the RAWS32/RAWS64 (from X:\Program Files\Symantec\Backup Exec\Agents) and the MSXML folders on the particular remote server where you want to install Remote Agent.On

Join our community for more solutions or to ask questions.

Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Sorry, we couldn't post your feedback right now, please try again later. Incase if you would like to troubleshoot further there Special considerations for installing Backup Exec to remote computers Item Consideration Windows XP SP2/Server 2003 SP1 To push-install Backup Exec to a How To Install Backup Exec Remote Agent Manually Apologies for the misquote in the OP, the full error is "Error connecting to the remote computer.

Under 'Launch and Activation Permissions' select the 'Customize' radio button and click EditFig 6 8. In system log is nothing. Reboot the Workstation or Server wherein this DCOM change occurred.10. this contact form Re-attempt the push installSystem account could be blocking the setup.   If a push/local install of RAWS fails with the error 1603 still and is accompanied by the below event log

Network access to server is have. If your post requires a picture put it in the text. /r/iiiiiiitttttttttttt (i7t12) for your rage comics, and "Read Only Friday" posts. /r/techsupportanimals for your memegenerator images Link Flair Filters Gilded Mike_Serbin N/A ‎03-18-2010 03:03 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I am having the same issue. Thank You!

From the dcomcnfg Console Root select Component Services | Computers | My Computer | DCOM ConfigLocate the DCOM Object that matches the Value Data from the 'AppID' Registry Value Data noted What do I need to do with regards to the firewall for my BE server to talk to and push out the agent to the client servers. 2 commentsshareall 2 commentssorted They are highly useful for migrations and disaster recovery. A definite work around is to do a local install of the agent on the server by downloading the BE install media and installing the agent that way.

http://www.symantec.com/business/support/index?page=content&id=TECH180429 will it work? OnlyEvent ID 4634: An account was successfully logged off. You must enable the following items: File and Printer Sharing Windows Management Instrumentation (WMI) For more information refer to your Microsoft Windows documentation. 0 Kudos Reply Also you can try the All rights reserved.REDDIT and the ALIEN Logo are registered trademarks of reddit inc.Advertise - technologyπRendered by PID 8535 on app-556 at 2016-10-01 22:52:27.440791+00:00 running 62abcea country code: US.

Only thing of note on the old box is a copy of vmware 2 hosting an accounts application Is there any way vmware will be blocking the ports I need? But now: Microsoft DenisFrolov Level 3 ‎04-30-2013 01:28 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ok. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Push install of the Backup Exec Remote Agent to a Remote Windows Server fails with Make sure...