Home > Backup Exec > Backup Exec System Recovery 2010 Cannot Connect To Agent

Backup Exec System Recovery 2010 Cannot Connect To Agent

Email Address (Optional) Your feedback has been submitted successfully! Error Message This program is unable to connect and communicate with the Backup Exec System Recovery Service on Cause This issue occurs because the Default Component Object 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 Therefore 100 separate rules must be created. have a peek here

All the computers are on the same domain and subnet All computers have a working network connection All three computers exhibit identical behavior to what Vero is showing. The trust relationship between the remote computer and the media server is automatically established during installation. (See related articles for How to push install Backup Exec RAWS)2. DCOM is enabled and is configured that everybody has all permissions. You may also refer to the English Version of this knowledge base article for up-to-date information.

Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Cannot connect to an Agent running on Windows Server 2008/Windows 7 if the Agent computer However once the 2003 server comes back up, I cannot connect and get the error message: "ESR 2010 - Program is unable to connect and communicate with Backup Exec System Recovery Error: This program is unable to connect and communicate with the Backup Exec System Recovery backup service on . No Yes Did this article save you the trouble of contacting technical support?

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 Create a REG_SZ - Right click again in the right pane and select New then String Value 4. Backup Exec System Recovery requires opening the following ports: 137 (inbound and outbound TCP and UDP) 138 (inbound and outbound UDP) 139 (inbound and outbound TCP) By default, DCOM is free No Yes How can we make this article more helpful?

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 No Yes How can we make this article more helpful? Push-install the remote agent to one or more remote computers from the media server. BlackSun Level 3 ‎07-05-2010 12:30 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content hello, does it work? 0 Kudos

It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.  Resolve the permissions issue by following the steps as below: 1.Click I get this message on XP 32 bit, 2003 32bit, Win7 32 and 64 bit, 2008r2 64bit machines if I deploy them via silent installation. Labels: Agents Backup and Recovery BESR 2010 Installing Remote Agent for Windows Servers System Recovery Windows 0 Kudos Reply 21 Replies Hello, i have the same BlackSun Level 3 ‎06-18-2010 09:20 No Yes How can we make this article more helpful?

i am having the same troubles with SSR 2011 Ports are in the excution list of the windows firewall - I checked the Symantec Article: TECH55824 - Troubleshooting Communication Issues With https://vox.veritas.com/t5/System-Recovery/Unable-to-connect-to-Remote-Agents-in-BESR-2010/td-p/310778 Solution Confirm the permissions issue by enabling the DCOM error logging through registry as below: 1.Click Start, click Run, type regedit, and then click OK.2.Locate the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole registry subkey.3.Right-click the Ole value, You may also refer to the English Version of this knowledge base article for up-to-date information. Create/Manage Case QUESTIONS?

Solution With a default installation of Windows Server 2008/Windows 7 with the Windows Firewall enabled, the Dynamic RPC ports are blocked.  This will prevent the Backup Exec System Recovery console running navigate here What Ports does Backup Exec System Recovery Utilize? 2. Create/Manage Case QUESTIONS? Click Add..., enter the IP address of the computer running the Backup Exec System Recovery Console under This IP address or subnet, click OK, and then click Next.  8.

Veritas does not guarantee the accuracy regarding the completeness of the translation. We are also starting to roll out Windows 7 machines, happens on those as well. Click Next  7. Check This Out This is another way to establish the trust relationship between remote computer and media server.3.

Follow the steps in www.symantec.com/business/support/index, then test the connection to the remote client/agent from the local SSR 2013 console. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : System Recovery : BESR 2010 - Program is unable to connect and commu...

Email Address (Optional) Your feedback has been submitted successfully!

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? On the Protocol and Paths screen, under Protocol type select TCP. Submit a False Positive Report a suspected erroneous detection (false positive). Try these resources.

You may also refer to the English Version of this knowledge base article for up-to-date information. Email Address (Optional) Your feedback has been submitted successfully! Sorry, we couldn't post your feedback right now, please try again later. http://cmptp.com/backup-exec/backup-exec-system-recovery-cannot-connect-to-agent.html Manually install the remote agent, then open the selection list on the media server and browse the remote server.

I fear this product is unusable with the new operating systems.. TECH55824 July 25th, 2011 http://www.symantec.com/docs/TECH55824 Support / Troubleshooting Communication Issues With Backup Exec System Recovery (BESR). Labels: Agents Backup and Recovery Basics BESR 2010 Configuring Error messages Installing System Recovery Tip-How to 0 Kudos Reply 3 Replies Getting the same problem here... One of our XP pro machines, with the firewall off, still can't connect.

Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : System Recovery : Cannot Connect to Agent VOX : Backup and Recovery : System Recovery : We use Symantec Endpoint Protection instead which has not interfered with this connection. under Actions  4. Install the Remote Agent for Linux or UNIX Servers on a Linux or UNIX computer respectively and then add the computer to User-defined Selections.   Please refer to the Related Document

Thank You! Below is an image of the message I receive when trying to connect. For Local Port select RPC Dynamic Ports. Double-click ActivationFailureLoggingLevel, type 1 in the Value data box, and then click OK.5.Right-click the Ole value, point to New, and then click DWORD Value.6.Type CallFailureLoggingLevel, and then press ENTER.

Create/Manage Case QUESTIONS? That did fix the XP pro machine, I'll be trying it on the Windows 7 machines this morning. I'm actually upgrading a lot of win2K3 box with besr 8.5 agent to besr 2010 and if deployment is ok after reboot I can't connect the box to besr to check Within Internet, create a REG_MULTI_SZ - With Internet highlighted, right click in the right pane and select New then MultiString Value 3.

You may also refer to the English Version of this knowledge base article for up-to-date information. I enabled the ports, but still won't connect, any other ideas? 0 Kudos Reply ..